Il giorno mercoledì 18 settembre 2019 18:24:40 UTC+2, John MacFarlane ha scritto:
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 <mmj...-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>…​abc</simpara>
>
> is converted to LaTeX
>
> \ldotsabc
>
> 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-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/45688658-4762-4910-b8d1-a28a23efd91c%40googlegroups.com.