From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: kbd@lists.altlinux.org
Subject: Re: [kbd] Please support narrow no-break space (U+202F)
Date: Thu, 09 Sep 2010 01:53:11 +0400 [thread overview]
Message-ID: <4C8805C7.7020002@gmail.com> (raw)
In-Reply-To: <1283715553.2881.40.camel@nicolas-home>
05.09.2010 23:39, Nicolas Delvaux wrote:
> Does it feel as a proper fix for you? If not, how can I improve it?
I added your patch and new fonts, but I need more testing it. Thanks!
http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=commitdiff;h=50f674d1775bc75f799c583b887c3329088ff620
--
Rgrds, legion
prev parent reply other threads:[~2010-09-08 21:53 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
[not found] ` <1283471403.10528.22.camel@nicolas-home>
[not found] ` <1283715553.2881.40.camel@nicolas-home>
2010-09-08 21:53 ` Alexey Gladkov [this message]
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=4C8805C7.7020002@gmail.com \
--to=gladkov.alexey@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).