From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ASCII input - non ASCII output
Date: Wed, 8 Nov 2017 15:36:35 +0100 [thread overview]
Message-ID: <f2cd1625-85fc-aca0-8fd3-2a35ab3a8fae@uni-bonn.de> (raw)
In-Reply-To: <CALBOmsZr_Kvymhf=4b7rt9RZdnjMq2pre24afBzz2MfWG0Ai1Q@mail.gmail.com>
On 11/08/2017 11:34 AM, Mojca Miklavec wrote:
> I'm still not arguing that this is the most brilliant idea, but I can
> totally imagine a Serbian professor wanting to "auto-generate" a
> Cyrillic version of his book on top of the Latin edition with
> close-to-zero extra effort.
Ok, I can see that this may be a convenient way of producing different
output from the same source; I wasn't aware of this (and I was somewhat
provocative about Latex, of course :-) From a conceptional point of
view, it still feels a bit hackish to do these things on the font level,
because they are not/should not be tied to specific fonts - you'd have
to rewrite your features or goodies or whatever they are called now for
every font you want to use (and you may run into a number of funny
inconsistencies in character names or even unicode slots).
Thomas
___________________________________________________________________________________
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:[~2017-11-08 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 12:48 Sava Maksimović
2017-11-07 13:10 ` Mojca Miklavec
2017-11-07 19:38 ` Thomas A. Schmitz
2017-11-08 10:00 ` Ulrike Fischer
2017-11-08 10:34 ` Mojca Miklavec
2017-11-08 14:36 ` Thomas A. Schmitz [this message]
2017-11-08 15:09 ` Mojca Miklavec
2017-11-09 3:15 ` Henri
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=f2cd1625-85fc-aca0-8fd3-2a35ab3a8fae@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).