Ticket #6689 (closed enhancement: fixed)

Opened 7 years ago

Last modified 2 years ago

Need to be able to customise default language/keyboard

Reported by: BryanBerry Owned by: dsd
Priority: high Milestone: 13.1.0
Component: distro Version:
Keywords: rel-8.1.1:- rel-8.2.0:? Cc: cscott
Action Needed: no action Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Hey cscott, sorry to hassle you over the customization key.

The XO's we received for Nepal probably *do not* have Nepal set as the country nor the language in the firmware's manufacturing data. That is because the XO's that arrived in Nepal were originally intended for a group in the US.

We need a way to customize the /home/olpc/.i18n using the customization key. Otherwise, the XO's will default back to English after reflashing.

It is quite critical that teachers and kids be able to reflash their XO's by simply sticking in a USB key and holding down the game buttons.

If they have access to the firmware then the restore process could become a lot more complicated.

thanks cscott!

Change History

Changed 7 years ago by BryanBerry

  • priority changed from blocker to high

I have downgraded this ticket because we figured out how to change the Locale from w/in the firmware.

from the Forth prompt:

change-tag LA ne_NP.UTF-8

change-tag KL ne

Ties Stuij figured this out

Changed 7 years ago by Blaketh

  • keywords release? added

Changed 6 years ago by cscott

  • summary changed from Need to be able to change .i18n file with Customization Key to Need to be able to change .i18n and .kbd files with Customization Key

We should still be able to change .i18n and .kbd with the customization key.

Changed 6 years ago by cscott

  • component changed from build-system to distro
  • milestone changed from Never Assigned to Update.2 (8.2.0)

Changed 6 years ago by mstone

  • keywords rel-8.1.1:- rel-8.2.0:? added; release? removed

Changed 6 years ago by cscott

  • next_action set to never set
  • blockedby 7878 added

Would be fixed by #7878.

Changed 6 years ago by cscott

  • blockedby 7878 removed

Changed 6 years ago by cscott

  • cc cscott added
  • owner changed from cscott to mstone

Michael, could you help out with this bug?

Changed 2 years ago by dsd

  • status changed from new to assigned
  • next_action changed from never set to package
  • summary changed from Need to be able to change .i18n and .kbd files with Customization Key to Need to be able to customise default language/keyboard
  • milestone changed from 8.2.0 (was Update.2) to 13.1.0
  • owner changed from mstone to dsd
  • type changed from task to enhancement

Similar field requirements also popped up in Canada recently. Implemented a simple scheme with olpc-utils and olpc-os-builder to customise default language and keyboard settings (overriding mfg data). Implemented as olpc-utils 4142a480b116027ef5a889a5e90117924458459a and olpc-os-builder 5257c94c119b2b20de489fbdb2a05597a1fe15d0

Changed 2 years ago by dsd

For the record, the problem in Canada is that they work in different communities, each with their own language. Some want an English default, some want French. Then they ship some modified keyboard layouts for some region, etc.

It wouldn't be nice/practical to adjust the mfg data on a per-school basis, but having OS images customised for regional requirements is manageable.

Changed 2 years ago by dsd

  • next_action changed from package to add to build

Fixed in olpc-utils-3.0.3.

Changed 2 years ago by dsd

  • next_action changed from add to build to test in build

Test in 13.1.0 build 2.

Changed 2 years ago by greenfeld

  • status changed from assigned to closed
  • next_action changed from test in build to no action
  • resolution set to fixed

I built a custom 13.1.0 post-os5 image with the new olpc-os-builder settings configured to set everything to Armenian on a non-Armenian laptop.

The laptop booted with an Armenian keyboard and display language as expected.

I also tried an image with invalid values to make sure the parameters were still being set (or overridden with sane defaults) as expected.

Note: The parameters provided to olpc-os-builder need to follow the format seen in the manufacturing table to get the desired effect.

Note: See TracTickets for help on using tickets.