For what it's worth, we've managed to leave the collation alone in the database (that is, set to the default Western collation) with no problem.
----- Original Message ----- From: "Bill Conlon" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, July 11, 2005 11:41 AM Subject: Re: Witango-Talk: Support for Other Languages > Not much experience, but I have thought about it. > > Apache lets you specify the character set, which I believe is also > negotiable. Clearly you might have to modify the witango http header, > though. > > I think the bigger issues are associated with collating. How is > indexing and sorting to be handled in the db if its on a > language-specific basis? Maybe there needs to be separate DSNs for > english and Russian so you can collate accordingly. > > And the multi-byte languages are a bear. You probably have followed > the never ending swish-e discussion on the lack of UTF support. > > On Monday, July 11, 2005, at 11:18 AM, John McGowan wrote: > > > 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 > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
