Steve N��ez wrote:
I note on the Axkit.org website that Axkit is claimed to support some 160 different output languages. Does anyone have any pointers or experience with using Axkit on a multi-language, Unicode site? I'm looking to write a database application that will need to handle 7 or so Asian languages and am investigating if Axkit is a viable option.I've used AxKit for multilingual sites, and in my experience it's worked marvellously well.
The only two problems I encountered were on the database side, and on the forms side. Some databases are rather braindead when it comes to encodings, so be careful to pick one that won't cause you trouble (properly built, Pg should be ok). The problem with forms is different: you can never be totally certain of the encoding a browser used to submit its data. Supposedly it's the one in which you sent the page containing the form to it, but sometimes it doesn't work out that well. Netscape 4 has many bugs in that area, as for IE it would seem that the way it reacts depends on whether Office is installed, and which version (one of them updates some internet component that modifies that behaviour.
None of those problems are AxKit-related however, and neither are solved by other publishing frameworks.
Once those problems were solved or ignored as being part of the general brokenness of browsers, all I did was keep the source data in UTF-8 as long as possible, and convert it only on output using AxKit's directives relating to transcoding.
--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
