ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Steffen Wolfrum <context@st.estfiles.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: transliteration russian
Date: Fri, 29 Oct 2010 23:25:20 +0200	[thread overview]
Message-ID: <AANLkTik8a5BBq_YxH9xbxO_bx7SXOtR6tqL=saYyRVRz@mail.gmail.com> (raw)
In-Reply-To: <6CB41398-8E44-433C-B4FA-1B98BC684A0E@st.estfiles.de>

On Fri, Oct 29, 2010 at 13:18, Steffen Wolfrum wrote:
> Hi all,
>
> I am just about to typeset a book of a russian author written in english, but with a lot of russian literature listed in the bibliography:
> The titles of theses sources are russian but in latin transliteration, like this ...
> O koordinacii mezhdunarodnyh i vneshnejekonomicheskih svjazej subjektov Rossijskoj Federacii
>
> But even though I assigned "\language[ru]" the word "vneshnejekonomicheskih" eg. does not get hyphenated.
> And there are some dozen titles more that show the same problem ...
>
> Is this (to not hyphenate) because of the transliteration?
> Do I have to choose another \language key?

Dear Steffen,

The Russian patterns only cover the Cyrillic part. Serbian patterns
are the only ones that cover both scripts, but even then the patterns
themselves are seen as two different languages by TeX.

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.

Another "easy" option would be to load any other slavic patterns as
Jano suggested and then add exceptions where needed. I'm not sure if
transliterated patterns belong to hyph-utf8. (If nothing else, Russian
is transliterated differently into Slovenian for example, so one would
formally then need "transliteration from Russian to any other given
language written in Cyrillic script").

[still under assumption that you use LuaTeX and that transliteration
is one-to-one]
By far the easiest and most portable solution would be if you could
convince Taco to implement something like "latin a is equivalent to
cyrillic a as far as hyphenation is concerned" (which could also solve
many other problems that we have). Actually, you can already do that
by redefining \lccode of latin a to point to cyrillic a (and do that
for the whole alphabet), but then you need to make sure that you don't
use any commands for lowercasing/uppercasing words. If you need
details, I can help you out, but first exact transliteration rules are
needed.

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
___________________________________________________________________________________


  parent reply	other threads:[~2010-10-29 21:25 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 [this message]
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
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='AANLkTik8a5BBq_YxH9xbxO_bx7SXOtR6tqL=saYyRVRz@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=context@st.estfiles.de \
    --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).