From: Mojca Miklavec via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Transliteration
Date: Thu, 3 Feb 2022 22:01:19 +0100 [thread overview]
Message-ID: <CALBOmsYv=XtxVQFtNHBUTbaAVojRu8LwUHvZ4k3jrtKR1sC5oQ@mail.gmail.com> (raw)
In-Reply-To: <3ca805e0-c7f3-54e5-3769-2bde039aacaf@xs4all.nl>
On Thu, 3 Feb 2022 at 21:41, Hans Hagen wrote:
>
> > 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
Yes, loading both patterns at once is definitely the correct approach.
That's what the rest of the TeX world already does (at least LuaTeX
and XeTeX; pdfTeX not of course), see
https://github.com/hyphenation/tex-hyphen/blob/master/hyph-utf8/tex/generic/hyph-utf8/loadhyph/loadhyph-sr-latn.tex
We have two sets of Cyrillic patterns (and several Latin ones as
well), so composing a single file was a bit of a (somewhat political)
challenge.
Now at least in theory the users are free to choose which of the two
sets of patterns they want.
I never checked what ConTeXt was doing with the Serbian patterns.
Personally I would suggest taking hyph-sh-cyrl.pat.txt and hyph-sh-latn.pat.txt.
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-02-03 21:01 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 ` Transliteration Hans Hagen via ntg-context
2022-02-03 21:01 ` Mojca Miklavec via ntg-context [this message]
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='CALBOmsYv=XtxVQFtNHBUTbaAVojRu8LwUHvZ4k3jrtKR1sC5oQ@mail.gmail.com' \
--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).