discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Marcin Karpezo <marcin@karpezo.pl>
To: discuss@mandoc.bsd.lv
Subject: Re: Bad national charachers renndering in PDF
Date: Mon, 19 Nov 2018 18:17:04 +0100	[thread overview]
Message-ID: <20181119171701.GA12677@mail.freearts.agency> (raw)
In-Reply-To: <20181119160729.GD21123@athene.usta.de>

Ingo Schwarze dixit (2018-11-19, 17:07):

> Hi Marcin,
> 
> Marcin Karpezo wrote on Mon, Nov 19, 2018 at 03:19:53PM +0100:
> 
> > Do you by any chance have some command example to get that from Groff? 
> > I've tried several options I've found in manuals and onlie sources but
> > results look worse then mandoc output. Charachers are either printent
> > with fre alphanums or do not printed at all. 
> 
> A default installation of the groff PostScript and PDF output devices
> does not include a font that supports the Polish language.  Did you
> install such a font?  If not, the gropdf(1) manual page explains
> how to do that, below "FONT INSTALLATION".
> 
> Once you have a font installed, both of the following commands are
> supposed to work:
> 
>  $ groff -k -mandoc -T pdf /usr/local/man/pl/man6/wesnothd.6 > /tmp/tmp.pdf
>  $ pdfroff -k -mandoc /usr/local/man/pl/man6/wesnothd.6 > /tmp/tmp.pdf
> 
> (Sorry for the silly example, that's the only Polish manual page
> i happen to have installed right now...)
> 
> In addition to the options shown above, you might also need the -f
> option documented in the groff(1) manual page to actually select the
> font family you just installed instead of the default, Times New Roman.
> 
> If you have no suitable font family installed, you will see error
> messages similar to the following, and wrong glyphs in the output
> file:
> 
> troff: wesnothd.6:29: warning: can't find special character 'u0073_0301'
> troff: wesnothd.6:29: warning: can't find special character 'u007A_0307'
> troff: wesnothd.6:46: warning: can't find special character 'u0065_0328'
> troff: wesnothd.6:46: warning: can't find special character 'u0061_0328'
> troff: wesnothd.6:53: warning: can't find special character 'u006E_0301'
> troff: wesnothd.6:158: warning: can't find special character 'u0053_0301'
> troff: wesnothd.6:297: warning: can't find special character 'u005A_0307'
> troff: wesnothd.6:297: warning: can't find special character 'u0045_0328'
> troff: wesnothd.6:297: warning: can't find special character 'u0041_0328'
> 
> While mandoc tries to make *reading* manual pages simple and hence
> does not require any fancy options or configuration for the -T utf8
> and -T html output modes, real typesetting to PostScript or PDF is
> unfortunately still somewhat tricky even in the 21st century and
> still requires configuring quite a bit of stuff...  :-(

This is just amazing, thank you for your time and such an extensive
instructions! 

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

  reply	other threads:[~2018-11-19 17:17 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
2018-11-19 14:19     ` Marcin „sirmacik” Karpezo
2018-11-19 16:07       ` Ingo Schwarze
2018-11-19 17:17         ` Marcin Karpezo [this message]
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:
  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=20181119171701.GA12677@mail.freearts.agency \
    --to=marcin@karpezo.pl \
    --cc=discuss@mandoc.bsd.lv \
    --subject='Re: Bad national charachers renndering in PDF' \
    /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

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