From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] Please support narrow no-break space (U+202F)
Date: Sun, 29 Aug 2010 23:52:16 +0100 [thread overview]
Message-ID: <20100829225216.GA6462@deepthought> (raw)
In-Reply-To: <1283121148.6204.15.camel@nicolas-home>
On Mon, Aug 30, 2010 at 12:32:28AM +0200, Nicolas Delvaux wrote:
>
> Indeed, it's logical, thanks.
>
> As a side note to this "feature request", there is other Unicode spaces
> you might want to support: http://en.wikipedia.org/wiki/Space_%
> 28punctuation%29#Table_of_spaces
> I let you see, personally I just need narrow non-break spaces. ;-)
>
> Nicolas
As a side-note to the request, you can change your local psfu fonts
using psftools (from freshmeat if your distro doesn't supply it):
txt2psf to reproduce the font in a text form ('-' for blank pixels,
'#' for lit pixels),
edit it to add more characters to the space glyph - e.g.
Unicode: [00000020];[000000a0];[0000202f];
(to add U+202f to an existing U+00a0).
and then txt2psf to convert the altered file to a psfu font.
I was interested to see your request, and _surprised_ that you have
this character mapped on your keyboard. I thought people would just
type a regular space - shows how little I know.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2010-08-29 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1282773735.2037.32.camel@nicolas-eisti>
2010-08-29 12:03 ` [kbd] Please support narrow no-break space (U+202F) Alexey Gladkov
[not found] ` <1283104206.2052.42.camel@nicolas-home>
2010-08-29 21:37 ` Ken Moffat
[not found] ` <1283121148.6204.15.camel@nicolas-home>
2010-08-29 22:52 ` Ken Moffat [this message]
[not found] ` <1283471403.10528.22.camel@nicolas-home>
[not found] ` <1283715553.2881.40.camel@nicolas-home>
2010-09-08 21:53 ` 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=20100829225216.GA6462@deepthought \
--to=zarniwhoop@ntlworld.com \
--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.