discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Fonts?
Date: Wed, 30 Jun 2010 16:40:24 +0200	[thread overview]
Message-ID: <20100630144024.GE24358@iris.usta.de> (raw)
In-Reply-To: <4C2B519A.6060606@bsd.lv>

Hi Kristaps,

Kristaps Dzonsons schrieb am Wed, Jun 30, 2010 at 04:15:54PM +0200:

> mandoc needs hard-coded glyph widths (font-metrics) or you'll get
> exactly these configuration questions.  Same goes with my question
> about dimensions and margins.

Aha.  So i understand you need to settle on a specific default font.
So be it...

> Your test with gv is the first time somebody's given independent
> feedback, so it's not fair to get angry (yet :-)).

Don't worry, I won't get angry about bugs, and I won't get angry
about experimentation with different design decisions either;
i might only get angry should the final design decisions turn
out, in the long run, to be constant sources of trouble.  :)

> The gv problems are with a lack of hinting in the PostScript file
> and unrelated to fonts.

All the better!

[...]
> You may not use the PostScript driver--I don't either--but when I first
> announced mandoc for both OpenBSD and NetBSD the first complaints were
> that it doesn't have -Tps.  Obviously somebody cares or I wouldn't be
> doing this.  If in fact nobody does care, a lot of time (and Google's
> money) are being spent for naught.

Don't worry!  Quite a few people do care, for example at least five
OpenBSD developers, probably more.

To be honest, right now, almost everybody considers ASCII rendering
issues more pressing then improved PostScript support, but as long
as we also get -Tascii up to OpenBSD quality standards in time for the
4.8 release, there is nothing wrong with developing -Tps in parallel.
Eventually, it will be a big asset.

> For the record, term_ps.c is pretty much as "complicated" as it's going
> to get.

I do not worry that much about a bit of additional code, in particular
when it is well modularized in *ps*.c files.  We need what we need.
Of course, bloat should be avoided, but it does not look like
anybody round here is prone to producing bloat.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-06-30 14:40 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     ` Ingo Schwarze [this message]
2010-06-30 15:10       ` Fonts? Kristaps Dzonsons
2010-06-30 20:36   ` Fonts? Dieter Baron
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=20100630144024.GE24358@iris.usta.de \
    --to=schwarze@usta.de \
    --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).