Re: [Lynx-dev] non-breaking space breaks justification

[Ian Collier]

On Wed, Aug 09, 2023 at 10:58:52PM +0000, Thorsten Glaser wrote:
> Some fanfiction is written like this:

> <p>[10*U+00A0][the actual long paragraph text]</p>

> This renders okay-ish in lynx, but the first p line is thus not
> justified, leading to awful reading like:

> [...]
>                The manic leader was disturbed from his thoughts as he heard
>    footsteps go past his door. That must be Tabby. The man looked down to the 
> corner
>    of  his  computer  screen to see the clock display. Ah, it was breakfast 
> time for
> [...]

What's awful about that is you've formatted it for more than 80 columns...

> I've looked a bit at the source code, and I understand that there
> is a deliberate decision to not justify if the line contains U+00A0

If you use "lynx -justify" (why would anyone use that?) then it seems there
are two things going on in sequence: (1) break the paragraph up into lines
of the right length, and (2) add extra spaces to justify the right margin.
The first of these things happens the same, regardless; the second appears
to be omitted for any resulting line that contains U+00A0.

I'd say that it just shouldn't be omitted - I can't think of any reason
why that would be useful.  (I'm assuming here that anything within <pre>
tags is not justified, and if you write ascii art without putting it
within <pre> tags then you deserve what you get.)

The rest of your message would have been clearer if you hadn't
confused "justify" with "indent".  However, making allowances for
people who randomly (and perhaps mistakenly) add U+00A0 to add extra
space between words isn't really Lynx's job.  The extra space should
stay as the author intended (or didn't intend, whatever).

imc