ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Andrzej Orłowski-Skoczyk" <aorlowski@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: transliteration russian
Date: Sat, 30 Oct 2010 00:15:10 +0200	[thread overview]
Message-ID: <4CCB476E.8040706@gmail.com> (raw)
In-Reply-To: <AANLkTik8a5BBq_YxH9xbxO_bx7SXOtR6tqL=saYyRVRz@mail.gmail.com>

On 10/29/2010 11:25 PM, Mojca Miklavec wrote:
> The best thing to do would be to transliterate Russian patterns into
> Latin script (under one condition: transliteration needs to be
> one-to-one; if one cyrillic glyph transliterates into two latin
> characters, that doesn't help you). If you use LuaTeX you may then
> load the patterns on the fly.

Warning: the transliteration used in Steffen's document is (or at least
the example is) lossy and as such will likely produce wrong hyphenation
output no matter the applied method of making TeX hyphenate it.

The transliteration (in the example) is also inconsistent - if you tried
to reverse transliterate it to Cyrillic, you would not only miss some
characters, but you would also get some other characters wrong.

Examples:
- 'subjektov' is 'субъектов',
- 'vneshnejekonomicheskih' is 'внешнеэкономических',
thus 'je' stands for both 'ъе' and for 'э'.

This however could be just the authors typo. In such case 'subjektov'
should be corrected to 'sub"ektov'.


The way to achieve a univocal (one-to-one) transliteration would be
first to reverse transliterate it to Cyrillic, and then transliterate
back to Latin using ISO 9 transliteration standard:
http://en.wikipedia.org/wiki/ISO_9
The example 'О координации международных и внешнеэкономических связей
субъектов Российской Федерации' would then output 'O koordinacii
meždunarodnyh i vnešneèkonomičeskih svâzej sub"ektov Rossijskoj
Federacii'. This however I wouldn't consider a very human-readable output.

A very handy tool for experiments can be found here:
http://translit.cc/

On the margin: Wouldn't it be much better to use just Cyrillic for that?
-- 
Andrzej Orłowski-Skoczyk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2010-10-29 22:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 11:18 Steffen Wolfrum
2010-10-29 11:58 ` Thomas A. Schmitz
2010-10-29 13:44   ` Jano Kula
2010-10-29 21:25 ` Mojca Miklavec
2010-10-29 22:05   ` Khaled Hosny
2010-10-30  8:17     ` Hans Hagen
2010-10-30  8:34       ` Taco Hoekwater
2010-10-30  9:34       ` Khaled Hosny
2010-10-31 18:12         ` Jano Kula
2010-10-31 18:47           ` Khaled Hosny
2010-10-29 22:15   ` Andrzej Orłowski-Skoczyk [this message]
2010-10-29 22:31     ` Mojca Miklavec
2010-10-30 14:24     ` Steffen Wolfrum
2010-10-29 22:47   ` Philipp Gesang
2010-10-29 23:06     ` Andrzej Orłowski-Skoczyk
2010-10-30  9:43       ` Philipp Gesang

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=4CCB476E.8040706@gmail.com \
    --to=aorlowski@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).