Informal romanizations of Cyrillic


Informal or ad hoc romanizations of Cyrillic have been in use since the early days of electronic communications, starting from early e-mail and bulletin board systems. Their use faded with the advances in the Russian internet that made support of Cyrillic script standard, but resurfaced with the proliferation of instant messaging, SMS and mobile phone messaging in Russia.

Development

Due to its informal character, there was neither a well-established standard nor a common name. In the early days of e-mail, the humorous term "Volapuk encoding" was sometimes used.
More recently the term "translit" emerged to indiscriminately refer to both programs that transliterate Cyrillic into Latin, as well as the result of such transliteration. The word is an abbreviation of the term transliteration, and most probably its usage originated in several places. An example of early "translit" is the DOS program TRANSLIT by Jan Labanowski, which runs from the command prompt to convert a Cyrillic file to a Latin one using a specified transliteration table.
There are two basic varieties of romanization of Russian: transliterations and Leetspeak-type of rendering of Russian text. The latter one is often heavily saturated with common English words, which are often much shorter than the corresponding Russian ones, and is sometimes referred to as Runglish or Russlish.

Translit

Translit is a method of encoding Cyrillic letters with Latin ones. The term is derived from transliteration, the system of replacing letters of one alphabet with letters of another. Translit found its way into web forums, chats, messengers, emails, MMORPGs and other network games. Some Cyrillic web sites had a translit version for cases of encoding problems.
As computer and network technologies developed support for the Cyrillic script, translit fell into disrepute. Sometimes translit users were ignored or even banned in Cyrillic-using communities.
Translit received its last development impulse with the increasing availability of mobile phones in Cyrillic-using countries. At first, the situation was the same as with computers; neither mobile phones nor mobile network operators supported Cyrillic. Although mobile phone technology now supports Unicode including all variants of Cyrillic alphabets, a single SMS in Unicode is limited to 70 characters, whereas a Latinate SMS can have up to 160 characters. If a message exceeds the character limit, it is split into multiple parts. That makes messages written in Cyrillic more expensive.
Sometimes ⟨y⟩, ⟨yu⟩, ⟨yo⟩, ⟨ye⟩, ⟨ya⟩ serve as transliteration for ⟨й⟩, ⟨ю⟩, ⟨ё⟩, ⟨е⟩, ⟨я⟩.
Lately a more aggressive form of translit appeared, its identifying characteristic being the use of numbers to substitute some of the letters. For example, 4 reads as "ch" and is used to translit letter "ч", from the transliteration of the word "four" in Russian, or, arguably, the appearance of the letter similar to that of four in Arabic numerals. Also, a number can substitute its whole name as part of a word: "sov7" for "sovsem" or "posmo3" for "posmotri".
NumberUsual transliterationOriginal word for it in TranslitOriginal word in Russian
1ododinодин
2dvdvaдва
3trtriтри
4chchetyreчетыре
5ppyat'пять
6shshest'шесть
7ssem'семь
8vovosem'восемь
9dtdevyat'девять

Such translit is often so distorted that native speakers have trouble reading it. The use of translit is forbidden on many Internet forums.
Russia and other former Soviet republics adopted the ISO 9 transliteration standard for official use, replacing the old Soviet GOST 16876-71.

Translit in Bulgaria

A modified version of Translit, called Shlyokavitsa or Maimunitsa is used widely on the Internet in Bulgaria. It is similar to Russian translit, except for the following differences:
Volapuk encoding or latinica is a slang term for rendering the letters of the Cyrillic script with Latin ones. Unlike Translit, in which characters are replaced to sound the same, in volapuk characters can be replaced to look or sound the same.

Etymology

The name Volapuk encoding comes from the constructed language Volapük, for two reasons. Cyrillic text written in this way looks strange and often funny, just as a Volapük-language text may appear. At the same time, the word "Volapük" itself sounds funny to Russian ears, so the name stuck.
The term was popularized by its use in the first Soviet commercially available UUCP and TCP/IP network, RELCOM, making it the likely origin of the usage of Volapuk as applied to Cyrillic encoding.

History

Volapuk and Translit have been in use since the early days of the Internet to write e-mail messages and other texts in Russian where the support of Cyrillic fonts was limited: either the sender did not have a keyboard with Cyrillic letters or the receiver did not necessarily have Cyrillic screen fonts. In the early days, the situation was aggravated by a number of mutually incompatible computer encodings for the Cyrillic script, so that the sender and receiver were not guaranteed to have the same one. Also, the 7-bit character encoding of the early days was an additional hindrance.
Some Russian e-mail providers even included Volapuk encoding in the list of available options for the e-mails routed abroad, e.g.,
By the late 90s, the encoding problem had been almost completely resolved, due to increasing support from software manufacturers and Internet service providers. Volapuk still maintains a level of use for SMS text messages, because it is possible to fit more characters in a Latinized SMS message than a Unicode one. It is also used in computer games that do not allow Cyrillic text in chat, particularly Counter-Strike.

Rules

Volapuk often replaces Cyrillic letters with Latin ones in order to look the same or at least similar as typed or handwritten Cyrillic letters.
  1. Replace "the same" letters: a, e, K, M, T, o. Capitalize when necessary for closer resemblance.
  2. Replace similar-looking letters: в – B, г – r, з – 3, л – J| or /\, н – Н, п – n, р – p, с – c, у – y, х – x, ч – 4, я – R, и – N. This may vary.
  3. Replace all other non-obvious hard-to-represent characters using leet ; there are many options for each letter. and so on. The choice for each letter depends on the preferences of the individual user.
Encoding depends on the language as well. For example, Ukrainian users have their own traditions, distinct from the Russian ones.

Table

Example

The Russian Chat Alphabet is a fast-to-type mix of translit and Volapuk, being translit mostly, but giving the option to replace some 2 or 3 character transliterations with shorter 1 character counterparts from Volapuk. This speeds up typing; however, in some cases characters may be Volapuk-encoded, making text appear incorrectly and therefore be harder or impossible to read. In Russia and countries where Russian is used regularly to communicate via mobile phone and chat room, it is used as an alternate and free style of transliteration. It also works around the limitations of programs and/or devices where a Cyrillic keyboard is not available.
Within Russia, one reason to use transliteration for Russian text is that mobile characters allow for more Latin characters than Cyrillic ones per SMS: Latin and capital Greek letters are covered by the GSM seven-bit alphabet, allowing up to 160 such characters in a message, while Cyrillic letters are not, requiring a 16-bit encoding that limits messages to 70 characters. In this case, the focus is of course on getting one Latin character for each Cyrillic character. Only those used for Russian are exemplified here.
Where variants are given, the first is most common and the last is less common, although trends change quickly and differ from person to person. Lack of standardization is the biggest weakness of this informal transliterations, as different styles contradict each other and can make reading slower than necessary.

Translit external links