ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jano Kula <jano.kula@tiscali.cz>
To: ntg-context@ntg.nl
Subject: Re: transliteration russian
Date: Sun, 31 Oct 2010 19:12:20 +0100	[thread overview]
Message-ID: <iakbi5$p4f$1@dough.gmane.org> (raw)
In-Reply-To: <20101030093433.GA2140@khaled-laptop>

Hi!

On 10/30/2010 11:34 AM, Khaled Hosny wrote:
> On Sat, Oct 30, 2010 at 10:17:11AM +0200, Hans Hagen wrote:
>> On 30-10-2010 12:05, Khaled Hosny wrote:
>>> On Fri, Oct 29, 2010 at 11:25:20PM +0200, Mojca Miklavec wrote:
>>>> 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.
>>>
>>> I was thinking, since using \lccode for hyphenation is really a wired
>>> choice (I'm sure don has a good reason back then, but such things are
>>> usually no longer relevant), and since it is used in a sort of
>>> controlled environment (playing with \lccode's for hyphenation is not
>>> ever one's toy), may be luatex can break the backward compatibility in
>>> the hyphenation area and have a dedicated new code, \hycode or
>>> something, only for hyphenation purposes (may be backward compatibility
>>> can be kept by using it in addition to \lccode, maybe).
>>>
>>> What do you think?
>>
>> just any letter (catcode letter) would do and the rest is to be
>> controlled by the patterns
>
> The issue here is that we want to make some character equivalent to each
> other, e.g. ' and ’ which are needed for some languages, without the
> need to duplicate the patterns.

Before jumping too deep to the subject, consider if it really worth an 
effort. There is not much more then, titles written in the 
transliterated text. No continuous reading.

My experience says, whatever language is the original title, reader 
usually expects hyphenation similar to the language of the main text. 
Whenever I've used English patterns in English titles (even citations), 
they where changed by the Czech proofreader -- though they were 
perfectly correct in English -- to resemble Czech patterns. I'm not 
saying it is the right approach, but from the readers' and proofreaders' 
point of view if he reads in Czech and doesn't now English patterns or 
even English, patterns different from Czech are disturbing.

Jano

___________________________________________________________________________________
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-31 18:12 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 [this message]
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='iakbi5$p4f$1@dough.gmane.org' \
    --to=jano.kula@tiscali.cz \
    --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).