From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Tim Cross <theophilusx@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-mode export to (latex) PDF
Date: Thu, 15 Jul 2021 12:06:59 +0000 [thread overview]
Message-ID: <87bl73srvg.fsf@posteo.net> (raw)
In-Reply-To: <87eec0qx9j.fsf@gmail.com> (Tim Cross's message of "Thu, 15 Jul 2021 09:26:15 +1000")
Tim Cross writes:
> Stefan Nobis <stefan-ml@snobis.de> writes:
>> But maybe we could assemble a list of good (enough) fonts for
>> different languages/scripts and provide a default setup in Org for
>> LaTeX export, that sets a proper font for the chosen document
>> language?
> I think such a list would be a really good addition to worg.
I think it's a great idea. Some resources on fonts and languages that
may be useful:
- The LaTeX Font Catalogue (https://tug.org/FontCatalogue/) is pretty
complete and includes a lot of high quality fonts, with coverage for
many languages. The fonts are from diverse origins, for example the
excellent fonts for Greek and Latin alphabets from the Greek Font
Society, the TeX Gyre project fonts, etc.
- To get quick information from an otf font (otf features, Unicode
ranges, scripts, glyphs, etc.) otfinfo is very useful
(https://man.archlinux.org/man/otfinfo.1.en). But the more powerful
tool in this regard is fontforge (https://fontforge.org/en-US/), which
is not only a complete professional font editor (and free as in
freedom) but can also be used by everyone to audit all aspects from a
font: glyphs, metadata, otf features, languages, scripts, ranges, etc.
- There are specialized fonts in a wide coverage of ranges and scripts,
but many are low-quality or proprietary. Google's Noto Fonts ensure at
least a reasonably complete coverage: I use them only for experiments
(or for ensure certain "rare" scripts in Emacs buffers, as Linear B or
Gothic), but they can also be used within a document.
- Finally, in case anyone is interested, I also wrote for my personal
use a Helm source to list all system font families and insert the
family name into a LaTeX document with the syntax of fontspec or Babel
("\babelfont", which is a frontend for fontspec).
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-07-15 12:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 13:42 org-mode export to (latex) PDF Jean-Christophe Helary
2021-07-10 13:52 ` Juan Manuel Macías
2021-07-10 14:13 ` Jean-Christophe Helary
2021-07-10 14:38 ` Juan Manuel Macías
2021-07-10 14:59 ` Tim Cross
2021-07-10 17:40 ` Juan Manuel Macías
2021-07-12 3:09 ` Tim Cross
2021-07-12 8:15 ` Eric S Fraga
2021-07-10 15:01 ` Jean-Christophe Helary
2021-07-10 16:13 ` Maxim Nikulin
2021-07-10 16:44 ` Stefan Nobis
2021-07-13 16:53 ` Maxim Nikulin
2021-07-13 17:53 ` Juan Manuel Macías
2021-07-14 6:44 ` Stefan Nobis
2021-07-14 17:30 ` Maxim Nikulin
2021-07-14 19:05 ` Stefan Nobis
2021-07-14 23:26 ` Tim Cross
2021-07-15 12:06 ` Juan Manuel Macías [this message]
2021-07-15 17:10 ` Maxim Nikulin
2021-07-15 19:40 ` Juan Manuel Macías
2021-07-16 16:56 ` Maxim Nikulin
2021-07-16 18:34 ` Juan Manuel Macías
2021-07-17 12:35 ` Maxim Nikulin
2021-07-17 14:27 ` Juan Manuel Macías
2021-07-16 9:20 ` Stefan Nobis
2021-07-16 10:38 ` Jean-Christophe Helary
2021-07-16 11:11 ` Stefan Nobis
2021-07-16 5:58 ` Jean-Christophe Helary
2021-07-14 19:29 ` Juan Manuel Macías
2021-07-10 18:43 ` Jonathan McHugh
2021-07-10 19:24 ` 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=87bl73srvg.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@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.
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).