From: Matthew Burgess <matthew@linuxfromscratch.org> To: kbd <kbd@lists.altlinux.org> Subject: Re: [kbd] kbd-1.15 lat1-16 font issues with groff-1.20.1 Date: Sat, 28 Feb 2009 11:09:05 -0700 Message-ID: <e91be5679e9d5a90650faeb4107ad06d@quantum.linuxfromscratch.org> (raw) In-Reply-To: <49A78A87.3000900@gmail.com> [-- Attachment #1: Type: text/plain, Size: 1061 bytes --] On Fri, 27 Feb 2009 09:39:03 +0300, Alexey Gladkov <gladkov.alexey@gmail.com> wrote: > Matthew Burgess wrote: >> 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? > > I think patch is better. OK, here's the patch against the output of 'pdfgettable lat1-16.psfu lat1-16.table.orig' I've also added mappings for the 2 'quote' type characters that GCC outputs in some of its warnings. Regards, Matt. [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: kbd-1.15-lat1_16_hyphen-1.patch --] [-- Type: text/x-diff; name="kbd-1.15-lat1_16_hyphen-1.patch", Size: 164 bytes --] 43c43 < 0x027 U+0027 --- > 0x027 U+0027 U+2019 49c49 < 0x02d U+002d --- > 0x02d U+002d U+2010 U+2012 U+2013 U+2212 100c100 < 0x060 U+0060 --- > 0x060 U+0060 U+2018
next parent reply other threads:[~2009-02-28 18:09 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-28 18:09 ` Matthew Burgess [this message] 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=e91be5679e9d5a90650faeb4107ad06d@quantum.linuxfromscratch.org \ --to=matthew@linuxfromscratch.org \ --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
Linux console tools development discussion This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/kbd/0 kbd/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 kbd kbd/ http://lore.altlinux.org/kbd \ kbd@lists.altlinux.org kbd@lists.altlinux.ru kbd@lists.altlinux.com public-inbox-index kbd Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.kbd AGPL code for this site: git clone https://public-inbox.org/public-inbox.git