Message ID | 20220125013310.182786-1-emil@soleyman.com |
---|---|
Headers |
Return-Path: <libc-alpha-bounces+patchwork=sourceware.org@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id A28F23857C7A for <patchwork@sourceware.org>; Tue, 25 Jan 2022 01:33:40 +0000 (GMT) X-Original-To: libc-alpha@sourceware.org Delivered-To: libc-alpha@sourceware.org Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by sourceware.org (Postfix) with ESMTPS id D819C3858005 for <libc-alpha@sourceware.org>; Tue, 25 Jan 2022 01:33:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D819C3858005 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=soleyman.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=soleyman.com Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3F7195C01C1; Mon, 24 Jan 2022 20:33:26 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 24 Jan 2022 20:33:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=soleyman.com; h= cc:cc:content-transfer-encoding:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm1; bh=S0KO8SJz2vop/AfYHA+pgTvDx9B6LauiJiX6kdESph8=; b=bOs3w keRs3JFVeTFHPgRPzCzC8JXkju5QJL7c8sKV2DUg4uEka5QVb+Lf7uENwsfwoH1+ s2E2uDVggEn4v8Fu6zFO3occaqWyJhwB7k5llr5IfrPSZP4yqGOD+Qbq/5EgQbn2 zltlYdIFnkRFDUU6JdCXUaMecrY2JhNyaSF1W0usWc85xwoWIVfdTAvQWWtYDumc lRIdJrLSNruirIahKzvLq7zmDoAONHqnads+iJl0Y2bX/wuYtp44x/i2uF/MLy5k zjZJ3DC060/yAff1DoZY9PwvDRkna1JuMBp8q94y1kWP4xQtiswIWFfTcFRS+NJC lVLD68YxVyb58eMUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding:date:date :from:from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=S0KO8SJz2vop/AfYHA+pgTvDx9B6L auiJiX6kdESph8=; b=PovG7QGP7N4oNnrEmHoE+xLHlys98wQH1RrO4udmRstk4 rx5WEhTE6Hd7DBhM2QSX1zkFJXvjyJYQmJrczqeREMvLmW9bYc0Sem8KLdlNLbTh pfdGKBqAIveVMrR0BQN/y9ZglRyoLDPMNz0raofwXCirteDTp5DRd25FCn88U0Wl s65Fp0KehRhBGbtYo48IsobJhoTdrQLS2t0kuSlCH9Ua7qt++aQKeHeFhsMgz42k WPzhl5t/404MlNqfXch2aUvCSJaB2yMRruRMxiqHbnCiNoa08OSIulTOFaecMpK9 mzo1Z5FfmFnWWD0bl/TZhUI5p4H1EySRC/164gJfg== X-ME-Sender: <xms:ZVPvYcC4pEdt8Fssei9Swe7bsxyGbXhIoXbB3n3LtZWow4EBHebO5A> <xme:ZVPvYehFFZis8gIkNsW5vK_AuNwq9Pk3XaF-NfRWtZ0Yegy1RleFHyfEPJoO6Tw89 I6JWd936TSG3iiRI0A> X-ME-Received: <xmr:ZVPvYfmLHXe_tRIFMyvD8sK3zbQLP4hOwKoACWPnfNeMmTydL0WZVLS0TbGD> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvdekgdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkffoggfgsedtkeertdertd dtnecuhfhrohhmpefgmhhilhcuufholhgvhihmrghnqdgkohhmrghlrghnuceovghmihhl sehsohhlvgihmhgrnhdrtghomheqnecuggftrfgrthhtvghrnhepfeeujedtkeejheegve ehvdekveekhedugfdvfeeltedvhedvheetveejtedtfffhnecuffhomhgrihhnpehunhhi tghouggvrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepvghmihhlsehsohhlvgihmhgrnhdrtghomh X-ME-Proxy: <xmx:ZlPvYSy7xX8hGngKEhPNO5bxZFwNq0VAWVRBIdx7ZvML7gPiqCvPjg> <xmx:ZlPvYRT-Lf7gSO03z9Upt21TD5mUpxa9fTlqi67po8t5g3fNFwdWEQ> <xmx:ZlPvYdbCMZ9hH9iKinmMYDMNKlAiQQlSSwZDzW9rB2pu-pP7LtM3Pw> <xmx:ZlPvYS7PCL_1DUmG60T4EervT2UZoFkuI8jDFOkZrcBbks7wn7jk3Q> Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 24 Jan 2022 20:33:25 -0500 (EST) From: Emil Soleyman-Zomalan <emil@soleyman.com> To: libc-alpha@sourceware.org Subject: [PATCH 0/2] localedata: Add locale for syr_SY [BZ #27063] Date: Mon, 24 Jan 2022 19:33:08 -0600 Message-Id: <20220125013310.182786-1-emil@soleyman.com> X-Mailer: git-send-email 2.32.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_LOW, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list <libc-alpha.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/libc-alpha>, <mailto:libc-alpha-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/libc-alpha/> List-Post: <mailto:libc-alpha@sourceware.org> List-Help: <mailto:libc-alpha-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/libc-alpha>, <mailto:libc-alpha-request@sourceware.org?subject=subscribe> Cc: Emil Soleyman-Zomalan <emil@soleyman.com> Errors-To: libc-alpha-bounces+patchwork=sourceware.org@sourceware.org Sender: "Libc-alpha" <libc-alpha-bounces+patchwork=sourceware.org@sourceware.org> |
Series |
localedata: Add locale for syr_SY [BZ #27063]
|
|
Message
Emil Soleyman-Zomalan
Jan. 25, 2022, 1:33 a.m. UTC
Please add the Syriac language locale in the country of Syria. This follows the data and patterns setup in CLDR but not yet published: https://st.unicode.org/cldr-apps/v#/syr_SY/ I am also a contributor to the Unicode CLDR for Syriac. Author: Emil Soleyman-Zomalan <emil@soleyman.com> -- Emil Soleyman-Zomalan (2): Add locale for syr_SY Add syr_SY to the localedata apparatus localedata/Makefile | 1 + localedata/SUPPORTED | 1 + localedata/locales/syr_SY | 197 ++++++++++++++++++++++++++++++++++++++ 3 files changed, 199 insertions(+) create mode 100644 localedata/locales/syr_SY
Comments
Emil Soleyman-Zomalan <emil@soleyman.com> さんはかきました: > Please add the Syriac language locale in the country of Syria. This follows the data and patterns setup in CLDR but not yet published: https://st.unicode.org/cldr-apps/v#/syr_SY/ > > I am also a contributor to the Unicode CLDR for Syriac. > > Author: Emil Soleyman-Zomalan <emil@soleyman.com> Is this about classical Syriac (iso 639-3 code syc) or is this about modern Syriac: https://en.wikipedia.org/wiki/ISO_639_macrolanguage#syr Wikipedia> syr is the ISO 639-3 language code for Syriac. Wikipedia> There are two individual language codes assigned: Wikipedia> Wikipedia> aii – Assyrian Neo-Aramaic Wikipedia> cld – Chaldean Neo-Aramaic > LC_MONETARY > int_curr_symbol "XDR " > currency_symbol "¤" XDR is a quite weird currency code: https://en.wikipedia.org/wiki/Special_drawing_rights ¤ is the generic currency sign. If this is about the modern living language and if the country is SY, shouldn‘t the currency be Syrian pound?: https://en.wikipedia.org/wiki/Syrian_pound i.e. int_curr_symbol "SYP " currency_symbol "£S" https://github.com/unicode-org/cldr/blob/main/seed/main/syr.xml#L1086 has <currencies> <currency type="SYP"> <symbol draft="unconfirmed">ل.س.</symbol> </currency> </currencies> If the country is the modern Syria, then maybe add int_prefix "963" to LC_TELEPHONE ?
Mike FABIAN <mfabian@redhat.com> さんはかきました: > Emil Soleyman-Zomalan <emil@soleyman.com> さんはかきました: > >> Please add the Syriac language locale in the country of Syria. This >> follows the data and patterns setup in CLDR but not yet published: >> https://st.unicode.org/cldr-apps/v#/syr_SY/ >> >> I am also a contributor to the Unicode CLDR for Syriac. >> >> Author: Emil Soleyman-Zomalan <emil@soleyman.com> > > Is this about classical Syriac (iso 639-3 code syc) or is this about > modern Syriac: > > https://en.wikipedia.org/wiki/ISO_639_macrolanguage#syr > > Wikipedia> syr is the ISO 639-3 language code for Syriac. > Wikipedia> There are two individual language codes assigned: > Wikipedia> > Wikipedia> aii – Assyrian Neo-Aramaic > Wikipedia> cld – Chaldean Neo-Aramaic > >> LC_MONETARY >> int_curr_symbol "XDR " >> currency_symbol "¤" > > XDR is a quite weird currency code: > > https://en.wikipedia.org/wiki/Special_drawing_rights > > ¤ is the generic currency sign. > > If this is about the modern living language and if the country is SY, > shouldn‘t the currency be Syrian pound?: > > https://en.wikipedia.org/wiki/Syrian_pound > > i.e. > > int_curr_symbol "SYP " > currency_symbol "£S" > > https://github.com/unicode-org/cldr/blob/main/seed/main/syr.xml#L1086 > > has > > <currencies> > <currency type="SYP"> > <symbol draft="unconfirmed">ل.س.</symbol> > </currency> > </currencies> > > If the country is the modern Syria, then maybe add > > int_prefix "963" > > to LC_TELEPHONE > > ? And could you please also add a file localedata/syr_SY.UTF-8.in containing lines with characters and/or words in Syriac in the correct sort order?
On Wed, Apr 6, 2022, at 11:32, Mike FABIAN wrote: > > Is this about classical Syriac (iso 639-3 code syc) or is this about > modern Syriac: > > https://en.wikipedia.org/wiki/ISO_639_macrolanguage#syr > > Wikipedia> syr is the ISO 639-3 language code for Syriac. > Wikipedia> There are two individual language codes assigned: > Wikipedia> > Wikipedia> aii – Assyrian Neo-Aramaic > Wikipedia> cld – Chaldean Neo-Aramaic Syr covers both modern and classical as it is default for all literary Syriac. https://www.syriaca.org/documentation/isostandards.html >> LC_MONETARY >> int_curr_symbol "XDR " >> currency_symbol "¤" > > XDR is a quite weird currency code: > > https://en.wikipedia.org/wiki/Special_drawing_rights > > ¤ is the generic currency sign. > > If this is about the modern living language and if the country is SY, > shouldn‘t the currency be Syrian pound?: > > https://en.wikipedia.org/wiki/Syrian_pound > > i.e. > > int_curr_symbol "SYP " > currency_symbol "£S" > https://github.com/unicode-org/cldr/blob/main/seed/main/syr.xml#L1086 > > has > > <currencies> > <currency type="SYP"> > <symbol draft="unconfirmed">ل.س.</symbol> > </currency> > </currencies> > > If the country is the modern Syria, then maybe add > > int_prefix "963" > > to LC_TELEPHONE > > ? The only reason I have shied away from using the Syrian Pound and corresponding symbol as well as the telephone prefix as we have Syriac readers and writers throughout the Middle East including Iran, Iraq, Syria, Turkey and of course the diaspora. These locale settings will apply to all of these readers irrespective of their location. I have attempted to make it generic in that regard. I would appreciate any guidance though. ― Emil Soleyman-Zomalan
* Emil Soleyman-Zomalan: > The only reason I have shied away from using the Syrian Pound and > corresponding symbol as well as the telephone prefix as we have Syriac > readers and writers throughout the Middle East including Iran, Iraq, > Syria, Turkey and of course the diaspora. > > These locale settings will apply to all of these readers irrespective > of their location. I have attempted to make it generic in that regard. Should it be a country-less locale like eo? Thanks, Florian
On Wed, Apr 6, 2022, at 13:28, Florian Weimer wrote: > > Should it be a country-less locale like eo? I can tell you that Microsoft Windows has had a Syriac locale since Windows 8 and uses the Syrian Pound as a currency but no telephone prefix. Given that we are a country-less and region-less people, it might make sense to go with a country-less locale like eo. I know that there are pros and cons to this but nothing is coming to mind right now. ― Emil Soleyman-Zomalan
On Wed, Apr 6, 2022, at 14:10, Emil Soleyman-Zomalan wrote: > > I can tell you that Microsoft Windows has had a Syriac locale since > Windows 8 and uses the Syrian Pound as a currency but no telephone > prefix. > > Given that we are a country-less and region-less people, it might make > sense to go with a country-less locale like eo. I know that there are > pros and cons to this but nothing is coming to mind right now. > I have added the syr_SY.UTF-8.in file to bugzilla#27063. I would like to say let's move forward with the country-less version of the Syriac locale. ― Emil Soleyman-Zomalan, MD FAAEM
"Emil Soleyman-Zomalan" <emil@soleyman.com> さんはかきました: > On Wed, Apr 6, 2022, at 14:10, Emil Soleyman-Zomalan wrote: >> >> I can tell you that Microsoft Windows has had a Syriac locale since >> Windows 8 and uses the Syrian Pound as a currency but no telephone >> prefix. >> >> Given that we are a country-less and region-less people, it might make >> sense to go with a country-less locale like eo. I know that there are >> pros and cons to this but nothing is coming to mind right now. >> > > I have added the syr_SY.UTF-8.in file to bugzilla#27063. I would like > to say let's move forward with the country-less version of the Syriac > locale. I am working on adding this to glibc now. I used the locale attached to the bug and the syr_SY.UTF-8.in from the bug and renamed it to syr.UTF-8.in The sorting test case fails like this: syr.UTF-8 collate-test FAIL --- syr.UTF-8.in 2022-04-19 13:07:31.675953523 +0200 +++ /local/mfabian/src/glibc-build/localedata/syr.UTF-8.out 2022-04-19 14:42:15.977224807 +0200 @@ -1,14 +1,14 @@ ; Symbol Name Hex Code ; ------+------+---------------------------------------+--------+ -ܐ ; Syriac Letter Alaph U+0710 ܑ ; Syriac Letter Superscript Alaph U+0711 +ܐ ; Syriac Letter Alaph U+0710 ܒ ; Syriac Letter Beth U+0712 ܭ ; Syriac Letter Persian Bheth U+072D ܓ ; Syriac Letter Gamal U+0713 ܔ ; Syriac Letter Gamal Garshuni U+0714 ܮ ; Syriac Letter Persian Ghamal U+072E -ܕ ; Syriac Letter Dalath U+0715 ܖ ; Syriac Letter Dotless Dalath Rish U+0716 +ܕ ; Syriac Letter Dalath U+0715 ܯ ; Syriac Letter Persian Dhalath U+072F ܗ ; Syriac Letter He U+0717 ܘ ; Syriac Letter Waw U+0718 Your locale uses LC_COLLATE copy "iso14651_t1" END LC_COLLATE i.e. it includes the file with the default Unicode collation. Your test file has two characters in a different order. If the default Unicode collation order is OK for you, I would fix the test file accordingly (My preferred solution, I would deviate from the default only if necessary). If these two characters really should be ordered as in your test file, I would add extra rules to the LC_COLLATE section to achieve that: LC_COLLATE copy "iso14651_t1" ... more rules here ... END LC_COLLATE But that is extra effort and I wonder whether this is needed. There is no collation information in CLDR yet, no file common/collation/syr.xml exists currently in CLDR. You said you are also the contributor to the Unicode CLDR for Syriac. But you didn’t add a collation file there. If that means the default order is OK, then just doing LC_COLLATE copy "iso14651_t1" END LC_COLLATE should be enough and I should fix the test file.
On Tue, Apr 19, 2022, at 08:43, Mike FABIAN wrote: > > I am working on adding this to glibc now. I used the locale attached to > the bug and the syr_SY.UTF-8.in from the bug and renamed it to > syr.UTF-8.in ... > But that is extra effort and I wonder whether this is needed. > There is no collation information in CLDR yet, no file > > common/collation/syr.xml > > exists currently in CLDR. > > You said you are also the contributor to the Unicode CLDR for Syriac. > But you didn’t add a collation file there. If that means the default > order is OK, then just doing > > LC_COLLATE > copy "iso14651_t1" > END LC_COLLATE > > should be enough and I should fix the test file. I have fixed the test file because the ordering won't make a difference in the end for those two letters and should not fail now (hopefully). I'm working on getting the collation setup with CLDR during their next submission cycle that starts on May 18. I have updated bugzilla. Thank you for your help! ― Emil Soleyman-Zomalan
"Emil Soleyman-Zomalan" <emil@soleyman.com> さんはかきました:
> I have updated bugzilla.
Thank you, looks good to me, except the second line in the test file:
; Symbol Name Hex Code
; ------+------+---------------------------------------+--------+
ܑ ; Syriac Letter Superscript Alaph U+0711
still makes the test fail because "; S" sorts after "; -".
I removed that line and attached an updated patch to
https://sourceware.org/bugzilla/show_bug.cgi?id=27063
https://sourceware.org/bugzilla/attachment.cgi?id=14074
I think this looks good and I can commit it.
On Wed, Apr 20, 2022, at 10:59, Mike FABIAN wrote: > I removed that line and attached an updated patch to > > https://sourceware.org/bugzilla/show_bug.cgi?id=27063 > https://sourceware.org/bugzilla/attachment.cgi?id=14074 > > I think this looks good and I can commit it. Thank you for all of your help. I appreciate it greatly. ― Emil Soleyman-Zomalan