As I'm building The Phile site, I'm wondering how one would go about implementing it in two or three languages.

Does anyone have guidelines on the architecture of a multi-languages site?

Kim Gjerstad

__________________
Kim Gjerstad

There are A LOT of things to think about here. Look for "Localization" and "Culture" on MSDN. In general Microsoft suggests building a cultural neutral application with code and the default language and then use separate assemblies that contain only text strings. The resource manager class is used to load the strings and set the thread of execution for the culture which causes dates and currencies, etc to display in accordance to the culture. As I said, there a lots of issues: formatting for all different lengths of strings, currency conversion, etc. It goes on and on. It may be easier to create specific language versions of the site, share what you can (especially the data layer) and provide an initial login page where the user can select their culture and have it re-direct them to the proper set of pages. Good Luck.

I currently have two websites (ASP3), french and english, since their content really differ. They do share the same admin, etc. I was pretty much looking into getting rid of my date converter and just having a simple way of displaying european dates (dd/mm/yyyy). Note, my server is Eastern American Time, while I'm in equatorial Africa with NO daylight saving times. When somebody posts an article I want the dates to be modified to concur with our local time.

There are some stuff on the Internet which I haven't read yet on localization, but inhave yet to dwell myself in it.

Cheers,

Kim Gjerstad