From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Matthew Burgess <matthew@linuxfromscratch.org>
Cc: kbd <kbd@lists.altlinux.org>
Subject: Re: [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1
Date: Thu, 12 Feb 2009 01:17:54 +0300 [thread overview]
Message-ID: <49934E92.9080805@gmail.com> (raw)
In-Reply-To: <d0239282eabaf6acc990ed5b73297d1d@quantum.linuxfromscratch.org>
Matthew Burgess wrote:
> Hi Alexey,
>
> I'm viewing man pages using a combination of groff-1.20.1 and the lat1-16
> font from kbd-1.15. You can see the results of this at
> http://www.linuxfromscratch.org/~matthew/test-results/preconv.en_utf8.jpg.
>
> As you can see, the line-break character (U+2010) isn't displayed correctly.
>
> We used to workaround this with previous versions of Groff by substituting
> U+2010, U+2212 to U+002D (minus sign). See
It seems that these characters are not mapped at all. At least the U+2010.
> http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/groff.html. Due to
> a change in Groff, that substitution no longer applies.
>
> Is it possible to map those characters like that in the lat1-16 font itself?
> That way, if there happen to be any other programs that output the
> problematic characters, they'll display correctly without any further changes.
>
> If so, how might we go about this, and is this suitable for the upstream
> Kbd package sources?
I think we can map this characters if they not mapped at all.
P.S. Add CC: kbd@lists.
Anyone have any ideas ?
--
Rgrds, legion
next parent reply other threads:[~2009-02-11 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d0239282eabaf6acc990ed5b73297d1d@quantum.linuxfromscratch.org>
2009-02-11 22:17 ` Alexey Gladkov [this message]
2009-02-12 16:12 ` [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1 Lefteris Dimitroulakis
[not found] <200902121900.03293.edimitro@tee.gr>
2009-02-16 23:50 ` Matthew Burgess
2009-02-18 21:22 ` Alexey Gladkov
[not found] <49A78A87.3000900@gmail.com>
2009-02-28 18:09 ` Matthew Burgess
2009-03-06 23:55 ` Alexey Gladkov
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=49934E92.9080805@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
--cc=matthew@linuxfromscratch.org \
/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