help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mandoc.bsd.lv
Subject: Re: Bad national charachers renndering in PDF
Date: Mon, 19 Nov 2018 15:06:39 +0100	[thread overview]
Message-ID: <20181119140639.GC21123@athene.usta.de> (raw)
In-Reply-To: <340.1542635529@cathet.us>

Hi Marcin and Anthony,

Anthony J. Bentley wrote on Mon, Nov 19, 2018 at 06:52:09AM -0700:
> Marcin Karpezo writes:

>> I'm having troubles with rendering of Polish charachers in my pdf
>> exports. I've tried every options I've found in man and so on, but
>> without any results.

> Unfortunately mandoc's PDF output doesn't handle Unicode at all, and
> renders all special characters as ASCII. I am not sure what adding
> such support would entail (there might be font issues?).

At least that, yes.  For PostScript and PDF output, font metrics
for the Times New Roman ASCII font are currently hardcoded in
term_ps.c, the number of supported glyphs is limited to 96 glyphs
per font style, and no other font can be used.  Generalizing font
support would be a major undertaking.

> mandoc is
> great at rendering Unicode in the terminal and in HTML output, but
> getting Unicode in PDF manuals is currently a matter of using some
> other troff implementation.

That statement is accurate.  Groff is to be recommended for that
purpose because it has better mdoc(7) support than other troff
implementations (except mandoc, of course).

 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

  reply	other threads:[~2018-11-19 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 13:31 Marcin „sirmacik” Karpezo
2018-11-19 13:52 ` Anthony J. Bentley
2018-11-19 14:06   ` Ingo Schwarze [this message]
2018-11-19 14:19     ` Marcin „sirmacik” Karpezo
2018-11-19 16:07       ` Ingo Schwarze
2018-11-19 17:17         ` Marcin Karpezo
2018-11-19 14:07   ` Marcin „sirmacik” Karpezo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181119140639.GC21123@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mandoc.bsd.lv \
    --subject='Re: Bad national charachers renndering in PDF' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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