On Wed, Apr 25, 2018 at 06:39:05PM +0200, Eike Rathke wrote:
Hi Khaled, On Tuesday, 2018-04-24 21:00:24 +0200, Khaled Hosny wrote:On Mon, Apr 23, 2018 at 10:21:49PM +0200, Eike Rathke wrote: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/zlmIdeally 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.Does it have to be [ms] and [ms-Arab] or could it be {[ms] or [zsm] or [zlm]} and {[zsm-Arab] or [zlm-Arab] (or maybe [ms-Arab])}?
I don’t really know. HarfBuzz expects a BCP 47 language tag, and I use LanguageTag::getBcp47() to get that, so as long as it gives me “ms” all good (the script part is redundant for me, because that is detected from the text string and passed independently to HarfBuzz). Regards, Khaled
Attachment:
signature.asc
Description: PGP signature