From: "Ivan Pešić" <ivan.pesic@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Adding built-in support for Serbian language
Date: Fri, 30 Oct 2020 23:18:41 +0400 [thread overview]
Message-ID: <263a379f-ca5e-e6e1-8b27-3dc5fcdf49d2@gmail.com> (raw)
In-Reply-To: <mailman.285.1604070640.1206.ntg-context@ntg.nl>
Dear Mojca,
Дана 30.10.2020. у 19:10, Mojca Miklavec пише:
> Would you be willing to also prepare the latin one then?
> The codes should be sorted out by Hans (potentially with some help),
> but we definitely want to use "sr-latn" and "sr-cyrl".
Sure, I will tomorrow create a transliteration to latin script and post
diffs here.
What you propose is in fact already used in some other places, I agree
with you.
> For the longer names there is some more freedom. LaTeX uses "serbianl"
> and "serbianc", I think, but I believe we can come up with something
> nicer.
> Maybe something along the lines of the following?
> \mainlanguage[serbian][script=latn]
> or
> \mainlanguage[serbian-latin]
> \mainlanguage[serbian-cyrillic]
> No clue, really.
>
> Thank you,
> Mojca
>
> (PS: I would say that adding support for transliteration of the text
> from one script to the other would be a really nice feature. Then you
> could type your text for a book once and have it typeset in both
> versions without any extra effort :)
As for transliteration, cyrillic to latin is one-to-one, straightforward
with no exceptions.
A simple table lookup is enough.
Going from latin to cyrillic, there are some exceptions, but we could
solve that.
I can provide Hans with all that is needed.
Ivan
___________________________________________________________________________________
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 parent reply other threads:[~2020-10-30 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.285.1604070640.1206.ntg-context@ntg.nl>
2020-10-30 19:18 ` Ivan Pešić [this message]
2020-10-30 19:27 ` Hans Hagen
2020-10-30 20:59 ` Ivan Pešić
2020-10-30 10:35 Ivan Pešić
-- strict thread matches above, loose matches on Subject: below --
2020-10-30 10:31 Ivan Pešić
2020-10-30 12:42 ` Mojca Miklavec
2020-10-30 14:07 ` Hans Hagen
2020-10-30 16:45 ` Henri Menke
2020-11-03 13:10 ` Hans Hagen
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=263a379f-ca5e-e6e1-8b27-3dc5fcdf49d2@gmail.com \
--to=ivan.pesic@gmail.com \
--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).