Bug #426

Not even an English writing system exists by default

Added by J C about 3 years ago. Updated over 2 years ago.

Status:New Start:05/08/2010
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:- Spent time: -
Target version:V1.1.x
Resolution:

Description

Out of the box, Solid doesn't have a single writing system predefined--not even English. Since English is part of the MDF standard, I would think it at least should be included. Instead, I had to manually create it type "Eng" "English" "en", and assign it to the appropriate fields. Hopefully I got that right.

Predefining the "big eight" or so LWC's would give good bang for the buck: English, French, Spanish, Mandarin, Arabic, Portuguese, Indonesian, Swahili.

Having dummy writing systems for national, regional, and vernacular would also be good, so that they can be pre-assigned to the appropriate MDF fields. Of course, the user would then have to rename them at some point. -Jon

History

Updated by J C about 3 years ago

Ken Z just told me the following: "If you have people use SOLID to make LIFT files, make sure it uses correct 2-letter writing system codes or it can get Flex messed up on import. A prime example is eng should be en."

This is all the more reason why the big 8 (at least) should be predefined, and the English fields pre-assigned.

Updated by john hatton almost 3 years ago

Jon, When I run SOLID, I see that it shows all the writing systems I've set up in the Windows Language and Keyboard settings: English, Icelandic, and Arabic. When you do it, I'd expect you'd see "English" and "Indonesian". Can you check again and tell me what you see?

Also, the English that I see does use the 2 letter code which FLEx requires (the 3 letter is also an ISO standard and valid in many contexts, but FLEx's use of ICU makes it intolerant to the 3 letter versions).

Updated by Beth Bryson almost 3 years ago

1. Apparently the "eng" problem got fixed along the way... And they have fixed FLEx import to recognize when data is coming in with the "eng" abbreviation.

2. In case it matters for anything, the 8 "Internationalization languages" are: English, French, Spanish, Portuguese, Chinese (not specified for Mandarin or Cantonese, Simplified or Traditional), Indonesian, Russian, German.

3. If JohnH is correct, that seems appropriate to me.

Updated by Cambell Prince over 2 years ago

  • Target version set to V1.1.x

TODO: Ship Solid with the big 8. Note to self, use the std ldml files + win keybd.

Updated by Beth Bryson over 2 years ago

Beth Bryson wrote:

1. Apparently the "eng" problem got fixed along the way... And they have fixed FLEx import to recognize when data is coming in with the "eng" abbreviation.

2. In case it matters for anything, the 8 "Internationalization languages" are: English, French, Spanish, Portuguese, Chinese (not specified for Mandarin or Cantonese, Simplified or Traditional), Indonesian, Russian, German.

3. If JohnH is correct, that seems appropriate to me.

If you set up the 8 internationalization languages that I listed, for Chinese it should probably be zh-CN, which would be mainland Chinese (simplified script, usually Mandarin language). If you wanted to add zh-TW, I think that could get used as well.

Also available in: Atom PDF