discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Dieter Baron <dillo@danbala.ifoer.tuwien.ac.at>
To: discuss@mdocml.bsd.lv
Subject: Re: Fonts?
Date: Wed, 30 Jun 2010 22:36:24 +0200	[thread overview]
Message-ID: <20100630203624.GD6880@danbala.tuwien.ac.at> (raw)
In-Reply-To: <20100630131222.GA24358@iris.usta.de>

hi,
   
> > Which font do you suggest I use for the hard-coded font value?
>  
> Basically, i don't know anything about fonts and don't care
> either, except that:
> 
>  * Please make sure to use something which is guaranteed to be
>    available everywhere by default without requiring users to
>    install anything, or if such stuff does not exist, use
>    generic settings if feasible.  I will never feed any font-
>    related arguments, options or parameters into mandoc and
>    will never set up any font-related configuration files,
>    and if mandoc ever asks me any questions about fonts or
>    produces any font-related error messages, i will get
>    really upset.
  
  Fear not, that is my goal (and Kristaps, I presume) as well.  Using
either Times or Palatino ensures the font's availability on any sane
PostScript (or PDF) viewer.  (Any PostScript viewer that doesn't
include these two fonts would have problems displaying heaps of other
documents as well.)
  
>  * Please do not use anything fancy, neither from the point of
>    view of design, nor from a technical point of view.  Just use
>    the most standard and boring stuff you can find.
  
  The most boring stuff would be Times, which is a good default, I
guess. 
  
> I would also suggest not to waste any time on fonts,
> but of course that is your call.  I don't see the point of  
> making anything about fonts configurable.  We are not in
> marketing, we are formatting manuals!
  
  For now, one hardcoded font is certainly fine.  However, I do see an
argument for making fonts selectable at run time: embedding the
resulting pages in a larger work, so they fit with the layout of other
parts of that work (e.g. book).  But let's not worry about that at the
moment.
  
> > Whatever's chosen, I'll need a suitable AFM for the WX value.
> 
> No idea what you are talking about.
  
  Font metrics: how wide each char is, so they can be placed
correctly, and line breaks can be made at the right points.
  
  
  I'm confident that my know how in this area (typography and
PostScript) is sufficient to solve these problems.  However, I can't
reply to mails with the speed you two display.  So, please be patient,
and give me at least two days to reply.
  
                                        yours,
                                        dillo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2010-06-30 20:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 11:15 Fonts? Kristaps Dzonsons
2010-06-30 13:12 ` Fonts? Ingo Schwarze
2010-06-30 14:15   ` Fonts? Kristaps Dzonsons
2010-06-30 14:40     ` Fonts? Ingo Schwarze
2010-06-30 15:10       ` Fonts? Kristaps Dzonsons
2010-06-30 20:36   ` Dieter Baron [this message]
2010-06-30 21:00     ` Fonts? Kristaps Dzonsons
2010-06-30 21:02     ` Fonts? Ingo Schwarze
     [not found] ` <3CFC79CF-AFDC-4F2A-A871-4D64F64B461B@danbala.tuwien.ac.at>
2010-06-30 13:21   ` Fonts? Kristaps Dzonsons
2010-06-30 13:25     ` Fonts? Ingo Schwarze
2010-06-30 13:27       ` Fonts? Jason McIntyre
2010-06-30 13:38         ` Fonts? Kristaps Dzonsons
2010-06-30 13:41           ` Fonts? Kristaps Dzonsons
2010-06-30 13:55           ` Fonts? Ingo Schwarze
2010-06-30 15:20     ` [FIXED] Fonts? Kristaps Dzonsons

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=20100630203624.GD6880@danbala.tuwien.ac.at \
    --to=dillo@danbala.ifoer.tuwien.ac.at \
    --cc=discuss@mdocml.bsd.lv \
    /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).