Ticket #9218 (new defect)

Opened 6 years ago

Last modified 4 years ago

Add Dari and Pashto locales for Afghanistan

Reported by: sayamindu Owned by: cjb
Priority: normal Milestone: 8.2.1
Component: not assigned Version: not specified
Keywords: r? Cc: edmcnierney, cjl
Action Needed: finalize Verified: no
Deployments affected: Afghanistan Blocked By:
Blocking:

Description

The locale information for Dari and Pashto need to be added to the builds. I am pushing this for 8.2.1 since

a) Right now there is absolutely no locale information for the two languages in glibc, which means even very basic things like right to left rendering of the UI will not work in the two locales

b) This needs to be done during the build. This is because even if the deployment team on the field wants, it would be impossible for them to add the information manually in each XO since the localedef tool (which adds the information from the definition files into the glibc locale db) will fail on the XO due to mmap() not working on jffs2 (workaround is to manually copy a 75 file on each XO, which may cause instability)

I'm attaching the patch which needs to be applied to glibc.

Chris, do you think this is useful enough to be worth of the last minute distractions ? ;-)

Attachments

olpc_afghanistan.patch (28.7 kB) - added by sayamindu 6 years ago.
Locale data, provided by Nasir from the Afghanistan deployment team.

Change History

Changed 6 years ago by sayamindu

Locale data, provided by Nasir from the Afghanistan deployment team.

in reply to: ↑ description   Changed 6 years ago by cjb

  • next_action changed from review to add to release

Replying to sayamindu:

I'm attaching the patch which needs to be applied to glibc. Chris, do you think this is useful enough to be worth of the last minute distractions ? ;-)

I think so, yes. Are you able to do a scratch build in koji with this, test it, and put it into ~/public-rpms/staging?

Thanks.

  Changed 6 years ago by cjb

.. oh, I guess you're going to have trouble testing it, for the reasons you mentioned above? But I do still need the RPM to feed to the build process.

  Changed 6 years ago by sayamindu

  • next_action changed from add to release to test in release

I added the RPMs in my staging.

  Changed 6 years ago by sayamindu

| Test Case |

1. Set /home/olpc/.i18n to LANG=fa_AF.UTF-8

2. Restart X (Ctrl-Alt-Backspace)

3a. Verify the interface gets rendered in RTL (right to left mode)

3b. Verify that the Xorg messages in VT1 does not mention "Warning: Locale not supported by C library.."

4. Repeat tests with /home/olpc/.i18n set to LANG=ps_AF.UTF-8

follow-up: ↓ 6   Changed 6 years ago by dsd

  • next_action changed from test in release to diagnose

Test case FAILS in staging-11:

fa_AF.UTF-8 works as expected, but ps_AF.UTF-8 is rendered LTR. There are no "Locale not supported" warnings that I can see, and the translations have been applied, however the interface is not RTL.

in reply to: ↑ 5   Changed 6 years ago by sayamindu

Replying to dsd:

Test case FAILS in staging-11: fa_AF.UTF-8 works as expected, but ps_AF.UTF-8 is rendered LTR. There are no "Locale not supported" warnings that I can see, and the translations have been applied, however the interface is not RTL.

Ugh. Thanks for testing. I'll check this out.

  Changed 6 years ago by sayamindu

  • next_action changed from diagnose to finalize

Just tested, this is not due to glibc. The GTK+ translations for Pashto are missing (which can be handled via language packs). (just copy the fa (Persian) translations of gtk20 into the ps directory, and you'll get RTL)

Since we have been working from the F-9 branch directly, I think we'll have to work from the staging area only (no Koji).

I'll submit the patch to Fedora, so that they can put this upstream whenever they can.

  Changed 4 years ago by cjl

  • cc cjl added

This was reported as fixed in the build 802 8.2.1 release notes on the wiki.

http://wiki.laptop.org/go/Release_notes/8.2.1

Can this be closed yet?

  Changed 4 years ago by cjl

Is there someone from OLPC Afghanistan that can confirm whether this has been fixed?

Note: See TracTickets for help on using tickets.