| Summary: | kab_DZ: new Kabyle Algeria locale | ||
|---|---|---|---|
| Product: | glibc | Reporter: | Claude Paroz <claude> |
| Component: | localedata | Assignee: | Mike FABIAN <maiku.fabian> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | belkacem77, carlos, cjlhomeaddress, libc-locales, maiku.fabian, slimane.amiri |
| Priority: | P2 | Flags: | fweimer:
security-
|
| Version: | unspecified | ||
| Target Milestone: | 2.27 | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Attachments: |
Kabyle locale file
Revised Kabyle locale file CLDR Kabyle - Beta release (32) kab_DZ attachment-57087-0.html |
||
Comment on attachment 8507 [details] Kabyle locale file >comment_char % >escape_char / please use the same header as other current locales: https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/en_US copy the first ~10 lines over >LC_IDENTIFICATION >title "Kabyle locale for Algeria" should be: Kabyle language locale for Algeria >category "kab_DZ:2000";LC_IDENTIFICATION >category "kab_DZ:2000";LC_CTYPE >category "kab_DZ:2000";LC_COLLATE >category "kab_DZ:2000";LC_TIME >category "kab_DZ:2000";LC_NUMERIC >category "kab_DZ:2000";LC_MONETARY >category "kab_DZ:2000";LC_PAPER >category "kab_DZ:2000";LC_MEASUREMENT >category "kab_DZ:2000";LC_MESSAGES >category "kab_DZ:2000";LC_NAME >category "kab_DZ:2000";LC_ADDRESS >category "kab_DZ:2000";LC_TELEPHONE these are all incorrect -- just copy them from en_US (see the link above) >LC_TIME >% yennayer, Furar, MeÉ£res, Ibrir, Maggu, Yunyu, Yulyu, Æuct, Cutembir, Tuber, Unbir, Dujenbir delete all these comments that just translate the <Uxxx> values. we've been dropping them from locales. >% Accer, Arim, Aram, Ahad, Amhad, Ssem, Ssed >day "<U0041><U0063><U0063><U0065><U0072>";/ just to be sure -- the first day here is Sunday right ? you should also define week in LC_TIME: week 7;19971130;1 >LC_MONETARY please define currency_symbol too >LC_PAPER >height 297 >width 210 >END LC_PAPER > >LC_MEASUREMENT >% metric >measurement 1 >END LC_MEASUREMENT copy ber_DZ for both of these >LC_MESSAGES >% ^[iIyY].* >yesexpr "<U005E><U005B><U0069><U0049><U0079><U0059><U005D><U002E><U002A>" >% ^[aAnN].* >noexpr "<U005E><U005B><U0061><U0041><U006E><U004E><U005D><U002E><U002A>" >END LC_MESSAGES these should be: yesexpr "^[+1yYiI]" noexpr "^[-0nNaA]" >LC_NAME >END LC_NAME please fill out all the fields here >country_num 12 this should be 012 >country_car "<U0041>" pretty sure this should be DZ >LC_TELEPHONE >% 213 >int_prefix "<U0032><U0031><U0033>" >END LC_TELEPHONE can you fill out the other fields here please ? Thanks Mike for the excellent review! >>LC_NAME >>END LC_NAME >please fill out all the fields here What do you mean by "all the fields"? Is this list: name_fmt, name_miss, name_mr, name_mrs, name_ms? (In reply to Claude Paroz from comment #2) those 5 fields, and name_gen. not all languages have concepts/translations for all the fields, but it seems unlikely that this one has none. Created attachment 9380 [details]
Revised Kabyle locale file
I just uploaded a revised file, status should be updated. (In reply to Claude Paroz from comment #5) > I just uploaded a revised file, status should be updated. Yes, this looks like it is ready for commit. - cjl The bug is still new? Please Would you like commit? If there is something wrong, let me know. I'am a Kabyle native and opensource kab localizer. (In reply to Belkacem Mohammed from comment #7) > The bug is still new? Please Would you like commit? > If there is something wrong, let me know. I'am a Kabyle native and > opensource kab localizer. My apologies. Commits for new locales only happen when you're working directly with a community developer that can commit this code for you. Maintainers are listed here: https://sourceware.org/glibc/wiki/MAINTAINERS. The review by Chris Leonard in comment #6 is proof enough that kab_DZ should be ready for commit. Chris is known in the community and has reviewed such patches in the past (though he is not a glibc developer). Have you been using the new kab_DZ locale? Is it working well? Does it match what is being submitted here? Which distro is including the locale? Hello, Thanks for help. I can't understand much more about technical devs . I followed a link when I was trying to start the kab locale for openSUSE. The kab localization of openSUSE is now ongoing but, it seems that we need kab on glibc to release our locale. We are also working on the kab locale on CLDR (please see http://st.unicode.org/cldr-apps/v#/kab/). You will find all needed data. The kab locale is now available on all Mozilla products and content (Firefox, Thudenrbird..), Odoo and much more. Note the iso 639-2 code of the Kabyle language is kab. Kab-DZ is same as kab. There is no other variant for our language. Please, let me know if you need more information Thank you The locale file was approved by Chris, a known glibc language reviewer more than a year ago. I struggle to find reasons for why this file was not yet committed. :) It took a lot of time. If there is something wrong with the file, somethig we can add, please let us know. thanks for help M. Belkacem Kabyle Software localizer https://translatewiki.net/wiki/User:Belkacem77 (In reply to Belkacem Mohammed from comment #9) > Hello, > Thanks for help. > > I can't understand much more about technical devs . I followed a link when I > was trying to start the kab locale for openSUSE. > > The kab localization of openSUSE is now ongoing but, it seems that we need > kab on glibc to release our locale. > > We are also working on the kab locale on CLDR (please see > http://st.unicode.org/cldr-apps/v#/kab/). You will find all needed data. The day and month names in your locale do not agree with what CLDR has. You have: mon "yennayer";/ "Furar";/ "Meɣres";/ "Ibrir";/ "Maggu";/ "Yunyu";/ "Yulyu";/ "Ɣuct";/ "Cutembir";/ "Tuber";/ "Unbir";/ "Dujenbir" abmon "yen.";/ "fur.";/ "meɣ.";/ "ibr.";/ "mag.";/ "yun.";/ "yul.";/ "ɣuc.";/ "cut.";/ "tub.";/ "unb.";/ "duj.";/ day "Accer";/ "Arim";/ "Aram";/ "Ahad";/ "Amhad";/ "Ssem";/ "Ssed" abday "ace.";/ "ari.";/ "ara.";/ "aha.";/ "amh.";/ "sem.";/ "sed." Compare with: http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml Why are there differences? What is correct? http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml contains: <posix> <messages> <yesstr>Ih:I</yesstr> <nostr>Uhu:U</nostr> </messages> </posix> but your locale contains: LC_MESSAGES yesexpr "^[+1yYiI]" noexpr "^[-0nNaA]" END LC_MESSAGES If CLDR is right, shouldn’t noexpr be: noexpr "^[-0nNuU]" Or is CLDR mistaken? Then one should fix it in CLDR ... We should probably also add yesstr "Ih" nostr "Uhu" or whatever the right words for "yes" and "no" are in Kabyle. int_curr_symbol should be 4 characters long and end with a space, like this: int_curr_symbol "DZD " The ar_DZ locale contains: first_weekday 7 first_workday 1 Is that also correct for kab_DZ, should we add it? Created attachment 10547 [details]
CLDR Kabyle - Beta release (32)
CLDR Kabyle - Beta release
We updated ( me and some academicians from Bejaia Univesity, and independant authors) some data in CLDR 32 that will be released next 1st November.
Note that the same data is currently used the kab locale of VK (social network), lighthning (Calendar on thanderbird), Evernote, Wikimedia, OpenStreetmap,.. and more other tools we localized into kabyle
Here are the common name used for months and days and their short forms:
These names are taught at School in Algeria (Kabylia). In fact, some authors use declination (other local forms). The forms below, are the most used.
mon "yennayer";/
"Fuṛar";/
"Meɣres";/
"Yebrir";/
"Mayyu";/
"Yunyu";/
"Yulyu";/
"Ɣuct";/
"Ctembeṛ";/
"Tubeṛ";/
"Wambeṛ";/
"Dujembeṛ"
abmon "yen.";/
"fur.";/
"meɣ.";/
"yeb.";/
"may.";/
"yun.";/
"yul.";/
"ɣuc.";/
"cte.";/
"tub.";/
"wam.";/
"duj.";/
day "Acer";/
"Arim";/
"Aram";/
"Ahad";/
"Amhad";/
"Sem";/
"Sed"
abday "ace.";/
"ari.";/
"ara.";/
"aha.";/
"amh.";/
"sem.";/
"sed."
(In reply to Mike FABIAN from comment #13) > http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml > > contains: > > <posix> > <messages> > <yesstr>Ih:I</yesstr> > <nostr>Uhu:U</nostr> > </messages> > </posix> > > > but your locale contains: > > LC_MESSAGES > yesexpr "^[+1yYiI]" > noexpr "^[-0nNaA]" > END LC_MESSAGES > > If CLDR is right, shouldn’t noexpr be: > > noexpr "^[-0nNuU]" > > Or is CLDR mistaken? Then one should fix it in CLDR ... > > > We should probably also add > > yesstr "Ih" > nostr "Uhu" > > or whatever the right words for "yes" and "no" are in Kabyle. yesstr "Ih" nostr "Uhu" Short form "Y" : "I" "N" : "U" (In reply to Mike FABIAN from comment #14) > int_curr_symbol should be 4 characters long and end with a space, like this: > > int_curr_symbol "DZD " yeah int_curr_symbol "DZD " (In reply to Mike FABIAN from comment #15) > The ar_DZ locale contains: > > first_weekday 7 > first_workday 1 > > Is that also correct for kab_DZ, should we add it? first_weekday 7 first_workday 1 Same as ar_DZ You use %p in t_fmt_ampm "%I:%M:%S %p" but you do not define: % % Strings for AM/PM % am_pm "AM";"PM" What are the appropriate strings to use for AM/PM in Kabyle? (In reply to Belkacem Mohammed from comment #18) > (In reply to Mike FABIAN from comment #13) > > http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml > > > > contains: > > > > <posix> > > <messages> > > <yesstr>Ih:I</yesstr> > > <nostr>Uhu:U</nostr> > > </messages> > > </posix> > > > > > > but your locale contains: > > > > LC_MESSAGES > > yesexpr "^[+1yYiI]" > > noexpr "^[-0nNaA]" > > END LC_MESSAGES > > > > If CLDR is right, shouldn’t noexpr be: > > > > noexpr "^[-0nNuU]" > > > > Or is CLDR mistaken? Then one should fix it in CLDR ... > > > > > > We should probably also add > > > > yesstr "Ih" > > nostr "Uhu" > > > > or whatever the right words for "yes" and "no" are in Kabyle. > > > yesstr "Ih" > nostr "Uhu" > > Short form > "Y" : "I" > "N" : "U" Then we should use noexpr "^[-0nNuU]" (u instead of a), right? (In reply to Mike FABIAN from comment #22) > (In reply to Belkacem Mohammed from comment #18) > > (In reply to Mike FABIAN from comment #13) > > > http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml > > > > > > contains: > > > > > > <posix> > > > <messages> > > > <yesstr>Ih:I</yesstr> > > > <nostr>Uhu:U</nostr> > > > </messages> > > > </posix> > > > > > > > > > but your locale contains: > > > > > > LC_MESSAGES > > > yesexpr "^[+1yYiI]" > > > noexpr "^[-0nNaA]" > > > END LC_MESSAGES > > > > > > If CLDR is right, shouldn’t noexpr be: > > > > > > noexpr "^[-0nNuU]" > > > > > > Or is CLDR mistaken? Then one should fix it in CLDR ... > > > > > > > > > We should probably also add > > > > > > yesstr "Ih" > > > nostr "Uhu" > > > > > > or whatever the right words for "yes" and "no" are in Kabyle. > > > > > > yesstr "Ih" > > nostr "Uhu" > > > > Short form > > "Y" : "I" > > "N" : "U" > > Then we should use > > noexpr "^[-0nNuU]" > > (u instead of a), right? yeah, u instead of a. ______ We have to ways to say No : Uhu(U), Ala(A). Uhu(u) is the most used. (In reply to Mike FABIAN from comment #21) > You use %p in > > t_fmt_ampm "%I:%M:%S %p" > > but you do not define: > > % > % Strings for AM/PM > % > am_pm "AM";"PM" > > What are the appropriate strings to use for AM/PM in Kabyle? type abbreviated: am: ft pm: md ___________ Type narrow am: f pm: m (In reply to Belkacem Mohammed from comment #17) > We updated ( me and some academicians from Bejaia Univesity, and independant > authors) some data in CLDR 32 that will be released next 1st November. > > Note that the same data is currently used the kab locale of VK (social > network), lighthning (Calendar on thanderbird), Evernote, Wikimedia, > OpenStreetmap,.. and more other tools we localized into kabyle > > Here are the common name used for months and days and their short forms: > > These names are taught at School in Algeria (Kabylia). In fact, some authors > use declination (other local forms). The forms below, are the most used. > > mon "yennayer";/ Why does this start with a lower case “y”? In CLDR trunk it is “Yennayer” with an uppercase “Y”. > "Fuṛar";/ > "Meɣres";/ > "Yebrir";/ > "Mayyu";/ > "Yunyu";/ > "Yulyu";/ > "Ɣuct";/ > "Ctembeṛ";/ > "Tubeṛ";/ > "Wambeṛ";/ > "Dujembeṛ" The above is the same as the "stand-alone" forms in CLDR but a little different from the locale as attached to this bug. So it is probably OK if I use the stuff from CLDR here. > abmon "yen.";/ > "fur.";/ > "meɣ.";/ > "yeb.";/ > "may.";/ > "yun.";/ > "yul.";/ > "ɣuc.";/ > "cte.";/ > "tub.";/ > "wam.";/ > "duj.";/ The stand-alone forms in CLDR trunk are: <monthContext type="stand-alone"> <monthWidth type="abbreviated"> <month type="1" draft="unconfirmed">Yen</month> <month type="2" draft="unconfirmed">Fur</month> <month type="3" draft="unconfirmed">Meɣ</month> <month type="4" draft="unconfirmed">Yeb</month> <month type="5" draft="unconfirmed">May</month> <month type="6" draft="unconfirmed">Yun</month> <month type="7" draft="unconfirmed">Yul</month> <month type="8" draft="unconfirmed">Ɣuc</month> <month type="9" draft="unconfirmed">Cte</month> <month type="10" draft="unconfirmed">Tub</month> <month type="11" draft="unconfirmed">Wam</month> <month type="12" draft="unconfirmed">Duj</month> </monthWidth> i.e. starting with upper case letters and without the final dot. OK to use it as in CLDR? > day "Acer";/ > "Arim";/ > "Aram";/ > "Ahad";/ > "Amhad";/ > "Sem";/ > "Sed" Same as in CLDR trunk. > abday "ace.";/ > "ari.";/ > "ara.";/ > "aha.";/ > "amh.";/ > "sem.";/ > "sed." CLDR trunk has: <dayContext type="stand-alone"> <dayWidth type="abbreviated"> <day type="sun" draft="unconfirmed">Ace</day> <day type="mon" draft="unconfirmed">Ari</day> <day type="tue" draft="unconfirmed">Ara</day> <day type="wed" draft="unconfirmed">Aha</day> <day type="thu" draft="unconfirmed">Amh</day> <day type="fri" draft="unconfirmed">Sem</day> <day type="sat" draft="unconfirmed">Sed</day> </dayWidth> I.e. starting with an upper case letter and without the final dot. OK to use it as in CLDR? (In reply to Belkacem Mohammed from comment #23) > > > > but your locale contains: > > > > > > > > LC_MESSAGES > > > > yesexpr "^[+1yYiI]" > > > > noexpr "^[-0nNaA]" > > > > END LC_MESSAGES > > > > > > > > If CLDR is right, shouldn’t noexpr be: > > > > > > > > noexpr "^[-0nNuU]" > > > > > > > > Or is CLDR mistaken? Then one should fix it in CLDR ... > > > > > > > > > > > > We should probably also add > > > > > > > > yesstr "Ih" > > > > nostr "Uhu" > > > > > > > > or whatever the right words for "yes" and "no" are in Kabyle. > > > > > > > > > yesstr "Ih" > > > nostr "Uhu" > > > > > > Short form > > > "Y" : "I" > > > "N" : "U" > > > > Then we should use > > > > noexpr "^[-0nNuU]" > > > > (u instead of a), right? > > yeah, > > u instead of a. > ______ > We have to ways to say No : Uhu(U), Ala(A). Uhu(u) is the most used. We could also use noexpr "^[-0nNuUaA]" to make the letters uUaA all acceptable as "no" answers. There is no conflict with: yesexpr "^[+1yYiI]" In LC_ADDRESS country_name was missing, I added this country_name "Lezzayer" (taken from CLDR). (In reply to Mike FABIAN from comment #27) > In LC_ADDRESS country_name was missing, I added this > > country_name "Lezzayer" > > (taken from CLDR). No, the country name in Kabyle "Zzayer". I think, it's CLDR 31? We updated all the names in CLDR 32 but it's beta release now. <zone type="Africa/Algiers"> <exemplarCity>Zzayer</exemplarCity> </zone> (In reply to Mike FABIAN from comment #27) > In LC_ADDRESS country_name was missing, I added this > > country_name "Lezzayer" > > (taken from CLDR). And the country name: <territory type="DZ">Zzayer</territory> (In reply to Belkacem Mohammed from comment #29) > (In reply to Mike FABIAN from comment #27) > > In LC_ADDRESS country_name was missing, I added this > > > > country_name "Lezzayer" > > > > (taken from CLDR). > > And the country name: > > <territory type="DZ">Zzayer</territory> http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml#L560 has <territory type="DZ">Lezzayer</territory> That URL points to CLDR trunk, so this is *not* CLDR 31, it is the most recent stuff in the svn repository. (In reply to Mike FABIAN from comment #27) > In LC_ADDRESS country_name was missing, I added this > > country_name "Lezzayer" > > (taken from CLDR). No, the country name in Kabyle "Zzayer". I think, it's CLDR 31? We updated all the names in CLDR 32 but it's beta release now. Algeria (country) : <territory type="DZ">Zzayer</territory> ____________ Algiers (the city) : <zone type="Africa/Algiers"> <exemplarCity>Zzayer</exemplarCity> </zone> _____________ Currency (Algerian Dinar): <currency type="DZD"> <displayName>Adinar n Zzayer</displayName> <displayName count="one">Adinar n Zzayer</displayName> <displayName count="other">Idinaren n Zzayer</displayName> <symbol>DZD</symbol> </currency>(In reply to Mike FABIAN from comment #30) > (In reply to Belkacem Mohammed from comment #29) > > (In reply to Mike FABIAN from comment #27) > > > In LC_ADDRESS country_name was missing, I added this > > > > > > country_name "Lezzayer" > > > > > > (taken from CLDR). > > > > And the country name: > > > > <territory type="DZ">Zzayer</territory> > > http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml#L560 > > has > > <territory type="DZ">Lezzayer</territory> > > That URL points to CLDR trunk, so this is *not* CLDR 31, it is the > most recent stuff in the svn repository. We will correct it on CLDR. The right word for the country name is : Zzayer (In reply to Belkacem Mohammed from comment #31) > (In reply to Mike FABIAN from comment #27) > > In LC_ADDRESS country_name was missing, I added this > > > > country_name "Lezzayer" > > > > (taken from CLDR). > > No, the country name in Kabyle "Zzayer". I think, it's CLDR 31? No. > We updated > all the names in CLDR 32 but it's beta release now. https://www.unicode.org/repos/cldr/tags/release-32-beta/common/main/kab.xml has: <territory type="DZ">Lezzayer</territory> > > > > (taken from CLDR). > > > > > > And the country name: > > > > > > <territory type="DZ">Zzayer</territory> > > > > http://unicode.org/cldr/trac/browser/trunk/common/main/kab.xml#L560 > > > > has > > > > <territory type="DZ">Lezzayer</territory> > > > > That URL points to CLDR trunk, so this is *not* CLDR 31, it is the > > most recent stuff in the svn repository. > > We will correct it on CLDR. > The right word for the country name is : Zzayer Yes, please correct it there because it seems still wrong in the latest CLDR. Created attachment 10548 [details]
kab_DZ
The kab_DZ file I have edited.
Is it OK?
If yes, I’ll commit it.
If not, tell me what is still wrong.
(In reply to Mike FABIAN from comment #33) > Created attachment 10548 [details] > kab_DZ > > The kab_DZ file I have edited. > > Is it OK? > > If yes, I’ll commit it. > > If not, tell me what is still wrong. Right ok. I just reviewed it. Everything is rihgt This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via b6b08b8e21e8393089765b64a96953d215b3454c (commit)
from 9ba7e81028b3313d9aeb97a98d2e37626694d442 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b6b08b8e21e8393089765b64a96953d215b3454c
commit b6b08b8e21e8393089765b64a96953d215b3454c
Author: Mike FABIAN <mfabian@redhat.com>
Date: Fri Oct 20 17:50:40 2017 +0200
Add new locale kab_DZ [BZ #18812]
[BZ #18812]
* localedata/SUPPORTED: Add kab_DZ/UTF-8.
* localedata/locales/kab_DZ: New file.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 6 ++
localedata/SUPPORTED | 1 +
localedata/locales/kab_DZ | 168 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 175 insertions(+), 0 deletions(-)
create mode 100644 localedata/locales/kab_DZ
Fixed in glibc master. Thanks Mike \o/ Thanks for everyone Please would you like add my email address in the file for those who wants contact me? (In reply to Belkacem Mohammed from comment #39) > Please would you like add my email address in the file for those who wants > contact me? I did that now in git master. Created attachment 10567 [details] attachment-57087-0.html How is the work on the CLDR locale going? I'm trying to encourage some work on CLDR locale develop by some of the communities working on the SugarLabs Pootle instance and I'd like to know how easy it is to work with CLDR. cjl On Tue, Oct 24, 2017 at 4:44 AM, belkacem77 at gmail dot com < sourceware-bugzilla@sourceware.org> wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=18812 > > --- Comment #38 from Belkacem Mohammed <belkacem77 at gmail dot com> --- > Thanks for everyone > > -- > You are receiving this mail because: > You are on the CC list for the bug. > Hi Chris, For the kab locale, we built a team of localizers, translators. The kab locale is just being built. CLDR Kab is now growing. There are some parts we will complete with the next release (33). version 32 is released yesterday (01/11). A lot of keys are still unconfirmed due to voting mode (process) on CLDR. I'm trying to set up a team along with the 3 kab univesities to maintain the locale. We will focus on the next release on the keyboard templates, kabyle calendar, collations. |
Created attachment 8507 [details] Kabyle locale file Here is a new locale for the Kabyle language in Algeria.