So the second set of tables are pictures showing how it should look, right? Is that page in esperanto??
Latin A displays characters everywhere, but most of them are wrong.
Latin B is mostly "?" and a few incorrect characters.
Yes, the second set (images) show how it should
look. (And yes, it's in Esperanto).
The Latin B characters are very exotic, and lack
of display there could be just a font issue. A
change of font might help. But a display of the
wrong character is always a big no-no.
I'm sorry. Maybe you could give the programmers
of iCab a hint...
OK. You say iCab can handle multiple languages without hassle. I hope you're right. Try the following URL with iCab, and then report. Did iCab display all of the characters in the tables of Latin Extended A and Latin Extended B? Were there characters that did not display or that were displayed in some surrogate form?
They should care since there are millions of people in America that use other languages than English, and since there are loads of characters in Unicode which are very handy in English, and which are not to be found in ASCII or Latin 1.
As usual not a single word about i18n. Of the
two browsers mentioned in the test (Neoplanet
is not a browser, it's just a skin) none has
any i18n support worth mentioning (if I'm wrong
about iCab, please correct me). Both big browsers
have excellent or at least half decent i18 support, and the up-coming Mozilla has brilliant i18n support.
i18n, and especially Unicode, is a must these days. Unicode is not a nice add-on or special effect, but the most basic of all features of any modern application that deals with text (the main feature of any browser). So non-Unicode, non-i18-n browers are just toys.
Why didn't they review Konqueror? I've never tested it (I use Windows - mostly because Linux is severly behind on the Unicode side), but they say it has Unicode support, so it's a serious candidate.
Slashdot Mirror
Yes, the second set (images) show how it should look. (And yes, it's in Esperanto).
The Latin B characters are very exotic, and lack of display there could be just a font issue. A change of font might help. But a display of the wrong character is always a big no-no.
I'm sorry. Maybe you could give the programmers of iCab a hint...
OK. You say iCab can handle multiple languages without hassle. I hope you're right. Try the following URL with iCab, and then report. Did iCab display all of the characters in the tables of Latin Extended A and Latin Extended B? Were there characters that did not display or that were displayed in some surrogate form?
-> Unicode tables
They should care since there are millions of people in America that use other languages than English, and since there are loads of characters in Unicode which are very handy in English, and which are not to be found in ASCII or Latin 1.
The UTF-8 encoding extends into the entire range of UCS, and that is a 32-bit space.
The UTF-16 encoding can through the use of surrogate pairs address more than a million characters, more than will probably ever be defined.
So don't worry!
As usual not a single word about i18n. Of the two browsers mentioned in the test (Neoplanet is not a browser, it's just a skin) none has any i18n support worth mentioning (if I'm wrong about iCab, please correct me). Both big browsers have excellent or at least half decent i18 support, and the up-coming Mozilla has brilliant i18n support.
i18n, and especially Unicode, is a must these days. Unicode is not a nice add-on or special effect, but the most basic of all features of any modern application that deals with text (the main feature of any browser). So non-Unicode, non-i18-n browers are just toys.
Why didn't they review Konqueror? I've never tested it (I use Windows - mostly because Linux is severly behind on the Unicode side), but they say it has Unicode support, so it's a serious candidate.