From: Lefteris Dimitroulakis <edimitro@tee.gr>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1
Date: Thu, 12 Feb 2009 18:12:56 +0200 [thread overview]
Message-ID: <200902121812.56579.edimitro@tee.gr> (raw)
In-Reply-To: <49934E92.9080805@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
Στις Thursday 12 February 2009 00:17:54 ο/η Alexey Gladkov έγραψε:
> 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.
>
I don't see any problem so I am attaching newlat1-16.psfu with new mappings
U+2010, U+2012, U+2013 and U+2212 to U+002d.
If someone wish to play with and change mappings here it is:
$psfgettable lat1-16.psfu > table.txt
Editing table.txt ---> newtable.txt with our preferences and then
$psfaddtable lat1-16.psfu newtable.txt newlat1-16.psfu.
cheers
Lefteris
[-- Attachment #2: newlat1-16.psfu.gz --]
[-- Type: application/x-gzip, Size: 1984 bytes --]
next prev parent reply other threads:[~2009-02-12 16:12 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 ` [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1 Alexey Gladkov
2009-02-12 16:12 ` Lefteris Dimitroulakis [this message]
[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=200902121812.56579.edimitro@tee.gr \
--to=edimitro@tee.gr \
--cc=kbd@lists.altlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.