ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: transliteration russian
Date: Sat, 30 Oct 2010 00:31:33 +0200	[thread overview]
Message-ID: <AANLkTinuKbse16eO1X_O6LE57+fXRu0_eip8YHT+viKA@mail.gmail.com> (raw)
In-Reply-To: <4CCB476E.8040706@gmail.com>

2010/10/30 Andrzej Orłowski-Skoczyk wrote:
> 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.

I didn't inspect the transliteration, but now that you point it out -
true, to achieve perfect results, one would need to completely
redesign the patterns.

... or simply use a random slavic language and fix the wrong
hyphenations one-by-one (in particular, words with sh/ch could easily
break even though they represent a single letter).

> 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.

... it depends on who the human is. Slavic-speaking countries have no
problem pronouncing čšž ... :) :) :) Quotation marks are a bit weird
though ...

Maybe the most sensible solution (assuming LuaTeX) that would work
perfectly but would not be easy to write could be to input the title
in Cyrillic script, let TeX hyphenate it, and finally output
automatically transliterated string.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2010-10-29 22:31 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
2010-10-29 22:31     ` Mojca Miklavec [this message]
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=AANLkTinuKbse16eO1X_O6LE57+fXRu0_eip8YHT+viKA@mail.gmail.com \
    --to=mojca.miklavec.lists@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).