public inbox for kbd@lists.linux.dev
 help / color / mirror / Atom feed
From: Matthew Burgess <matthew@linuxfromscratch.org>
To: edimitro@tee.gr
Cc: kbd@lists.altlinux.org
Subject: Re: [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1
Date: Mon, 16 Feb 2009 16:50:43 -0700	[thread overview]
Message-ID: <9f4dcca5e71f960b98653ae5380e647d@quantum.linuxfromscratch.org> (raw)
In-Reply-To: <200902121900.03293.edimitro@tee.gr>

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

On Thu, 12 Feb 2009 19:00:03 +0200, Lefteris Dimitroulakis <edimitro@tee.gr> wrote:

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

For some reason, your newlat1-16.psfu didn't work for me (setfont
complained of bad input file size, psfgettable complained of bad magic
number).  I suspect this was just a download issue.  I followed your other
instructions and have managed to get it working with the font file (also at
http://www.linuxfromscratch.org/~matthew/lat1-16.psfu.gz).

Alexey, is that file suitable for inclusion in kbd, or do you want a patch against
the 'psfgettable' for lat1-16?

Thanks for you help!

Matt.

[-- Attachment #2: lat1-16.psfu.gz --]
[-- Type: application/x-gzip, Size: 1990 bytes --]

       reply	other threads:[~2009-02-16 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200902121900.03293.edimitro@tee.gr>
2009-02-16 23:50 ` Matthew Burgess [this message]
2009-02-18 21:22   ` [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1 Alexey Gladkov
     [not found] <49A78A87.3000900@gmail.com>
2009-02-28 18:09 ` Matthew Burgess
2009-03-06 23:55   ` Alexey Gladkov
     [not found] <d0239282eabaf6acc990ed5b73297d1d@quantum.linuxfromscratch.org>
2009-02-11 22:17 ` Alexey Gladkov
2009-02-12 16:12   ` Lefteris Dimitroulakis

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=9f4dcca5e71f960b98653ae5380e647d@quantum.linuxfromscratch.org \
    --to=matthew@linuxfromscratch.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox