On Mon, Apr 23, 2018 at 10:21:49PM +0200, Eike Rathke wrote:
Hi Khaled, On Saturday, 2018-04-21 23:21:23 +0200, Khaled Hosny wrote:On Fri, Mar 30, 2018 at 01:59:51PM +0200, Khaled Hosny wrote:I want to set a text in Malay [1] but using the Arabic script (AKA Jawi [2]), but it seems that Malay is only allowed for “Western” text and not “CTL” and free-form language tags are not allowed in CTL as well. Do I need to add a new locale or do something else? Any reason why free-form language tags are not allowed for CTL text?I found https://bugs.documentfoundation.org/show_bug.cgi?id=81714 which answers the last question somehow (though it is not clear what is exactly needed). My main question about supporting Jawi is still unanswered.Seems I overlooked your previous mail. Anyway, if this is about supporting the same language in different scripts we can sort that out by using proper language tags and hard categorizing the CTL one. However, the Malay language group is confusing to me. Are we talking about "Standard Malay [zsm]" https://iso639-3.sil.org/code/zsm written in Latin and Arabic script, or any of the various languages listed under the [msa] macrolanguage code there (the macrolanguage code being the [ms] 639-1 code we currently have as tag, which actually is not "a language"), or "Malay (individual language) [zlm]" https://iso639-3.sil.org/code/zlm
Ideally it would be whatever Malay variants we support now. Looks like we have LANGUAGE_MALAY_MALAYSIA and LANGUAGE_MALAY_BRUNEI_DARUSSALAM and both can be written in Arabic script, so I think we need to support both For my actual need, any thing that ends up sending “ms” language tag (with Arabic script text) down to HarfBuzz will do, the country variant does not matter. Regards, Khaled
Attachment:
signature.asc
Description: PGP signature