Re: [I18n] Issue 1015: new Belarusian locale variant, need assistance

[Ihar Hrachyshka]

Sorry for bothering you,

but it seems like this email didn't get to glibc-alpha ML. At least
archives don't show it here:
http://www.cygwin.com/ml/libc-alpha/2010-11/ Can you help us to
actually push this problem resolution, maybe by finding a glibc
developer that is willing to make the needed commit for locale files
attached to bugzilla?

Thanks,
Ihar

On Tue, Nov 2, 2010 at 00:23, Mark Brown <ms_b...@sbcglobal.net> wrote:
> Hi-
>
> This was sent to the glibc steering committee list; since we have a BZ with
> files, is alpha the right place for this now?
>
>
> -------- Original Message --------
> Subject: Issue 1015: new Belarusian locale variant, need assistance from you
> Date: Mon, 1 Nov 2010 02:19:27 +0200
> From: Ihar Hrachyshka <ihar.hr...@gmail.com>
> To: glib...@gnu.org
> CC: Belarusian i18n list <i1...@mova.org>
>
> Greetings to members of the GNU C Library Steering Committee,
>
> Prelude: This issue was raised at GNU C Library Bugzilla about five
> years ago, and still there is no final resolution. Discussion on
> Bugzilla is stalled, and it seems like active glibc maintainers and
> contributors don't monitor it. It would be great to see some progress
> on this issue and finally get this locale variant in upstream. I hope
> that you can help us in achieving this hence I write this mail to you.
>
> The Belarusian language community affiliated with open-source feels
> there's a time for creating the additional sub-variant of the be_BY
> locale (suggested name -- be_BY@tarask, where @tarask stands for a
> special IANA registered -tarask modifier).
>
> Such sub-variant would denote the locale data and text (translations
> etc.) represented in the fairly popular in Belarusian community
> informal variant of the Belarusian language, which is standardized in
> the book:
>
> "Беларускі клясычны правапіс. Збор правілаў. Сучасная нармалізацыя",
> Audra, Вільня-Менск, 2005. (title translation: "Belarusian classical
> orthography. Set of rules. Modern normalization.")
>
> The community feels that the current situation, with locale and text
> data mixing  both of the variants, serves bad both translators and
> users. Separation of  variants, like proposed, would facilitate both
> effectiveness of translating process, for translators, and consistent
> feel-of-product, for consumers. Among others, there were requests from
> one of the embedded hardware vendors wanting to supply its firmware
> with the aforementioned language variant support and feeling the lack
> of such locale in upstream GNU C Library distribution.
>
> The issue had already been raised c.June 2005 as a Bugzilla issue
> (http://sources.redhat.com/bugzilla/show_bug.cgi?id=1015), but then
> the community didn't agree on some points (naming etc.), and the issue
> was suspended. Now, sort of consensus has been reached and both
> "sides" of the dispute are now endorsing this request to create the
> additional sub-variant of the be_BY locale with suggested name of
> be_BY@tarask.
>
> The needed locale files are attached at the corresponding Bugzilla page.
>
> Don't hesitate to ask me for any additional comments if needed. I also
> put Belarusian localization mailing list in Cc in case you need to
> hear from community.
>
> Looking forward to hear from you soon,
> Ihar Hrachyshka
>
>
>

_______________________________________________
I18n mailing list
I1...@mova.org
http://mova.org/cgi-bin/mailman/listinfo/i18n

[Ihar Hrachyshka]

On Thu, Nov 4, 2010 at 14:57, Mark Brown <ms_b...@sbcglobal.net> wrote:
> Ihar-

>
> On 11/03/2010 06:43 PM, Ihar Hrachyshka wrote:
>>
>> Sorry for bothering you,
>>
>> but it seems like this email didn't get to glibc-alpha ML. At least
>> archives don't show it here:
>> http://www.cygwin.com/ml/libc-alpha/2010-11/ Can you help us to
>> actually push this problem resolution, maybe by finding a glibc
>> developer that is willing to make the needed commit for locale files
>> attached to bugzilla?
>

> Yes, it looks like I made a mistake, and will be sending it out again today.
> The list I should have sent it to (and will) is
> libc-...@sourceware.org .
>

Mark,
Thanks for assisting us in this issue resolution. We'll wait patiently
for discussion results.
Ihar