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 22:37:34 +0100 [thread overview]
Message-ID: <20100829213733.GA5127@deepthought> (raw)
In-Reply-To: <1283104206.2052.42.camel@nicolas-home>
On Sun, Aug 29, 2010 at 07:50:06PM +0200, Nicolas Delvaux wrote:
>
> Of course it would be better if nnbsp were at least "unbreakable" but,
> with the current kbd, even non-break spaces break (because they are
> mapped to 0x20). Perhaps this is by design, I don't know.
>
The console fonts run in a tty. I think the appropriate
description might be "what you ask for is what you get".
If you are looking at html in a browser, the browser makes decisions
about how to process the nbsp entity. But for plain text, you get
what the current font produces for that character. The font doesn't
add a linefeed of its own accord - long lines just appear to wrap onto
the next line of the screen.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2010-08-29 21:37 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 [this message]
[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
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=20100829213733.GA5127@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox