public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yury_tarasievich at yahoo dot com" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/1015] There is a need for an alternative belarusian locale Date: Thu, 04 Aug 2005 09:35:00 -0000 [thread overview] Message-ID: <20050804093525.24841.qmail@sourceware.org> (raw) In-Reply-To: <20050616151127.1015.mikhailian@altern.org> ------- Additional Comments From yury_tarasievich at yahoo dot com 2005-08-04 09:35 ------- I didn't make myself clear, then. This isn't about linguistics at all. In Belarusian language community, there exists certain interest group, promoting use of several (long obsoleted) orthography rules. This group calls their variant of Belarusian orthography "classic". Alexander Mikhailian proposes creating additional be_BY@... branch, which would assert usage of the mentioned orthography variant. And that's perfectly okay! Just the qualifier isn't chosen well. I wouldn't put "classic" but rather, e.g., "alternative" there because: The term "classic", by every definition, is something well-recognized, widely or traditionally used. However, virtually nobody in Belarusian community outside of the interest group (which isn't numerous and/or popular!) recognizes the mentioned variant as "classic", neither by knowing or referring the name, nor by usage tradition -- as the variant's key orthography features were obsoleted about 70 years ago! Even the group-promoted usage of name "classic" started, it seems, between 1992 and 1994 (judging by two big publications on Belarusian orthography by one of the group leaders). On the other hand, term "alternative" here would be immediately recognizable, both by popular understanding and by group self-imaging. P.S. The book Kirill A. Shutemov pointed me to contains one of the editions of the mentioned orthography variant, published by the interest group, supervised, even authored, it seems, by one of the interest group leaders. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=1015 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-08-04 9:35 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-16 15:12 [Bug localedata/1015] New: " mikhailian at altern dot org 2005-06-16 20:49 ` [Bug localedata/1015] " barbier at linuxfr dot org 2005-06-22 0:27 ` mikhailian at altern dot org 2005-07-12 9:21 ` yury_tarasievich at yahoo dot com 2005-08-03 13:26 ` adiel at nospam dot kiev dot ua 2005-08-03 13:31 ` kas at altlinux dot org 2005-08-03 13:55 ` cactus at narod dot ru 2005-08-04 9:35 ` yury_tarasievich at yahoo dot com [this message] 2005-10-14 18:05 ` drepper at redhat dot com 2005-10-18 8:25 ` yury_tarasievich at yahoo dot com 2005-12-08 13:45 ` ShupaS at rferl dot org 2005-12-13 23:09 ` yury_tarasievich at yahoo dot com 2005-12-14 8:35 ` viksia at gmail dot com 2005-12-26 12:24 ` yury_tarasievich at yahoo dot com 2006-11-09 11:47 ` ihar dot hrachyshka at gmail dot com 2006-11-13 10:41 ` ihar dot hrachyshka at gmail dot com 2007-12-19 21:02 ` ihar dot hrachyshka at gmail dot com 2008-05-17 5:33 ` 375gnu at gmail dot com 2008-05-31 14:01 ` ihar dot hrachyshka at gmail dot com 2009-10-23 20:29 ` ihar dot hrachyshka at gmail dot com 2009-10-23 20:42 ` jekhor at gmail dot com 2010-01-17 17:12 ` 375gnu at gmail dot com [not found] <bug-1015-131@http.sourceware.org/bugzilla/> 2010-11-06 12:46 ` pasky at suse dot cz 2010-11-06 13:15 ` ihar.hrachyshka at gmail dot com 2012-04-04 15:50 ` pasky at ucw dot cz 2012-04-04 15:51 ` pasky at ucw dot cz 2012-12-28 19:11 ` 375gnu at gmail dot com
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=20050804093525.24841.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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).