aboutsummaryrefslogtreecommitdiff
path: root/localedata/locales/km_KH
AgeCommit message (Collapse)Author
2016-04-12localedata: LC_MEASUREMENT: use copy directives everywhereMike Frysinger
There are only two measurement systems that locales use: US and metric. For the former, move to copying the en_US locale, while for the latter, move to copying the i18n locale. This lets us clean up all the stray comments like FIXME. There should be no functional differences here.
2016-03-21localedata: standardize copyright/license information [BZ #11213]Mike Frysinger
Use the language from the FSF in all locale files to disclaim any license/copyright on locale data. See https://sourceware.org/ml/libc-locales/2013-q1/msg00048.html
2016-03-21localedata: standardize first few linesMike Frysinger
Purely a style touchup to make sure the headers all look the same.
2016-02-19localedata: CLDRv28: update LC_TELEPHONE.int_prefixMike Frysinger
This updates a bunch of locales based on CLDR v28 data: ar_SS: int_prefix: changing 249 to 211 bn_BD: int_prefix: changing 88 to 880 dz_BT: int_prefix: changing 66 to 975 en_HK: int_prefix: changing to 852 en_PH: int_prefix: changing to 63 en_SG: int_prefix: changing to 65 es_DO: int_prefix: changing 1809 to 1 es_PA: int_prefix: changing 502 to 507 es_PR: int_prefix: changing 1787 to 1 km_KH: int_prefix: changing 856 to 855 mt_MT: int_prefix: changing to 356 ne_NP: int_prefix: changing 91 to 977 pap_AW: int_prefix: changing 599 to 297 the_NP: int_prefix: changing 91 to 977 tk_TM: int_prefix: changing to 993 uz_UZ: int_prefix: changing 27 to 998 zh_SG: int_prefix: changing to 65 I've also checked these against https://countrycode.org/. Note: the Dominican Republic (DO) and Puerto Rico (PR) updates are correct: they both use +1. Historically, DO had one area code of 809 and PR of 787 which is why they were listed as such, but they have both expanded into 829 and 989 respectively, so using the four digit value is def incorrect now.
2015-08-18Fix lang_lib/lang_term as per ISO 639-2 [BZ #16973]Marko Myllynen
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
2015-08-05localedata: remove timezone information [BZ #18525]Marko Myllynen
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.
2013-11-14[BZ #16103] LC_MEASUREMENT review and standardizationChris Leonard
2012-11-15Correct L10n of country-name and lang-name in km_KHChris Leonard
[BZ #13952] * locales/km_KH: Correct country-name and lang-name.
2006-07-30* locale/programs/localedef.c (add_to_readlist): Rename localUlrich Drepper
variables to avoid confusion. * locale/programs/charmap.c (charmap_read): Emit error message if charmap couldn't be found or read.
2005-09-25[BZ #714]Ulrich Drepper
2005-09-25 Ulrich Drepper <drepper@redhat.com> [BZ #714] * iconv/loop.c [!STORE_REST] (SINGLE): Correctly record number of left-over bytes and store them correctly. * iconvdata/tst-iconv6.c: New file. * iconvdata/Makefile (tests): Add tst-iconv6.
2004-12-22(CFLAGS-tst-align.c): Add -mpreferred-stack-boundary=4.Ulrich Drepper
2007-07-122.5-18.1Jakub Jelinek