[1/1] Added new Locale bho_NP

Bhojpuri is one the most common language in Nepal and India.
http://codefornepal.org/en/2014/02/top-10-languages-spoken-as-mother-tongues-in-nepal/
https://en.wikipedia.org/wiki/Bhojpuri_language

Added "bho_NP" locale and Reference is taken form "bho_IN".

[#BZ 21845]
* SUPPORTED: Add bho_NP
* locales/bho_NP: New file, Bhojpuri locale for Nepal.

---
 localedata/SUPPORTED      |    1 +
 localedata/locales/bho_NP |   92 +++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 93 insertions(+), 0 deletions(-)
 create mode 100644 localedata/locales/bho_NP

Akhilesh Kumar <akhilesh.k@samsung.com> さんはかきました:

> Bhojpuri is one the most common language in Nepal and India.
> http://codefornepal.org/en/2014/02/top-10-languages-spoken-as-mother-tongues-in-nepal/
> https://en.wikipedia.org/wiki/Bhojpuri_language
>
> Added "bho_NP" locale and Reference is taken form "bho_IN".
>
> [#BZ 21845]
  ^^^^^^^^^^^[BZ #21845]
              
> * SUPPORTED: Add bho_NP
> * locales/bho_NP: New file, Bhojpuri locale for Nepal.
>
> ---
>  localedata/SUPPORTED      |    1 +
>  localedata/locales/bho_NP |   92 +++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 93 insertions(+), 0 deletions(-)
>  create mode 100644 localedata/locales/bho_NP
>
> diff --git a/localedata/SUPPORTED b/localedata/SUPPORTED
> index 5a9df1b..6bb95a3 100644
> --- a/localedata/SUPPORTED
> +++ b/localedata/SUPPORTED
> @@ -65,6 +65,7 @@ bg_BG.UTF-8/UTF-8 \
>  bg_BG/CP1251 \
>  bhb_IN.UTF-8/UTF-8 \
>  bho_IN/UTF-8 \
> +bho_NP/UTF-8 \
>  bi_VU/UTF-8 \
>  bn_BD/UTF-8 \
>  bn_IN/UTF-8 \
> diff --git a/localedata/locales/bho_NP b/localedata/locales/bho_NP
> new file mode 100644
> index 0000000..3a09f87
> --- /dev/null
> +++ b/localedata/locales/bho_NP
> @@ -0,0 +1,92 @@
> +comment_char %
> +escape_char /
> +
> +% This file is part of the GNU C Library and contains locale data.
> +% The Free Software Foundation does not claim any copyright interest
> +% in the locale data contained in this file.  The foregoing does not
> +% affect the license of the GNU C Library as a whole.  It does not
> +% exempt you from the conditions of the license if your use would
> +% otherwise be governed by that license.
> +
> +% Bhojpuri language locale for Nepal.
> +% Akhilesh Kumar <akhilesh.k@samusng.com>.
> +
> +LC_IDENTIFICATION
> +title      "Bhojpuri language locale for Nepal"
> +source     "Samsung Electronics Co., Ltd."
> +address    ""
> +contact    ""
> +email      "akhilesh.k@samusng.com"
> +tel        ""
> +fax        ""
> +language   "Bhojpuri"
> +territory  "Nepal"
> +revision   "0.1"
> +date       "2017-24-07"
> +
> +category "i18n:2012";LC_IDENTIFICATION
> +category "i18n:2012";LC_CTYPE
> +category "i18n:2012";LC_COLLATE
> +category "i18n:2012";LC_TIME
> +category "i18n:2012";LC_NUMERIC
> +category "i18n:2012";LC_MONETARY
> +category "i18n:2012";LC_MESSAGES
> +category "i18n:2012";LC_PAPER
> +category "i18n:2012";LC_NAME
> +category "i18n:2012";LC_ADDRESS
> +category "i18n:2012";LC_TELEPHONE
> +category "i18n:2012";LC_MEASUREMENT
> +END LC_IDENTIFICATION
> +
> +LC_CTYPE
> +copy "ne_NP"
> +END LC_CTYPE

copy "bho_IN"

seems better, what do you think? The LC_CTYPE of ne_NP just does the
standard copy "i18n", copy "bho_IN" would do copy "hi_IN" which does
something with devanagari digits.

> +LC_COLLATE
> +copy "ne_NP"
> +END LC_COLLATE

copy "bho_IN" will give the identical result but seems more logical.

> +LC_MONETARY
> +copy "ne_NP"
> +END LC_MONETARY
> +
> +LC_NUMERIC
> +copy "ne_NP"
> +END LC_NUMERIC
> +
> +LC_TIME
> +copy "bho_IN"
> +END LC_TIME

OK.

> +LC_MESSAGES
> +copy "hi_IN"
> +END LC_MESSAGES

Maybe better copy "bho_IN"? Although it makes no difference here.

> +LC_PAPER
> +copy "ne_NP"
> +END LC_PAPER
> +
> +LC_NAME
> +copy "bho_IN"
> +END LC_NAME
> +
> +LC_ADDRESS
> +postal_fmt  "%f%N%h%s%N%T"
> +country_name "<U0928><U0947><U092A><U093E><U0932>"
> +country_ab2 "NP"
> +country_ab3 "NPL"
> +country_num 524
> +% NEP
> +country_car  "NEP"
> +lang_name    "<U092D><U094B><U091C><U092A><U0941><U0930><U0940>"
> +lang_term    "bho"
> +lang_lib     "bho"
> +END LC_ADDRESS
> +
> +LC_TELEPHONE
> +copy "ne_NP"
> +END LC_TELEPHONE
> +
> +LC_MEASUREMENT
> +copy "ne_NP"
> +END LC_MEASUREMENT

OK.

> > +category "i18n:2012";LC_COLLATE
> > +category "i18n:2012";LC_TIME
> > +category "i18n:2012";LC_NUMERIC
> > +category "i18n:2012";LC_MONETARY
> > +category "i18n:2012";LC_MESSAGES
> > +category "i18n:2012";LC_PAPER
> > +category "i18n:2012";LC_NAME
> > +category "i18n:2012";LC_ADDRESS
> > +category "i18n:2012";LC_TELEPHONE
> > +category "i18n:2012";LC_MEASUREMENT
> > +END LC_IDENTIFICATION
> > +
> > +LC_CTYPE
> > +copy "ne_NP"
> > +END LC_CTYPE
>  
> copy "bho_IN"
>  
> seems better, what do you think? The LC_CTYPE of ne_NP just does the
> standard copy "i18n", copy "bho_IN" would do copy "hi_IN" which does
> something with devanagari digits.
  
  Agree 
  
> > +LC_COLLATE
> > +copy "ne_NP"
> +END LC_COLLATE
> copy "bho_IN" will give the identical result but seems more logical.
  Agree   
> > +LC_MONETARY
> > +copy "ne_NP"
> > +END LC_MONETARY
> > +
> > +LC_NUMERIC
> > +copy "ne_NP"
> > +END LC_NUMERIC
> > +
> > +LC_TIME
> > +copy "bho_IN"
> > +END LC_TIME
>  
> OK.
>  
> > +LC_MESSAGES
> > +copy "hi_IN"
> > +END LC_MESSAGES
>  
> Maybe better copy "bho_IN"? Although it makes no difference here.

  Agree 
  All review Comments are integrated please find updated patch
  https://sourceware.org/ml/libc-alpha/2017-07/msg00948.html
  
> > +LC_PAPER
> > +copy "ne_NP"

Akhilesh