emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Rob Sargent <rsargent@xmission.com>, emacs-orgmode@gnu.org
Subject: Re: how to add special glyphs
Date: Wed, 8 Mar 2023 21:59:31 +0700	[thread overview]
Message-ID: <c445e8e9-08dc-e8ba-24cd-31d80b5141ab@gmail.com> (raw)
In-Reply-To: <950d033d-a53c-3fe5-ec58-b10a7e032127@xmission.com>

On 08/03/2023 07:29, Rob Sargent wrote:
>> LuaLaTeX may be instructed to use fallback fonts, see e.g.
>> To my taste it is too low level.
> That I placed the unicode into the text was "too low level"?  I could 
> argue that "it's a UTF doc", or that "\ding{55}" is bizarrely high 
> level.  Other's have shown methods which maximize the cross export 
> experience.  I'll consider those.  I'm not sure LuaLaTex is an option 
> for me.

I would prefer to use Unicode symbols in UTF-8 encoded documents. While 
browsers and office software tries to find some substitution when some 
glyph is not available in requested font, configuration of LaTeX engines 
is more complicated. Support of Unicode in LuaTeX is much better than in 
pdfTeX. Unfortunately for characters outside of ~latin-1 set, all fonts 
must be carefully configured. I consider necessity to specify font per 
language and fallback fonts as too low level operations for regular users.

I do not see a robust way to determine fonts available for LaTeX to 
implement automatic configuration in ox-latex with reasonable amount of 

I recommend to consider LuaLaTeX if you are going to use Unicode. 
Alternatives are PDF export through LibreOffice or through HTML and a 

  reply	other threads:[~2023-03-08 15:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 15:42 how to add special glyphs Rob Sargent
2023-03-06 17:37 ` Thomas S. Dye
2023-03-06 17:42   ` Rob Sargent
2023-03-06 22:23     ` Rob Sargent
2023-03-06 23:06       ` Thomas S. Dye
2023-03-06 23:24         ` Rob Sargent
2023-03-07 10:48           ` Fraga, Eric
2023-03-07 14:05       ` Ihor Radchenko
2023-03-07 15:54 ` Max Nikulin
2023-03-08  0:29   ` Rob Sargent
2023-03-08 14:59     ` Max Nikulin [this message]
2023-03-08 15:17       ` Rob Sargent
2023-03-08 10:08 Pedro Andres Aranda Gutierrez
2023-03-08 15:14 ` Rob Sargent
2023-03-08 16:53   ` Pedro Andres Aranda Gutierrez

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:

  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=c445e8e9-08dc-e8ba-24cd-31d80b5141ab@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rsargent@xmission.com \


* 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


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).