Freytag" , "UnicoDe List"
Betreff: Re: Re: NBSP supposed to stretch, right?
So I was wondering whether TeX only does this to the ~ input character or the actual NBSP Unicode character too?
So I was wondering whether TeX only does this to the ~ input character or
the actual NBSP Unicode character too?
unlike usual space tokens that are collapsed to one space token.
-- Jörg Knappen
Gesendet: Dienstag, 17. Dezember 2019 um 17:20 Uhr
Von: "Asmus Freytag via Unicode"
An: unicode@unicode.org
Betreff: Re: NBSP supposed to stretch, right?
On 12/17/2019 2:41 AM, Shriramana Sharma via Uni
On 12/19/19, James Kass via Unicode wrote:
>
> There's a bug report for the LibreOffice application here...
> https://bugs.documentfoundation.org/show_bug.cgi?id=41652
> ...which shows an interesting history of the situation.
LOL two years ago almost to the date Shriramana Sharma seems to have
On 2019-12-21 2:43 AM, Shriramana Sharma via Unicode wrote:
Ohkay and that's very nice meaningful feedback from actual
developer+user interaction. So the way I look at this going forward is
that we have four options:
1)
With the existing single NBSP character, provide a software option to
On 12/21/19, Richard Wordingham via Unicode wrote:
> On Fri, 20 Dec 2019 17:25:17 +0530
> Shriramana Sharma via Unicode wrote:
>
>> I don't expect NBSP to ever disappear, because spaces disappear only
>> at linebreaks, and NBSP simply doesn't stand at linebreaks.
>
> I can certainly imagine
On 12/21/19, Shriramana Sharma wrote:
> 1)
>
> With the existing single NBSP character, provide a software option to
> either make it flexible or inflexible, but this preference should be
> stored as part of the document and not the application settings, else
> shared documents would not preserve
On 12/21/19, Murray Sargent wrote:
> I checked with the Word team and they actually tried out stretching NBSP
> back in 2015 in the "good client" mode. But customer feedback was negative.
> The problem is that NBSP is used sometimes when stretching isn't wanted such
> as between the end of a
On Fri, 20 Dec 2019 17:25:17 +0530
Shriramana Sharma via Unicode wrote:
> So I never asked for NBSP to disappear. I said I want it to *stretch*.
> And to my mind "stretch" means to become wider than one's normal
> width. It doesn't include decreasing or disappearing width.
Don't spaces
From our colleague’s web site,
http://jkorpela.fi/chars/spaces.html
“On web browsers, no-break spaces tended to be non-adjustable, but
modern browsers generally stretch them on justification.”
Jukka Korpela then offers pointers about avoiding unwanted stretching.
and
“The change in the
On 2019-12-17 12:50 AM, Shriramana Sharma via Unicode wrote:
I would have gone and filed this as a LibreOffice bug since that's the
software I use most, but when I found this is a cross-software
problem, I thought it would be best to have this discussed and
documented here (and in a future
U+0020 SPACE
U+00A0 NO-BREAK SPACE
These two characters are equal in every way except that one of them
offers an opportunity for a line break and the other does not.
If the above statement is true, then any conformant application must
treat/process/display both characters identically.
On 12/17/2019 5:49 PM, James Kass via
Unicode wrote:
Asmus Freytag wrote,
> And any recommendation that is not compatible with what the
overwhelming
> majority of software has been doing should be ignored (or
only
Asmus Freytag wrote,
> And any recommendation that is not compatible with what the overwhelming
> majority of software has been doing should be ignored (or only
enabled on
> explicit user input).
>
> Otherwise, you'll just advocating for a massively breaking change.
It seems like the
On 12/17/2019 11:31 AM, James Kass via
Unicode wrote:
So it
follows that any justification operation should treat NO-BREAK
SPACE and SPACE identically.
And any recommendation that is not
compatible with what the overwhelming majority of software
On Tue, 17 Dec 2019 06:20:39 +0530
Shriramana Sharma via Unicode wrote:
> Hello. I've just tested LibreOffice, Google Docs and MS Office on
> Linux, Android and Windows, and it seems that NBSP doesn't get
> stretched like the normal space character when justified alignment
> requires it.
>
>
On 2019-12-17 10:37 AM, QSJN 4 UKR via Unicode wrote:
Agree.
By the way, it is common practice to use multiple nbsp in a row to
create a larger span. In my opinion, it is wrong to replace fixed
width spaces with non-breaking spaces.
Quote from Microsoft Typography Character design standards:
On 12/17/2019 2:41 AM, Shriramana
Sharma via Unicode wrote:
On Tue 17 Dec, 2019, 16:09
QSJN 4 UKR via Unicode,
wrote:
Agree.
By the way,
On Tue 17 Dec, 2019, 16:09 QSJN 4 UKR via Unicode,
wrote:
> Agree.
> By the way, it is common practice to use multiple nbsp in a row to
> create a larger span. In my opinion, it is wrong to replace fixed
> width spaces with non-breaking spaces.
> Quote from Microsoft Typography Character design
Agree.
By the way, it is common practice to use multiple nbsp in a row to
create a larger span. In my opinion, it is wrong to replace fixed
width spaces with non-breaking spaces.
Quote from Microsoft Typography Character design standards:
«The no-break space is not the same character as the figure
Hello. I've just tested LibreOffice, Google Docs and MS Office on
Linux, Android and Windows, and it seems that NBSP doesn't get
stretched like the normal space character when justified alignment
requires it.
Let me explain. I'm creating a document with the following text
typeset in 12 pt Lohit
21 matches
Mail list logo