| Summary: | new locale en_RU | ||
|---|---|---|---|
| Product: | glibc | Reporter: | Kirill A. Korinskiy <catap> |
| Component: | localedata | Assignee: | GNU C Library Locale Maintainers <libc-locales> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | drepper.fsp, glibc-bugs, lapdev |
| Priority: | P2 | Flags: | fweimer:
security-
|
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
|
Description
Kirill A. Korinskiy
2009-04-06 11:43:26 UTC
Can you please provide backing by consensus of some kind of Russian LUG or ack from the current ru_RU locale authors? Who author current ru_RU locale? Who is a author of current ru_RU locale? Try contacting Keld.Simonsen@dkuug.dk. Subject: Re: new locale en_RU
On Wed, Apr 08, 2009 at 03:07:51PM -0000, pasky at suse dot cz wrote:
>
> ------- Additional Comments From pasky at suse dot cz 2009-04-08 15:07 -------
> Try contacting Keld.Simonsen@dkuug.dk.
OK, I am here. I could stand as the author.
keld
Ok, couple of points... Can you fill in the missing LC_IDENTIFICATION bits, please? At least the source field... Is there some reason why the LC_ADDRESS, LC_NAME, LC_MEASUREMENT, LC_PAPER and LC_TELEPHONE sections aren't simply copied over from the ru_RU locale? Ok. I update locale: - fill missing LC_IDENTIFICATION bits - copy from ru_RU sections LC_MONETARY, LC_NUMERIC, LC_MESSAGES, LC_PAPER, LC_TELEPHONE, LC_MEASUREMENT, LC_NAME and LC_ADDRESS anybody have a news? Why should this locale be added? There are people speaking English in about every country. Locales can easily be added as part of a locale pack or so. Just use localedef. I'm and use localdef now. In russian most popular using engilsh interface. And most peoples use en_US locale for english interface on desktop and this way not a correct because guys lost of normal date format and othe. Can you somehow show that english interface is more important in Russia than in other non-English-speaking countries? Also, instead of going through the combinatorial explosion of adding locales for every language/country combination (I repeatedly fend off requests for adding en_SV, for example), it would be better to fix desktop environments to allow users to configure LC_MESSAGES and LANG differently, so that you would use LANG=ru_RU.UTF-8 and LC_MESSAGES=en_US.UTF-8. I'm not going to add the locale. People interesting in them can compile it themselves. It's true that many people in Russia (and elsewhere) for various reasons prefer en_US locale. I believe many people would like to have an English locale without British and American quirks, that is, with A4 paper format, monday as the first weekday, %d.%m.%Y as date format, metric system and comma as decimal point. These features, I believe, are shared by the most of European nations and at the same time they are ones that a user encounters most. One could name it an "International" locale, or, perhaps, "European" one. Probably, it doesn't really matter if it is coded as en_RU, en_DE, en_FI, whatever. In fact, this locale (more or less) already exists: http://lh.2xlibre.net/locale/en_DK/. Well, "International" locale happened to be Danish one for reasons of historical nature, so to say. there is also another international locale, namely the i8n locale of TR 14562. |