[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#749891: marked as done (pandoc: doesn't support some Unicode characters with PDF output)

Your message dated Fri, 12 Jun 2020 21:40:22 +0200
with message-id <159199082276.4184237.949528776698790683@auryn.jones.dk>
and subject line Re: [Pkg-haskell-maintainers] Bug#749891: pandoc: doesn't support some      Unicode characters with PDF output
has caused the Debian Bug report #749891,
regarding pandoc: doesn't support some Unicode characters with PDF output
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

749891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749891
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: pandoc
Severity: normal

$ cat file
a ≤ b
$ pandoc file -o out.pdf
pandoc: Error producing PDF from TeX source.
! Package inputenc Error: Unicode char \u8:≤ not set up for use with LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
l.50 a ≤

Try running pandoc with --latex-engine=xelatex.


If I try with --latex-engine=xelatex, I no longer get an error, but
the "≤" character doesn't appear. There are similar problems with
other characters. See e.g. Markus Kuhn's UTF-8-demo.txt from:


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pandoc depends on:
ii  libc6        2.18-7
ii  libffi6      3.1~rc1+r3.0.13-12
ii  libgmp10     2:6.0.0+dfsg-4
ii  libicu52     52.1-3
ii  liblua5.1-0  5.1.5-5
ii  libpcre3     1:8.31-5
ii  libyaml-0-2  0.1.4-3.2
ii  pandoc-data
ii  zlib1g       1:1.2.8.dfsg-1

pandoc recommends no packages.

Versions of packages pandoc suggests:
pn  etoolbox                   <none>
pn  pandoc-citeproc            <none>
ii  texlive-latex-recommended  2014.20140528-1
ii  texlive-luatex             2014.20140528-1
ii  texlive-xetex              2014.20140528-1

-- no debconf information

--- End Message ---
--- Begin Message ---
Quoting Vincent Lefevre (2014-05-30 17:28:05)
> On 2014-05-30 07:47:08 -0700, John MacFarlane wrote:
> > Most likely this is because you're using a font that doesn't have
> > these glyphs.  Try with
> > 
> >    -V mainfont="FONT NAME"
> > 
> > where FONT NAME is a (ttf) font you have installed that has the 
> > character in question.
> Using mainfont='DejaVu Sans Mono' works, but
> * by default, pandoc should use a font that has the character in
> question (the default X11 fonts have it);
> * if the character isn't present, it should output an error.
> But if pandoc had correct pdflatex support, there would be no
> problems (I use UTF-8 math characters in my LaTeX files without
> any problem).

Pandoc could indeed by default use a font like Noto which strives 
towards universal glyph coverage (even if arguably dull looking).

Or it could by default us a nice modern looking font.

Or a nice classic looking font.

Pandoc makes no promise about its choice of default font, and it is 
therefore not a bug that _your_ expectations are not met.

Thanks for reporting this, and arguing your case.  I will however close 
this as a non-bug.

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

--- End Message ---

Reply to: