From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Retaking AUTO for \usepackage{fontenc}
Date: Tue, 13 Feb 2024 11:57:49 +0000 [thread overview]
Message-ID: <87wmr8a85e.fsf@posteo.net> (raw)
In-Reply-To: <CAO48Bk_tkzajm-BEKW86fNh92kshyQQEpJWx8rUNeDLtJ-H76A@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Tue, 13 Feb 2024 08:51:48 +0100")
Pedro Andres Aranda Gutierrez writes:
> Hi,
>
> Next step, @all, please help me filling up the list of codings vs.
> languages. I currently am somehow confident of the following:
>
> greek -> LGR
> russian -> T2A
The information is in the encguide PDF (you can run texdoc fontenc or
texdoc encguide). You should look especially at section 2.3 256 glyph
encodings. I don't know if some languages require more than one
encoding. Cyrillic appears to be T2A, T2B and T2C. T4 is for
"The African Latin fonts contain in their lower half (0–127) the same
characters as the European Latin (T1-encoded) Fonts, while in their
upper half (128–255) they contain letters and symbols for African
languages that use extended Latin alphabets."
etc.
But I can't find a simpler list anywhere.
Best regards,
Juan Manuel
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
next prev parent reply other threads:[~2024-02-13 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 6:36 Retaking AUTO for \usepackage{fontenc} Pedro Andres Aranda Gutierrez
2024-02-12 14:01 ` Ihor Radchenko
2024-02-13 7:51 ` Pedro Andres Aranda Gutierrez
2024-02-13 11:57 ` Juan Manuel Macías [this message]
2024-02-13 16:47 ` Pedro Andres Aranda Gutierrez
2024-02-13 17:22 ` Juan Manuel Macías
2024-02-14 14:55 ` Ihor Radchenko
2024-02-14 22:03 ` Juan Manuel Macías
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmr8a85e.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=paaguti@gmail.com \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).