From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Transliteration
Date: Thu, 3 Feb 2022 22:11:17 +0100 [thread overview]
Message-ID: <bc3a5dfe-ad1e-9b5b-5883-bac4f6071398@xs4all.nl> (raw)
In-Reply-To: <CALBOmsYv=XtxVQFtNHBUTbaAVojRu8LwUHvZ4k3jrtKR1sC5oQ@mail.gmail.com>
On 2/3/2022 10:01 PM, Mojca Miklavec wrote:
> 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.
we currently do this:
{ "sr", "hyph-sr", "serbian", false, { "hyph-sr-cyrl",
"hyph-sr-latn" }, },
so you suggest to replace that by the "sh" variants
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-02-03 21:11 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 ` Transliteration Mojca Miklavec via ntg-context
2022-02-03 21:11 ` Hans Hagen via ntg-context [this message]
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=bc3a5dfe-ad1e-9b5b-5883-bac4f6071398@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).