public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: nopria <mmj529-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: U+200B and LaTeX
Date: Wed, 18 Sep 2019 09:24:24 -0700	[thread overview]
Message-ID: <m25zlp4lon.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <45688658-4762-4910-b8d1-a28a23efd91c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


The question is how we should render U+200B zero-width space
in LaTeX. Currently we are just outputing the unicode character
(which should work okay with xelatex anyway).

Is there a better way?

We could just output {}, for example.

It's probably worth putting an issue on the tracker.

nopria <mmj529-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Converting from docbook to LaTeX I came across a possible uncorrect 
> management of U+200B when converting to LaTeX.
> The following docbook MWE (the simple string "...abc")
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?asciidoc-toc?>
> <?asciidoc-numbered?>
> <article xmlns="http://docbook.org/ns/docbook" xmlns:xl=
> "http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
> <simpara>&#8230;&#8203;abc</simpara>
>
> is converted to LaTeX
>
> \ldots​abc
>
> with a (invisible but detectable in the real output) zero-width-space 
> between "\ldots" and "abc".
>
> I think that the correct LaTeX output should be
>
> \ldots abc
>
> with a standard space after `\ldots`, because if you try to produce a PDF 
> you get
>
> [WARNING] Missing character: There is no ÔÇï (U+200B) in font [lmroman10-
> regular]:mapping=tex-text;!
>
> because of the presence of the zero-width-space, whereas with the standard 
> space you get the correct output ("...abc" and not "... abc") in PDF (and 
> no warnings).
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/45688658-4762-4910-b8d1-a28a23efd91c%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m25zlp4lon.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2019-09-18 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 10:05 nopria
     [not found] ` <45688658-4762-4910-b8d1-a28a23efd91c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-18 16:24   ` John MacFarlane [this message]
     [not found]     ` <m25zlp4lon.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-18 18:21       ` nopria

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=m25zlp4lon.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=mmj529-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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).