In .NET 2.0, you can create your own culture, optionally based on others. Take a look at CultureAndRegionInfoBuilder class in sysglobl.dll (in the GAC). You may also want to take a look at http://msdn2.microsoft.com/en-us/library/ms404375.aspx to know how to save cultures without admin privileges. There was a tool "Microsoft Locale Builder", but I cannot find it anymore ?!
Sébastien On 11/29/07, Mark Nicholls <[EMAIL PROTECTED]> wrote: > On Mon, 26 Nov 2007 06:15:34 -0500, Mark Nicholls > <[EMAIL PROTECTED]> wrote: > > on actually getting a chance to look at this, I must admit that the dotnet > multilingual stuff is pretty nicely implemented. > > So I am sorely tempted to do something truly dreadful in order to keep > this as simple as possible...i.e. make each installation use a specific > language e.g. English (Zimbabwe). > > It is irratating that the multilingual support is as closed as it > is....i.e. my application are UK based, but in two different companies who > have slightly different business terms for the same, but I don't > especially want to have to recreate the localisation functionality of > dotnet. > > Is there a way to do this without fudging the culture....how nightmarish > is it to create a "en-a1" and "en-a2" culture? > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com > -- Sébastien www.sebastienlorion.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
