On 2014-05-18 22:18, Thorsten Glaser wrote:
> >I noticed that lynx doesn't seem to make certain semi-obvious
> >transformations from fancy Unicode characters down to standard
> >ascii characters. For an example, check out my tweet on this page
> >in both
>
> I require Lynx to not do this, because I use Unicode excessively.
>
> On the other hand, selecting a nōn-UTF8 charset might want to do
> that… but the tables are apparently hand-generated and do not cover
> full Unicode, only the obvious stuff related to most legacy
> charsets. Covering all of Unicode is going to be a crazy job anyway…
I agree that, if the containing terminal supports it, lynx should
just present the character as-is. I don't know if there's an easy
way to detect whether a terminal supports smarter encodings like
UTF-{8,16,32} where it can/should present the characters as-is, but on
dumber terminals, fall back to a character-remapping.
-tkc
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
