On 12/17/19, Asmus Freytag via Unicode <unicode@unicode.org> wrote: > On 12/17/2019 2:41 AM, Shriramana Sharma via Unicode wrote: >> >> On Tue 17 Dec, 2019, 16:09 QSJN 4 UKR via Unicode, <unicode@unicode.org> >> wrote: >>> >>> «The no-break space is not the same character as the figure space. The >>> figure space is not a character defined in most computer system's >>> current code pages. In some fonts this character's width has been >>> defined as equal to the figure width. This is an incorrect usage of >>> the character no-break space.» >> >> >> Sorry but I don't understand how this addresses the issue I raised. > > You don't? > > In principle it may be true that NBSP is not fixed width, but show me > software that doesn't treat it that way. > > In HTML, NBSP isn't subject to space collapse, therefore it's the go-to > space character when you need some extra spacing that doesn't disappear.
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. I don't expect NBSP to ever disappear, because spaces disappear only at linebreaks, and NBSP simply doesn't stand at linebreaks. -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा 𑀰𑁆𑀭𑀻𑀭𑀫𑀡𑀰𑀭𑁆𑀫𑀸