On Tue, Feb 21, 2012 at 01:07:56PM -0800, Owen Leibman wrote: > The W3C recommends (see > http://www.w3.org/TR/html4/struct/dirlang.html#bidi88598) the use > of character set ISO-8859-8-I rather than ISO-8859. Although Lynx does > recognize ISO-8859-8 as a valid encoding, > it does not recognize the character set ISO-8859-8-I (nor ISO-8859-8-E), > and is treating the encoding as ISO-8859-8-1 if so specified. > This is true whether the character set is specified in a meta tag (using > either Content-type or Charset), > or in an http header. Test pages to demonstrate the problem are at: > http://www.dayenu.com/lieberman.iso88598i.htm (8859-8-i handled incorrectly) > http://www.dayenu.com/lieberman.iso88598.htm (8859-8 handled correctly) > > Although there is code to recognize the 2 encodings in LYCharSets.c, that > code seems ineffective > in recognizing the character set however the site specifies it. On the other > hand, it seems sufficient, in all cases, > to modify UCdomap.c to treat ISO-8859-8-I and ISO-8859-8-E as aliases of > ISO-8859-8. > A diff to accomplish this follows:
thanks -- Thomas E. Dickey <[email protected]> http://invisible-island.net ftp://invisible-island.net
signature.asc
Description: Digital signature
_______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
