ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>,
	Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Transliteration
Date: Thu, 3 Feb 2022 21:41:37 +0100	[thread overview]
Message-ID: <3ca805e0-c7f3-54e5-3769-2bde039aacaf@xs4all.nl> (raw)
In-Reply-To: <c0e09d5f-0198-8755-e730-922f5a0b3898@gmail.com>

On 2/3/2022 8:15 PM, Ivan Pešić via ntg-context wrote:
> Hello!
> I've been working on a Serbian book and I had to transliterate it from 
> cyrillic to latin.
> There's been some nice improvement in transliteration, and I would like 
> to propose a small change.
> One of the peculiarities that current transliteration mechanisms (both 
> internal one and the 3rd party module from Philipp Gesang)
> don't process is that Љ, Њ and Џ are transliterated to Lj, Nj and Dž in 
> normal words that start the sentence, or in names that normally start 
> with a capital letter,
> but in titles written in all capitals they should be transliterated to 
> LJ, NJ and DŽ.
> So, the quick solution was to update the current mapping vector and add 
> another one (that is attached) that maps cyrillic capitals to LJ, NJ and DŽ
> and set the correct 30 letters used in Serbian language.
> It requires a bit more manual work to set the correct mapping for all 
> capitals text, but it works.
> I have also merged the Serbian hyphenation patterns, so there is no need 
> to switch the language in order to have hyphenation in transliterated text.
> That was possible because cyrillic and latin scripts use different code 
> points, and there are no conflicts in patterns.
> So I suggest merging the patterns for Serbian cyrillic and latin.

I'd like to hear Arthur / Mojca on that .... we can of course load them 
both but if that is an upstream merge i'll wait for that

you can actually map multiple to multiple in the tranmsliteration tables

["foo"] = "oof"

and such and there is in the next version also an exception mechanism 
that permits clone a transliteration and add exceptions

> There is another issue if one wants to use a dropcap and the rest of 
> that first word, and several following words are to be typeset in small 
> caps.
> If that first letter is Љ (or other two letters that transliterate as 
> digraphs), then the second letter of the digraph is not typeset in small 
> caps because
> it gets injected before the group that turns on small caps.
> For example:
> 
>     \placeinitial
>     Љ{\sc уди нису знали}
> 
> but this is quite a special case...
you can use \settransliteration{name} locally so as part of a style 
specification (there is also \resettransliteration)

the next upload has some more that Sreeram is currently documenting on 
the wiki

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-02-03 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 19:15 Transliteration Ivan Pešić via ntg-context
2022-02-03 20:41 ` Hans Hagen via ntg-context [this message]
2022-02-03 21:01   ` Transliteration Mojca Miklavec via ntg-context
2022-02-03 21:11     ` Transliteration Hans Hagen via ntg-context

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=3ca805e0-c7f3-54e5-3769-2bde039aacaf@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.nl \
    --cc=mojca.miklavec.lists@gmail.com \
    /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).