public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Zmicer Turok <nashtlumach@gmail.com>
To: libc-locales@sourceware.org
Subject: Fwd: Re: be-tarask
Date: Tue, 25 Feb 2020 05:11:00 -0000	[thread overview]
Message-ID: <3553C750-DE2C-469F-9CC2-C6A2633F3F84@gmail.com> (raw)
In-Reply-To: <2362D44A-F3B5-4148-84AD-1298AA797F84@gmail.com>




-------- Original Message --------
From: Zmicer Turok <nashtlumach@gmail.com>
Sent: 25 лютага 2020 08.07.01 GMT+03:00
To: Rafal Luzynski <digitalfreak@lingonborough.com>, libc-locales@sourceware.org
Subject: Re: be-tarask

Taraškievica is not supported by any official and/or scientific
institution, but there are philologists and writers who use this spelling. There are much more, the weight of those who use be-latn. There are as many users. Approximate activity can be viewed in the Wikipedia. The layout is no different from "be", there are necessary chars. Sense to add a locale exists.

On 24 лютага 2020 23.36.20 GMT+03:00, Rafal Luzynski <digitalfreak@lingonborough.com> wrote:
>24.02.2020 16:18 Carlos O'Donell <carlos@redhat.com> wrote:
>> 
>> On 2/24/20 10:02 AM, Zmicer Turok wrote:
>> > Hi, tell me please, is it possible to add a locale be-tarask for
>> > Belarusian?
>> 
>> Locales can certainly be added if people are willing to do the work
>to add
>> them.
>> 
>> Can you please explain what be-tarask would represent?
>
>be-tarask is an alternative (classical, old) spelling of Belarusian
>language
>using the Cyrillic script (same as be_BY). [1]
>
>> We currently have be_BY and be_BY@latin (latin script version).
>
>The bug report and the discussion is here: [2]
>
>Last time I asked a native speaker I was told that less and less people
>use
>that spelling so it is not worth adding.  Has anything changed
>recently?
> Are
>there people willing to use it?
>
>Another obstacle is that the variant is not supported by CLDR.  Also
>I'm
>not sure if Taraškievica is supported by any official and/or scientific
>institution.  It may be difficult to verify the correctness of the
>data.
>However, if we overcome these difficulties adding be_BY@tarask is
>possible.
>
>Regards,
>
>Rafal
>
>
>[1] https://en.wikipedia.org/wiki/Tara%C5%A1kievica
>[2] https://sourceware.org/bugzilla/show_bug.cgi?id=1015

  parent reply	other threads:[~2020-02-25  5:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 15:02 be-tarask Zmicer Turok
2020-02-24 15:18 ` be-tarask Carlos O'Donell
2020-02-24 20:33   ` be-tarask Rafal Luzynski
     [not found]     ` <2362D44A-F3B5-4148-84AD-1298AA797F84@gmail.com>
2020-02-25  5:11       ` Zmicer Turok [this message]
2020-02-26 13:13       ` be-tarask Zmicer Turok
     [not found] <D1B79508-A3D4-4C2E-BC48-487A58CF27E3@gmail.com>
2020-02-24 16:47 ` Fwd: be-tarask Zmicer Turok
2020-02-24 16:55   ` Carlos O'Donell
2020-02-24 17:02     ` Zmicer Turok

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3553C750-DE2C-469F-9CC2-C6A2633F3F84@gmail.com \
    --to=nashtlumach@gmail.com \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).