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
