about summary refs log tree commit diff
path: root/localedata/locales
Commit message (Collapse)AuthorAgeFilesLines
* locledata: trim trailing blank lines/commentsMike Frysinger2016-02-1833-39/+0
| | | | No functional changes, just trying to standardize the format a bit.
* localedata: convert all files to utf-8Mike Frysinger2016-02-0814-146/+146
| | | | | The comments were using various encodings like ISO-8859-1. Convert them all over to UTF-8.
* localedata: nl_NL: date_fmt: rewrite to match standards [BZ #16495]Evert2016-01-081-3/+5
| | | | Add some references to public Dutch standards.
* localedata: nl_NL@euro: copy measurement from nl_NL [BZ #19198]Mike Frysinger2015-12-291-2/+1
| | | | | No real changes here as the output is the same. Just making the input a little bit nicer.
* localedata: bg_BG: use colon as time separator [BZ #19385]Damyan Ivanov2015-12-291-2/+2
| | | | | | | | | | | | | The only official source is the "Official spelling dictionary of the Bulgarian language, Prosveta 2012", which states there are three ways to separate time components: comma, colon and dot. That same dictionary doesn't say which one is preferred. So I turned to the mailing list of the translators of free software in Bulgarian. The consensus is that colon is the only separator that is widely used in Bulgarian texts and everything else will just be confusing. URL: http://lists.ludost.net/pipermail/dict/2015-December/000538.html
* Automate LC_CTYPE generation for tr_TR, update to Unicode 8.0.0 (bug 18491).Joseph Myers2015-12-111-1027/+1789
| | | | | | | | | | | | | | | | | | | | This patch makes the automation of Unicode LC_CTYPE generation also support generating the modified LC_CTYPE used for Turkish (where case conversions of 'i' and 'I' differ from ASCII conventions), so allowing that to be more readily kept in sync for future Unicode updates. The patch includes the locale update generated by the scripts. Tested for x86_64. [BZ #18491] * unicode-gen/unicode_utils.py (to_upper_turkish): New function. (to_lower_turkish): Likewise. * unicode-gen/gen_unicode_ctype.py (output_tables): Support producing output with Turkish case conversions. (--turkish): New command-line option. * unicode-gen/Makefile (GENERATED): Add tr_TR. (tr_TR): New rule. * locales/tr_TR: Regenerate LC_CTYPE.
* Update to Unicode 8.0.0.Mike FABIAN2015-12-107-1086/+1262
| | | | | | Update __STDC_ISO_10646__ to 201505L for Unicode 8.0.0. Update character encoding, ctype, and transliteration tables. New scripts autogenerate transliteration tables.
* Update da, nb, nn, and sv locales (Bug 89)Mike FABIAN2015-12-093-3/+62
| | | | Add transliteration rules for da, nb, nn, and sv locales.
* Update transliteration support to Unicode 7.0.0.Carlos O'Donell2015-12-096-48/+1784
| | | | | The transliteration files are now autogenerated from upstream Unicode data.
* Generic updates to transliterations.Mike FABIAN2015-12-091-5/+465
| | | | | | | | | | | | | | | - Remove duplicate transliterations for U+0152 and U+0153 from C-translit.h.in. - Change Ö U+00D6 LATIN CAPITAL LETTER O WITH STROKE → O (instead of → OE) - Change ö U+00F6 LATIN SMALL LETTER O WITH STROKE → o (instead of → oe) - Add ₹ U+20B9 INDIAN RUPEE SIGN → INR - Add ₫ U+20AB DONG SIGN → Dong (in addition to "₫ → Đồng") - Add many others from http://unicode.org/cldr/trac/browser/trunk/common/transforms/Latin-ASCII.xml - Add some more currency signs suggested by Marko Myllynen - Add another patch with more characters by Marko Myllynen
* lt_LT: change currency symbol to the euro [BZ #18953]Gunnar Hjalmarsson2015-10-171-2/+2
| | | | Lithuania switched currency to the Euro on 1st Jan 2015.
* hu_HU: change time separator to colon [BZ #18918]Egmont Koblinger2015-10-171-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous (11th) version of the Hungarian spelling rules (released in 1984) said that the separator had to be a dot, e.g. 10.35 meaning 10 o'clock 35 minutes. glibc correctly implements this. The brand new (12th) version, in effect since September 1, 2015 adopts to the common use of colon (especially in the digital world) and allows to use either separator, without even expressing a preference. For computer systems, using colons is way more typical and probably easier to recognize. Dot is typically used in printed materials. It also avoids an almost ambiguous situation where a space makes a difference, e.g. "10.15-ig" means "until 10 o'clock 15 minutes" whereas "10. 15-ig" means "until 15th of October". So I believe using the colon as the separator is not only more frequent in the computer world, but is also easier and quicker to recognize for the brain that it's about hour:minute rather than month and day. And luckily it's now equally correct according to the official rules. 11th edition: http://helyesiras.mta.hu/helyesiras/default/akh11 12th edition: http://helyesiras.mta.hu/helyesiras/default/akh12 In both editions it's the very last (299th and 300th, respectively) rule. Microsoft also uses and recommends a colon since at least May 2011: http://download.microsoft.com/download/e/6/1/e61266b2-d8b4-4fe0-a553-f01dc3976675/hun-hun-StyleGuide.pdf The time format is different in common language and in the language of IT. In common texts we usually do not abbreviate, so the full forms are used: “7 óra 10 perckor csörgött a telefon”. However, the short format, consisting of numerals only, can also be used. In this case a period must be used between the two numbers and there must not be a space between them: “találkozzunk 10.45-kor”. However, in software mostly the short format is used, and the numbers are separated by a colon. An obvious example is the clock in the bottom right corner of your screen, thus 18:31.
* Fix lang_lib/lang_term as per ISO 639-2 [BZ #16973]Marko Myllynen2015-08-189-12/+25
| | | | | | | | | | lang_lib (which reflects ISO 639-2/B (bibliographic) codes) and lang_term (which reflects ISO 639-2/T (terminology) codes) should be identical except for those languages for which ISO 639-2 specifies separate bibliographic/terminology values. I used this Library of Congress page as the source: http://www.loc.gov/standards/iso639-2/php/code_list.php
* locales/ce_RU: sync with other *_RU localesArslanbek Astemirov2015-08-071-6/+4
| | | | | | | [BZ #18618] * locales/ce_RU (LC_IDENTIFICATION): Fix language. (LC_TIME): Set first_weekday and first_workday. (LC_NUMERIC): Copy ru_RU.
* localedata: remove timezone information [BZ #18525]Marko Myllynen2015-08-056-35/+0
| | | | | | | | | | as discussed in the thread starting at https://sourceware.org/ml/libc-alpha/2015-06/msg00098.html it looks like the best options is to remove locale timezone information from locales which currently provide it (in incomplete or incorrect fashion) rather than to start duplicating tzdata info in glibc.
* locale: Remove obsolete repertoire map referencesMarko Myllynen2015-07-2163-64/+0
| | | | | | | | repertoire maps and character mnemonics were used early in the glibc i18n/l10n effort but were quickly deprecated in favor of Unicode code points. According to ChangeLog, the in-tree repertoire maps were removed 2000-07-07 but some stray references remain even today. The patch below removes them.
* locale: Do not define lang_ab for tcy_IN and bhb_INKhem Raj2015-07-212-2/+2
| | | | | | | | | After renaming localedef now complains and build fails LC_ADDRESS: field `lang_ab' must not be defined earlier the names were similar to lang_ab definitions 'tu' or 'bh' but after rename they are not.
* Correcting language code for Bhili and Tulu locales (bug 17475)Pravin Satpute2015-07-152-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | Bhili [1] and Tulu [2] language does not have iso-639-1 codes. Patch moves locale file with correct code and also fix iso-639.def. 1. http://www-01.sil.org/iso639-3/documentation.asp?id=bhb 2. http://www-01.sil.org/iso639-3/documentation.asp?id=tcy localedata/ChangeLog: 2015-07-02 Pravin Satpute <psatpute@redhat.com> [BZ #17475] * locales/tu_IN: renamed to tcy_IN * locales/bh_IN: renamed to bhb_IN Changelog: 2015-03-05 Pravin Satpute <psatpute@redhat.com> [BZ #17475] * locale/iso-639.def: Update Bhili and Tulu language codes as per iso639-3.
* Fix sorting order for Ukrainian locale (BZ 17293)Andriy Rysin2015-05-261-62/+4
| | | | | | | | | | | | | In the introduction for the official orthography rules for Ukrainian language (http://spelling.ulif.org.ua/peredmova.htm) there's a note that only apostrophe does not affect order of the words when sorting. As could be seen from the official alphabet the soft sign (U+044C/U+042C) has its hard position and thus affects the order and also letters "е" and "є" (CYR-IE: U+0435/U+0415 and UKR-IE: U+0454/U+0404) have their own positions and should have separate place when sorting. This also corresponds to official Unicode collation chart for these letters: http://unicode.org/charts/collation/chart_Cyrillic.html
* Fix bo_CN and bo_IN.Marko Myllynen2015-05-162-2/+2
| | | | | | Both bo_CN and bo_IN were not compiling. The following fix gets them into a usable state again giving a clean build result for `make localedata/install-locales`.
* Update currency_symbol in da_DKChristian Schmidt2015-05-071-1/+1
|
* Unicode 7.0.0 update; added generator scripts.Alexandre Oliva2015-02-201-1224/+1428
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | for localedata/ChangeLog [BZ #17588] [BZ #13064] [BZ #14094] [BZ #17998] * unicode-gen/Makefile: New. * unicode-gen/unicode-license.txt: New, from Unicode. * unicode-gen/UnicodeData.txt: New, from Unicode. * unicode-gen/DerivedCoreProperties.txt: New, from Unicode. * unicode-gen/EastAsianWidth.txt: New, from Unicode. * unicode-gen/gen_unicode_ctype.py: New generator, from Mike FABIAN <mfabian@redhat.com>. * unicode-gen/ctype_compatibility.py: New verifier, from Pravin Satpute <psatpute@redhat.com> and Mike FABIAN. * unicode-gen/ctype_compatibility_test_cases.py: New verifier module, from Mike FABIAN. * unicode-gen/utf8_gen.py: New generator, from Pravin Satpute and Mike FABIAN. * unicode-gen/utf8_compatibility.py: New verifier, from Pravin Satpute and Mike FABIAN. * charmaps/UTF-8: Update. * locales/i18n: Update. * gen-unicode-ctype.c: Remove. * tst-ctype-de_DE.ISO-8859-1.in: Adjust, islower now returns true for ordinal indicators.
* New locale raj_IN (#16857)Pravin Satpute2014-12-011-0/+177
|
* New locale ce_RU (BZ #17192)Pravin Satpute2014-12-011-0/+169
|
* New Bhilodi and Tulu locales (BZ #17475)Tatiana Udalova2014-11-122-0/+374
|
* Add lang_name to various locales.Chris Leonard2013-12-2611-1/+21
|
* Add lang_name to various locales.Chris Leonard2013-12-2010-1/+19
|
* Add entries for U00D8 and U00F8.Toke Høiland-Jørgensen2013-12-121-0/+4
|
* Fix Charset comment in fi_FI, fi_FI@euroMarko Myllynen2013-12-122-2/+2
|
* Add lang_name to various locales.Chris Leonard2013-12-0118-4/+36
|
* Add lang_name to various locales.Chris Leonard2013-11-2715-6/+45
|
* revert hebrew lang_name additionChris Leonard2013-11-251-1/+0
|
* Add lang_name to various locales.Chris Leonard2013-11-2515-0/+29
|
* Add lang_name to various locales.Chris Leonard2013-11-2421-3/+40
|
* revert error-generated by bs_BA.Chris Leonard2013-11-231-2/+0
|
* Add lang_name to various locales.Chris Leonard2013-11-2310-4/+35
|
* Add lang_name to various locales.Chris Leonard2013-11-236-0/+13
|
* Add lang_name to German, English, Spanish, French locales.Chris Leonard2013-11-2246-0/+87
|
* Add lang_name to Arabic locales.Chris Leonard2013-11-2119-0/+19
|
* Rename Oriya locale to Odia (bug 15601)Siddhesh Poyarekar2013-11-201-5/+5
| | | | | | | | | | | | The state of Orissa was officially renamed the state to Odisha and the language from Oriya to Odia in 2010. References: http://zeenews.india.com/election09/story.aspx?aid=739995 http://orissamatters.com/2011/11/07/orissa-became-odisha/ http://www.ndtv.com/article/india/parliament-passes-bill-to-change-orissa-s-name-93888 http://orissa.gov.in/e-magazine/Orissareview/2011/Nov/engpdf/9-17.pdf
* [BZ #16144] Duplicated abday value for tk_TM.Chris Leonard2013-11-181-4/+0
|
* Correct wae_CH to UTF-8 encoding.Chris Leonard2013-11-171-8/+8
|
* New locale for the_NP.Arun Kumar Pyasi2013-11-151-0/+230
|
* [BZ #16143] pap_* locales have duplicated LC_NUMERIC section.Chris Leonard2013-11-143-18/+0
|
* [BZ #16103] LC_MEASUREMENT review and standardizationChris Leonard2013-11-14303-615/+748
|
* Adjust language-code fields of LC_ADDRESS.Chris Leonard2013-11-042-5/+4
|
* Adjust language-code fields of LC_ADDRESS.Chris Leonard2013-11-0328-40/+146
|
* Adjust language-code fields of LC_ADDRESS.Chris Leonard2013-11-0324-50/+154
|
* Adjust language-code fields of LC_ADDRESS.Chris Leonard2013-11-0112-9/+54
|
* Adjust language-code fields of LC_ADDRESS.Chris Leonard2013-10-3110-7/+52
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-26 06:22:10 +0000