Re: obscure new display features

[Dave Love]

Juri Linkov <address@hidden> writes:

> I agree.  ^L fontified as a keyword looks horrible.  That's why I suggested
> to change its color to "dark red" to look more like comments.

The point isn't the specific colour, but the fact that there is
mysterious highlighting at all.

>> I've no idea why non-breaking characters should be displayed like
>> this, but U+00AD isn't one -- it's SOFT HYPHEN.  If you're going to
>> change its display, the issue (see Unicode) is whether or not it
>> should be displayed at all -- not that I think it should be
>> invisible.
>
> I guess it should be visible at the end of the line.

Well Unicode says that guess is wrong...

>> NON-BREAKING HYPHEN is U+2011.
>
> Yes, this should be added too.

If you want to highlight non-breaking characters for some mysterious
reason, you don't _add_ it, you use it instead of soft hyphen.  (For
what it's worth, the other no-break characters are U+0F0C, U+2007,
U+2060, U202F and U+FEFF, but why does anyone care?)

> I don't know what is the cleanest way to check it in all charsets,
> perhaps the following code will work:

??  You'd have to check the tables which define the charsets.

> (eq (aref (get 'utf-translation-table-for-encode 'translation-table) ? ) 
> ?\x8a0)
> (eq (aref (get 'utf-translation-table-for-encode 'translation-table) ?­) 
> ?\x8ad)