[PATCH] New locale mag_IN

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[PATCH] New locale mag_IN

Petr Baudis
http://sourceware.org/bugzilla/show_bug.cgi?id=13968
(Patch slightly fixed up.)

Add new locale mag_IN.

Ok to commit?

2012-04-20  Chandan Kumar  <[hidden email]>

        [BZ#13968]
        * locales/mag_IN: New file.
        * SUPPORTED (SUPPORTED-LOCALES): Add appropriate entry.

diff --git a/localedata/SUPPORTED b/localedata/SUPPORTED
index 1fd7847..4010a21 100644
--- a/localedata/SUPPORTED
+++ b/localedata/SUPPORTED
@@ -285,6 +285,7 @@ lt_LT.UTF-8/UTF-8 \
 lt_LT/ISO-8859-13 \
 lv_LV.UTF-8/UTF-8 \
 lv_LV/ISO-8859-13 \
+mag_IN/UTF-8 \
 mai_IN/UTF-8 \
 mg_MG.UTF-8/UTF-8 \
 mg_MG/ISO-8859-15 \
diff --git a/localedata/locales/mag_IN b/localedata/locales/mag_IN
new file mode 100644
index 0000000..8a1f973
--- /dev/null
+++ b/localedata/locales/mag_IN
@@ -0,0 +1,167 @@
+comment_char    %
+escape_char     /
+% Magahi language locale for India.
+% Contributed by Chandan Kumar <[hidden email]>, Rajesh Ranjan <[hidden email]>
+% and Pravin Satpute <[hidden email]>
+
+LC_IDENTIFICATION
+title      "Magahi language locale for India"
+source     ""
+address    ""
+contact    ""
+email      "[hidden email]"
+tel        ""
+fax        ""
+language   "Magahi"
+territory  "India"
+revision   "0.1"
+date       "2012-04-11"
+%
+category  "mag_IN:2012";LC_IDENTIFICATION
+category  "mag_IN:2012";LC_CTYPE
+category  "mag_IN:2012";LC_COLLATE
+category  "mag_IN:2012";LC_TIME
+category  "mag_IN:2012";LC_NUMERIC
+category  "mag_IN:2012";LC_MONETARY
+category  "mag_IN:2012";LC_MESSAGES
+category  "mag_IN:2012";LC_PAPER
+category  "mag_IN:2012";LC_NAME
+category  "mag_IN:2012";LC_ADDRESS
+category  "mag_IN:2012";LC_TELEPHONE
+
+END LC_IDENTIFICATION
+
+LC_CTYPE
+copy "hi_IN"
+END LC_CTYPE
+
+LC_COLLATE
+copy "hi_IN"
+END LC_COLLATE
+
+LC_MONETARY
+copy "hi_IN"
+END LC_MONETARY
+
+
+LC_NUMERIC
+copy "hi_IN"
+END LC_NUMERIC
+
+
+LC_TIME
+% This is the POSIX Locale definition for the LC_TIME category.
+% These are generated based on XML base Locale definition file
+% for IBM Class for Unicode/Java
+%
+% Abbreviated weekday names (%a)
+abday       "<U090F><U0924><U0935><U093E><U0930><U0020>";/
+            "<U0938><U094B><U092E><U093E><U0930><U0020>";/
+            "<U092E><U0902><U0917><U0930><U0020>";/
+            "<U092C><U0941><U0927><U0020>";/
+            "<U092C><U093F><U092B><U0947><U0020>";/
+            "<U0938><U0942><U0915><U0020>";/
+            "<U0938><U0928><U093F><U091A><U0930><U0020>"
+%
+% Full weekday names (%A)
+day         "<U090F><U0924><U0935><U093E><U0930><U0020>";/
+            "<U0938><U094B><U092E><U093E><U0930><U0020>";/
+            "<U092E><U0902><U0917><U0930><U0020>";/
+            "<U092C><U0941><U0927><U0020>";/
+            "<U092C><U093F><U092B><U0947><U0020>";/
+            "<U0938><U0942><U0915><U0020>";/
+            "<U0938><U0928><U093F><U091A><U0930><U0020>"
+%
+% Abbreviated month names (%b)
+abmon       "<U091C><U0928><U0935><U0930><U0940>";/
+            "<U092B><U093C><U0930><U0935><U0930><U0940>";/
+            "<U092E><U093E><U0930><U094D><U091A>";/
+            "<U0905><U092A><U094D><U0930><U0947><U0932>";/
+            "<U092E><U0908>";"<U091C><U0942><U0928>";/
+            "<U091C><U0941><U0932><U093E><U0908>";/
+            "<U0905><U0917><U0938><U094D><U0924>";/
+            "<U0938><U093F><U0924><U092E><U094D><U092C><U0930>";/
+            "<U0905><U0915><U094D><U091F><U0942><U092C><U0930>";/
+            "<U0928><U0935><U092E><U094D><U092C><U0930>";/
+            "<U0926><U093F><U0938><U092E><U094D><U092C><U0930>"
+%
+% Full month names (%B)
+mon         "<U091C><U0928><U0935><U0930><U0940>";/
+            "<U092B><U093C><U0930><U0935><U0930><U0940>";/
+            "<U092E><U093E><U0930><U094D><U091A>";/
+            "<U0905><U092A><U094D><U0930><U0947><U0932>";/
+            "<U092E><U0908>";"<U091C><U0942><U0928>";/
+            "<U091C><U0941><U0932><U093E><U0908>";/
+            "<U0905><U0917><U0938><U094D><U0924>";/
+            "<U0938><U093F><U0924><U092E><U094D><U092C><U0930>";/
+            "<U0905><U0915><U094D><U091F><U0942><U092C><U0930>";/
+            "<U0928><U0935><U092E><U094D><U092C><U0930>";/
+            "<U0926><U093F><U0938><U092E><U094D><U092C><U0930>"
+%
+% Equivalent of AM PM
+am_pm       "<U092A><U0942><U0930><U094D><U0935><U093E><U0939><U094D><U0928>";/
+            "<U0905><U092A><U0930><U093E><U0939><U094D><U0928>"
+%
+% Appropriate date and time representation
+% %A %d %b %Y%I:%M:%S  %Z
+d_t_fmt     "<U0025><U0041><U0020><U0025><U0064><U0020><U0025><U0062>/
+<U0020><U0025><U0059><U0020><U0025><U0049><U003A><U0025><U004D><U003A>/
+<U0025><U0053><U0020><U0025><U0070><U0020><U0025><U005A>"
+%
+% Appropriate date representation
+% %A %d %b %Y
+d_fmt       "<U0025><U0041><U0020><U0025><U0064><U0020><U0025><U0062>/
+<U0020><U0025><U0059>"
+%
+% Appropriate time representation
+% %I:%M:%S  %Z
+t_fmt       "<U0025><U0049><U003A><U0025><U004D><U003A><U0025><U0053>/
+<U0020><U0020><U0025><U005A>"
+%
+% Appropriate 12 h time representation (%r)
+t_fmt_ampm  "<U0025><U0049><U003A><U0025><U004D><U003A><U0025><U0053>/
+<U0020><U0025><U0070><U0020><U0025><U005A>"
+%
+date_fmt       "<U0025><U0061><U0020><U0025><U0062><U0020><U0025><U0065>/
+<U0020><U0025><U0048><U003A><U0025><U004D><U003A><U0025><U0053><U0020>/
+<U0025><U005A><U0020><U0025><U0059>"
+END LC_TIME
+
+LC_MESSAGES
+copy "hi_IN"
+END LC_MESSAGES
+
+
+LC_PAPER
+copy "hi_IN"
+END LC_PAPER
+
+
+LC_NAME
+% This is the ISO_IEC TR14652 Locale definition for the
+% LC_NAME category.
+%
+name_fmt    "<U0025><U0070><U0025><U0074><U0025><U0066><U0025><U0074>/
+<U0025><U0067>"
+name_gen    ""
+name_mr     "<U0936><U094d><U0930><U0940><U002E>"
+name_mrs    "<U0936><U094d><U0930><U0940><U092e><U0924><U0940><U002E>"
+name_miss   "<U0938><U0941><U0936><U094d><U0930><U0940><U002E>"
+name_ms     "<U0938><U0941><U0936><U094d><U0930><U0940><U002E>"
+
+END LC_NAME
+
+
+LC_ADDRESS
+copy "hi_IN"
+END LC_ADDRESS
+
+
+LC_TELEPHONE
+copy "hi_IN"
+END LC_TELEPHONE
+
+
+LC_MEASUREMENT
+copy "hi_IN"
+END LC_MEASUREMENT
Reply | Threaded
Open this post in threaded view
|

Locale copyright assignments

Petr Baudis
  Hi!

On Fri, Apr 20, 2012 at 01:08:21PM +0200, Petr Baudis wrote:

> http://sourceware.org/bugzilla/show_bug.cgi?id=13968
> (Patch slightly fixed up.)
>
> Add new locale mag_IN.
>
> Ok to commit?
>
> 2012-04-20  Chandan Kumar  <[hidden email]>
>
> [BZ#13968]
> * locales/mag_IN: New file.
> * SUPPORTED (SUPPORTED-LOCALES): Add appropriate entry.

  I just realized that I did not check whether the author has copyright
assignment with FSF. Is our policy to require copyright assignments for
locales as well? I'm wondering since it seems this has not been the
practice up to now, though it would be good if someone with access
to the assignment list could check.


  P.S.: The GNU maintainer manual also mentions at

        http://www.gnu.org/prep/maintain/html_node/Legally-Significant.html#Legally-Significant

tracking of legal significance of minor changes, writing "(tiny patch)"
in the ChangeLog etc. This is certainly not the current glibc practice.
To be clear, I'm not seeking to adopt it since I'm all for minimalizing
bureaucracy. But we should perhaps have a clear understanding of our
practices in this area now that many people are committing changes.

                                Petr "Pasky" Baudis
Reply | Threaded
Open this post in threaded view
|

Re: Locale copyright assignments

Petr Baudis
  Hi!

On Fri, Apr 20, 2012 at 07:00:57PM +0200, Petr Baudis wrote:
>   I just realized that I did not check whether the [Glibc Locale] author has copyright
> assignment with FSF. Is our policy to require copyright assignments for
> locales as well? I'm wondering since it seems this has not been the
> practice up to now, though it would be good if someone with access
> to the assignment list could check.

  I expected to get an "obviously an assignment is required" reply but
I got none, so maybe it is not so obvious. The locale files contain
little creativity, even less than e.g. the timezone files which at least
contain very detailed rationale for each record.

  So this is a ping and I'm also Cc'ing [hidden email] and Brett Smith
who was interested in locales copyright before as well:

        http://sourceware.org/ml/libc-locales/2011-q1/msg00017.html

(Note that this licence is still used for some locales.)

  P.S.: I'm not interested in fixing up any past (c) mistakes, someone
else or the FSF would have to spend their time on that. I just want
to clarify the policy for future submissions.

--
                                Petr "Pasky" Baudis
        Smart data structures and dumb code works a lot better
        than the other way around.  -- Eric S. Raymond
Reply | Threaded
Open this post in threaded view
|

[gnu.org #751250] Re: Locale copyright assignments

Mike Stump via RT
> [[hidden email] - Mon Apr 30 13:31:15 2012]:
>
>   Hi!
>
> On Fri, Apr 20, 2012 at 07:00:57PM +0200, Petr Baudis wrote:
> >   I just realized that I did not check whether the [Glibc Locale]
> author has copyright
> > assignment with FSF. Is our policy to require copyright assignments
> for
> > locales as well? I'm wondering since it seems this has not been the
> > practice up to now, though it would be good if someone with access
> > to the assignment list could check.
>
>   I expected to get an "obviously an assignment is required" reply but
> I got none, so maybe it is not so obvious. The locale files contain
> little creativity, even less than e.g. the timezone files which at
> least
> contain very detailed rationale for each record.
>
>   So this is a ping and I'm also Cc'ing [hidden email] and Brett Smith
> who was interested in locales copyright before as well:

Brett actually had his last day on Friday. Josh Gay <[hidden email]> has taken over his
responsibilities.

>
> http://sourceware.org/ml/libc-locales/2011-q1/msg00017.html

That looks like a situation where we have not requested assignment in the past. If there is a
particular contributor you want me to look up for you I can do that as well. The person involved
in that thread (Keld Simonsen) does not have an assignment on file, but instead has a
translation disclaimer in place. Other people on libc's translation team
(http://translationproject.org/domain/libc.html) also just have a disclaimer, but no assignment.
So I am guessing that assignment is not necessary in this situation.

>
> (Note that this licence is still used for some locales.)

That is something that Josh will probably want to look at.

>
>   P.S.: I'm not interested in fixing up any past (c) mistakes, someone
> else or the FSF would have to spend their time on that. I just want
> to clarify the policy for future submissions.
>
>
>
--
Sincerely,

Donald R. Robertson, III, J.D.
Assignment Administrator
Free Software Foundation
51 Franklin Street, Fifth Floor
Boston, MA 02110
Phone +1-617-542-5942
Fax +1-617-542-2652

---

Reply | Threaded
Open this post in threaded view
|

Re: Locale copyright assignments

Carlos O'Donell-2
In reply to this post by Petr Baudis
On Mon, Apr 30, 2012 at 1:31 PM, Petr Baudis <[hidden email]> wrote:

>  Hi!
>
> On Fri, Apr 20, 2012 at 07:00:57PM +0200, Petr Baudis wrote:
>>   I just realized that I did not check whether the [Glibc Locale] author has copyright
>> assignment with FSF. Is our policy to require copyright assignments for
>> locales as well? I'm wondering since it seems this has not been the
>> practice up to now, though it would be good if someone with access
>> to the assignment list could check.
>
>  I expected to get an "obviously an assignment is required" reply but
> I got none, so maybe it is not so obvious. The locale files contain
> little creativity, even less than e.g. the timezone files which at least
> contain very detailed rationale for each record.
>
>  So this is a ping and I'm also Cc'ing [hidden email] and Brett Smith
> who was interested in locales copyright before as well:
>
>        http://sourceware.org/ml/libc-locales/2011-q1/msg00017.html
>
> (Note that this licence is still used for some locales.)
>
>  P.S.: I'm not interested in fixing up any past (c) mistakes, someone
> else or the FSF would have to spend their time on that. I just want
> to clarify the policy for future submissions.

Petr,

I think you're on the right path here and I appreciate your effort!

We don't have very clear policy here and we should, so you're blazing
a trail here for the community.

Whatever conclusion we reach we should document it in the wiki and
teach the new volunteers about it.

Cheers,
Carlos.
Reply | Threaded
Open this post in threaded view
|

Re: [gnu.org #751250] Re: Locale copyright assignments

Petr Baudis
In reply to this post by Mike Stump via RT
  Hi!

On Tue, May 01, 2012 at 12:56:00PM -0400, Donald R Robertson III via RT wrote:

> > [[hidden email] - Mon Apr 30 13:31:15 2012]:
> > On Fri, Apr 20, 2012 at 07:00:57PM +0200, Petr Baudis wrote:
> > >   I just realized that I did not check whether the [Glibc Locale] author has copyright
> > > assignment with FSF. Is our policy to require copyright assignments for
> > > locales as well? I'm wondering since it seems this has not been the
> > > practice up to now, though it would be good if someone with access
> > > to the assignment list could check.
> >
> >   I expected to get an "obviously an assignment is required" reply but
> > I got none, so maybe it is not so obvious. The locale files contain
> > little creativity, even less than e.g. the timezone files which at
> > least
> > contain very detailed rationale for each record.
..snip..
> >
> > http://sourceware.org/ml/libc-locales/2011-q1/msg00017.html
>
> That looks like a situation where we have not requested assignment in the past. If there is a
> particular contributor you want me to look up for you I can do that as well. The person involved
> in that thread (Keld Simonsen) does not have an assignment on file, but instead has a
> translation disclaimer in place. Other people on libc's translation team
> (http://translationproject.org/domain/libc.html) also just have a disclaimer, but no assignment.
> So I am guessing that assignment is not necessary in this situation.

  Thanks for the info!

  So the legal position of FSF is that locale data is similar to
translations?

  Should we require locale contributors to sign and mail the disclaimer
then or is it fine if we simply do not require any paperwork at all?

  Thanks,

                                Petr "Pasky" Baudis