If you're talking about displaying non-western characters from a database then we've done a lot of that. We tried to get Unicode to work and never did, so we store the text data in the database in the code-page required by the end language and have coded our application to change the code page META tag based on what language you're trying to display. As long as you change the encoderesults .ini setting (to false) we haven't had any trouble. Customer's can type data into the system through HTML forms without problem (we're doing Chinese and Korean and now moving into Polish and Eastern Europe, plus all the western European languages).
We're using MS-SQL and what we do is save the source text (usually sent to us in Excel) as Unicode (UTF-16) and then use an application to convert from Unicode into the correct code page (try http://www.crystalsoftware.com.au/textpipe/pro.html). We then can import or copy/paste that text data into the database or copy and paste it into WiTango actions. WiTango queries work as normal and as long as the HTML meta tag uses the correct code page then the resulting text comes out OK on the screen. Dave Machin BenchmarkPortal ----- Original Message ----- From: "John McGowan" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, July 11, 2005 11:18 AM Subject: Re: Witango-Talk: Support for Other Languages > Thanks for the reply Bill. Those issues are obviously something to > think about. > > What about the basic handling of characters that aren't in the latin > character set. Have any experience with that? > > /John > > Bill Conlon wrote: > > > Take a look at the apache manual section on content negotiation. > > Language is one negotiable element, and you can pull that from the > > header to manage this. > > > > But I think there are some potential problems within Witango, date > > formatting for example. I believe the language used by Witango is > > taken from the environment or the witango user, rather than from the > > header. So if your witango runs with 'lang=en-us', you'll always get > > 'July', instead of 'Juli' for German. > > > > About 4 months ago I posted a feature request related to this. > > > > > > On Monday, July 11, 2005, at 06:48 AM, John McGowan wrote: > > > >> We have a content management system that uses Witango and > >> MSSQL/MySQL All sites using it have been english sites, but one of > >> our clients wants to run a Russian site. I am not familiar with > >> what is required to make something like this work. I am going to > >> investigate what will need to be done to our applicaiton to support > >> different languages. I'm not talking about making the CMS support > >> bilingual sites, here, just the ability to support the editing and > >> hosting of a site with a different character set. > >> > >> > >> > >> > >> > >> > >> _______________________________________________________________________ > >> _ > >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >> > > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
