Gabor Gombas <[EMAIL PROTECTED]> writes: > It seems that elinks cannot handle UTF-8 input/output properly. Symptoms > include links containing accented characters jumping some positions to > the left or becoming garbled when selected, or wrong cursor positioning > in input fields when I enter accented characters. Google's Hungarian > index page (http://www.google.co.hu) is a good example where all these > happen.
In ELinks 0.12.GIT configured with --enable-utf-8, <http://www.google.hu/intl/hu/> appears to render correctly. In ELinks 0.12.0, --enable-utf-8 will probably be the default. > From the symptoms I'd guess that elinks simply uses strlen() and ignores > the fact that the displayed length of strings is not the same as the > number of octets in them. ELinks 0.12.GIT has code for converting bytes to Unicode characters, and for counting the character cells that a character spans in a terminal. (However, it does not support combining characters, and no such feature is planned for 0.12.0.) Related upstream bugs at <http://bugzilla.elinks.cz/>: Bug 20 - UTF8 I/O can look absurd ;-) Bug 375 - utf-8 form content (textarea) gets screwed if not displayable Bug 822 - Should enable CONFIG_UTF8 by default (after it's safe) Bug 824 - Unicode combining characters support
pgp4RSoAmdCo4.pgp
Description: PGP signature
