[bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented

[Dave]

Follow-up Comment #3, bug #58962 (project groff):

[comment #0 original submission:]
> Either way, if Latin-1 A0 behaves the same as one of "\ " or
> "\~", the output-equivalency conditional operator (rendered
> as 'XXX'YYY' in the info manual, though a host of characters
> besides single quotes can be used) ought to recognize this.

What this operator actually tests is not straightforward, as bug #60836
discusses.  That is, input that produces identical output does not always
return true under this operator.

I don't fully grok how this operator works, so I can't speak with authority
about it.  But I think for the case outlined here, the operator _should_
consider the results identical.  This is an instance of merely representing
the same character (the no-break space) in different ways in the input; the
edge cases 60836 talks about have to do with equivalent cursor motions being
specified in different ways.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58962>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/