From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: ASCII input - non ASCII output
Date: Wed, 8 Nov 2017 11:00:53 +0100 [thread overview]
Message-ID: <1nw71rn8y52s7.dlg@nililand.de> (raw)
In-Reply-To: <a54c9186-81fd-d34e-b7b7-a17b775849bb@uni-bonn.de>
Am Tue, 7 Nov 2017 20:38:14 +0100 schrieb Thomas A. Schmitz:
>> In Latex, package fontenc(precisely OT2 encoding) do that things.
> Yes, LaTeX stays firmly in the 1970s. But the world has moved on.
And LaTeX has moved on too. You can use luatex and utf8 input with
it without problem and for the unicode engines an unicode
fontencoding and open type fonts are the default in the kernel. That
you still *can* use special fontencodings to mimic transliteration,
8-bit-engines and type1-fonts with LaTeX doesn't mean that you
*have* to use them. You have the choice.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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 10:00 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 [this message]
2017-11-08 10:34 ` Mojca Miklavec
2017-11-08 14:36 ` Thomas A. Schmitz
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=1nw71rn8y52s7.dlg@nililand.de \
--to=news3@nililand.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).