There are two issues here. >thees are ARMSCII-8 sites: > >http://www.parliament.am/ >http://www.aeb.am/ >http://acba.am/mainframe.php
The first is that these sites are sending a charset of "x-user-defined" (using the HTML meta tag) instead of "armscii-8" (or whatever the standard identifier for the charset is); if they sent the proper charset, the issue would go away. >There is no difference if I check "Automatically Detect Page Encoding" or >not. All this sites looks fine in Firefox (if I select right encoding from >menu), but not Camino. I discovered that there's not an autodetector for ARMSCII-8 (only a UTF-8 converter), so that explains why "Automatically Detect" makes no difference. The second issue is that Camino only shows a subset of possible page encodings in the Text Encoding submenu, leaving out many of the hundreds of esoteric encodings that Firefox exposes in its (much-maligned, even by its own developers) text encoding menu, so you can't manually select ARMSCII-8 in Camino. It might be possible for someone to write a JavaScript bookmarklet that you could simply click when you hit such sites that would change the charset tag on the page to ARMSCII-8 and force Gecko to re-render the page correctly. I don't forsee Camino adding the hundreds of esoteric encodings exposed by Firefox (or even several of them) to our text encoding menu, so unfortunately your best option is to lobby the sites to send the proper charset to begin with (or to switch to UTF-8), thereby avoiding all of these issues entirely in all modern browsers. Smokey -- Smokey Ardisson Co-Lead Triage/QA and Website & Documentation The Camino Project _______________________________________________ Camino mailing list [email protected] http://mozdev.org/mailman/listinfo/camino
