From: keld@keldix.com
To: Kalle Olavi Niemitalo <kon@iki.fi>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [RFC][PATCH][BZ 20756] Locales: Use Unicode wise thousands separator
Date: Thu, 03 Nov 2016 08:07:00 -0000 [thread overview]
Message-ID: <20161103080723.GA24234@www5.open-std.org> (raw)
In-Reply-To: <8760o5771m.fsf@Niukka.kon.iki.fi>
I agree to change space to something else. Given the problems mentioned below with fonts,
maybe a good way forward is to use NBSP, which should be available in all fonts,
and also is available in olden 8-bit charsets, that are still in use.
Best regards
Keld
On Thu, Nov 03, 2016 at 02:15:17AM +0200, Kalle Olavi Niemitalo wrote:
> Stanislav Brabec <sbrabec@suse.cz> writes:
>
> > In non-proportional fonts, NNBSP renders as a standard width space
> > (NBSP), so there should not be a problem as well.
>
> My Emacs 23 displays U+202F as a rectangle in many fonts, e.g.
> -Adobe-Helvetica-Medium-R-Normal--17-120-100-100-P-88-ISO10646-1
> (helvR12.pcf.gz from xfonts-100dpi 1:1.0.3 on Debian 8.6).
> Playing around with xfontsel -sampleUCS and xfd -fn, I see that
> -Misc-Fixed-Bold-R-Normal--18-120-100-100-C-90-ISO10646-1
> (9x18B.pcf.gz from xfonts-base 1:1.0.3 on Debian 8.6) likewise
> displays a rectangle, but the non-bold variant (9x18.pcf.gz)
> displays a space for U+202F.
>
> Maybe things look better with FreeType but not everything uses that.
next prev parent reply other threads:[~2016-11-03 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 15:53 Stanislav Brabec
2016-11-02 16:24 ` keld
2016-11-02 16:37 ` Stanislav Brabec
2016-11-02 16:54 ` Carlos O'Donell
2016-11-03 0:14 ` Kalle Olavi Niemitalo
2016-11-03 8:07 ` keld [this message]
2016-11-03 8:32 ` Andreas Schwab
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=20161103080723.GA24234@www5.open-std.org \
--to=keld@keldix.com \
--cc=kon@iki.fi \
--cc=libc-alpha@sourceware.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).