Locale en_RU 0.5.2-1

Locale en_RU

Locale en_RU is English language locale for Russia. Locale en_RU developed and tested in Fedora and will likely work in other GNU/Linux distros based on glibc. There are prebult RPM packages for a few versions of Fedora and Red Hat/CentOS, source tarball for configure && make && make install is also available. Locale en_RU is free software.

This document describes Locale en_RU version 0.5.2-1 released on 2017-04-10.

Contents

Quick Start

  1. Install
  2. Use
  3. ???????
  4. PROFIT

What?

Locale is a set of parameters that defines language- and country-specific preferences like number formats, date and time formats, currency symbol, paper size, etc.

Locale name consists of four parts:

language_territory.codeset@modifier

Nowadays UTF-8 encoding is a de-facto standard, so codeset is usually utf8 (or UTF-8). modifier is often omitted, so typical locale name looks like:

Usually a GNU/Linux system is equipped with a large set of predefined locales. Fedora 19 has 789 predefined locales. Technically, locales are part of glibc, a core system library.

As a part of glibc, locales may affect any application, either console or GUI, which uses glibc. Since glibc is used by a great majority of GNU/Linux applications, locales may affect almost all applications.

Locales may have effect, but may not, because application should use locale. If an application is not locale-aware, locales will not affect it. Nowadays most of applications are locale-aware.

Locale en_RU is a custom locale. Custom means it is not a part of glibc package. However, being installed from RPM package it becomes a fully functional first-class sitizen of system locale family.

As you can deduce from its name, en_RU is English language (en) locale for Russia (RU). What does it mean? Look:

$ export LANG=en_RU.utf8

$ date +%c
Wed 05 Nov 2014 18:00:00 MSK   # Note 24-hour clock.

$ cal
    November 2014
Mo Tu We Th Fr Sa Su           # Week starts on Monday.
                1  2
 3  4  5  6  7  8  9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

$ printf "%'0.2f\n" 1000000
1 000 000.00                   # Thousand separator is space.

See section What Exactly? for detailed description of en_RU locale parameters.

Why?

Nowadays the great majority of people use computers every day, either at work or home. They are not computer professionals (programmers or system administrators), they are just end users. They may know English language or may not. Programs for end users are usually internationalized and localized to let users talk with computers using their mother tongue. That's generally right approach, but some old fogeys who still prefer English for user interface because English commands and messages are often shorter than Russian counterparts, localizations are incomplete or outdated, or just because it is a very old habit.

However, using locale en_US (English for the USA) or other predefined locales like en_GB (English for Great Britain) or en_CA (English for Canada) has noticeable drawbacks: ridiculous 12-hour clock (anybody knows if 12pm is noon or midnight? 12am?), confusing (at least for Russians) mm/dd/yyyy date format, ugly imperial units, etc.

Trick with combining locales by setting environment variables LANG and LC_MESSAGES does not play well to me:

$ export LANG=ru_RU.utf8
$ export LC_MESSAGES=en_US.utf8

$ date +%c
Ср 05 ноя 2014 18:01:43        # Note Russian weekday and month names.

$ cal
     Ноябрь 2014               # Again.
Пн Вт Ср Чт Пт Сб Вс
                1  2
 3  4  5  6  7  8  9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

$ printf "%'0.2f\n" 1000000
1 000 000,00                   # Decimal mark is comma.

Thus, I prefer to use English language, but I want to have 24-hour clock, Monday as the first day of a week and metric units. In other words, I need locale en_RU.

Others

Simple Google search1 shows I am not the only inventor of the locale, and not the first of inventors. However, the same search also shows the idea of such a locale visited many unretated minds. From time to time different people asked for such a locale:

…or provided instructions how to set up it:

The most noticeable attempt to the problem was made by Kirill A. Korinskiy in 2009: he submitted a proposal of a new locale to glibc Bugzilla. However, glibc maintainer Ulrich Drepper rejected it, he said people interested in the new locale can compile it themselves.

Still Why?

There are instructions how to set up locale en_RU, why did I create one more locale? Well, I did it because:

Features

This incarnation of locale en_RU is not a plain locale source and/or instruction how to compile and install it but a full-featured RPM package which:

Installing

Note: Installing the locale does not have immediate visible effect. To see the locale in action, you need to use it.

Installing prebuilt RPM package

The easiest way to install Locale en_RU is using prebuilt RPM package. Enable my repository first, then:

  • Starting from Fedora 22 use dnf command (run the command from root account):

    # dnf install locale-en_RU
  • In older distros, use yum command instead (run the command from root account):

    # yum install locale-en_RU

Building from sources

Download Locale en_RU source tarball:

$ wget https://sourceforge.net/projects/en-ru/files/0.5.2/locale-en_RU-0.5.2.tar.gz

unpack it:

$ tar xaf locale-en_RU-0.5.2.tar.gz
$ cd locale-en_RU-0.5.2

then follow instructions in INSTALL.en.md.

Using

In specific application

Just set environment variable LANG to en_RU.utf8 before running desired application, e. g.:

$ LANG=en_RU.utf8 gedit

This works for both console and GUI applications.

Note: Make sure there are no LC_* environment variables (e. g. LC_ALL, LC_MESSAGES, LC_TIME, etc), because they have priority over LANG. To check if there are any LC_* environment variables run:

$ printenv | grep ^LC_

Output should be empty. If it is not, unset all the variables:

$ unset `printenv | grep ^LC_ | cut -f1 -d=`

As your default locale in console session

Set environment variable LANG to value en_RU.utf8 in your profile script.

If your login shell is bash, make sure ~/.bash_profile file includes line:

export LANG=en_US.utf8

or two:

LANG=en_US.utf8
export LANG

In case of other shells, name of your profile script and assignment syntax may vary.

Changes in profile will have effect at your next login.

As your default locale in graphical session

Setting default locale depends on your graphical desktop environment (e. g. Gnome, KDE, etc). It could be either special GUI application (named Settings, Preferences, or Control Center), or a kind of configuration file.

Gnome 3.8, …, 3.22

SettingsRegion & Language; set Language to English (Russian Federation), and Formats to Russian Federation (English). Change will be applied the next time you log in.

As system default locale

In modern systemd-based GNU/Linux distros system-wide default locale is controlled by localectl program. Run

$ localectl status

to see current system locale, and

$ localectl set-locale LANG=en_RU.utf8

to change it to locale en_RU.

This command may be executed from non-root account. If so, user will be propmted for root password.

Changing the system locale does not have immediate effect. New locale will be used by system services at the next system boot. User may notice new locale at the next login.

Note: System default locale is often overriden by user's personal settings, especially in graphic sessions.

What Exactly?

Locale en_RU consistenly sticks to English language, but fixes other parameters which look ugly for Russians:

Known Problems

  1. Bug in glibc-locale-en_RU-0.001-1 prevents ugrading it. You will need uninstall it first, then install another version.

Bug Reports and Feedback

If you found a bug of any sort (including an typo or mistake in supporting documentation and/or website) or have a request, please submit a ticket. Questions and discussions are welcome at forums. Feel free to post a review and rate the project.

Note: Sorry, anonymous posts are not allowed. You have to register at SourceForge to get write permissions.

If registration at SourceForge is not feasible to you, send an email directly to author: mailto:van.de.bugger@gmail.com.

Donations are not requested. Just post a review and rate the project at SourceForge.

Enabling My Repository

My repository contains my software (and some 3rd-party software built and packaged by me). Packages are built for few versions of Fedora and Red Hat/CentOS.

To enable my repository in modern distros (i. e. starting from Fedora 22) run two commands from root account:

# dnf install dnf-plugins-core
# dnf copr enable vandebugger/release

In older distros (e. g. in Fedora 21, Red Hat 6 and 7):

# yum install yum-plugin-copr
# yum copr enable vandebugger/release

  1. Google search depends on searching history, so your may see different results.

  2. There is a bug in the first release of en_RU, though.

  3. Width of narrow no-break space depends on the font. In monospaced font all the glyphs should have the same width and so narrow no-break space has the same width as normal space. In proportional font narrow no-break space may be really narrow.

  4. Actually, this is an option. If glibc does not support ruble sign (it was introduced in glibc version 2.22), generic currency sign ("¤", U+00A4) can be used instead.