Alexander Savenkov suggested:
Why not? I think Peter needs a good book on typesetting to find out
what is inserted inserted between Louis and XIV. In this case IIRC
there should be the following sequence: Louis,ZWNBSP,SP,ZWNBSP,XIV.
Kenneth Whistler replied:
Uh, no. ZWNBSP, SPACE, ZWNBSP
Hello,
and sorry for the late response.
2004-04-01T05:41:02+03:00 fantasai [EMAIL PROTECTED] wrote:
But, as Ken has just clarified, with NBSP Louis' neck may be
stretched rather uncomfortably, if not cut completely. Here is what I
don't want to see (fixed width font required):
Louis XVI
Hello,
sorry for the late response.
2004-04-01T03:47:40+03:00 Kenneth Whistler [EMAIL PROTECTED] wrote:
Other possible approaches that any industrial-strength
typesetting program ought to provide:
...
The point is that looking to encode a special character in
Unicode for every distinct
It only affects its (visual) aesthetic
quality.
That is arguable. An aural user agent could pronounce 1, 2, 3 a bit
different from 1, 2, 3 if there is a (say) thin space between the
digits in the latter case. It could pronounce it quicker, for example.
And it could read it as thin
Somebody wrote:
non-breaking and non-stretching are presentational properties, not
semantic ones. They don't change the meaning of the space: it's still
just a space, not a hyphen or the letter g. They don't affect
non-visual media; we don't break lines in spoken speech. Louis XVI
is
5 matches
Mail list logo
