People that have more extended experience with custom cultures may
correct me if needed, but on my previous project, we made a custom
culture for US Spanish (es-US) which for some reasons is not supported
natively by .NET. It worked without a hitch. I really fail to see how
it can be more messy tha
On Nov 30, 2007 10:06 AM, Mark Nicholls <[EMAIL PROTECTED]> wrote:
> My 'bodge' is to highjack another locale and use it for a specific client,
> so the config contains some specific locale string 'en-xx'...which then
> localises the app to that client.what I don't like about it is that
> you n
The problem is it seems to be a vista thing.I'm generally working
against XP.
===
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
Thanks I'll take a look.
===
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
On Thu, 29 Nov 2007 13:23:23 -0500, Peter Ritchie
<[EMAIL PROTECTED]> wrote:
>On Mon, 26 Nov 2007 06:15:34 -0500, Mark Nicholls
><[EMAIL PROTECTED]> wrote:
>>What do you mean by "keeping the text in the resources"?
>>How would you go about wrapping Properties.Resources class?
>
>In the Solution E
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.
On Mon, 26 Nov 2007 06:15:34 -0500, Mark Nicholls
<[EMAIL PROTECTED]> wrote:
>What do you mean by "keeping the text in the resources"?
>How would you go about wrapping Properties.Resources class?
In the Solution Explorer, Properties\Resources.resx lets you have any
number of application-wide reso
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 possibl
On Wed, 21 Nov 2007 10:27:48 -0500, Peter Ritchie
<[EMAIL PROTECTED]> wrote:
>Yes, the built-in multilingual support in WinForms is dependant on culture
>names (like "en-US"). If you wanted to use the built-in functionality
>you'd have to create and install your own locales.
sounds unpleasant.
Yes, the built-in multilingual support in WinForms is dependant on culture
names (like "en-US"). If you wanted to use the built-in functionality
you'd have to create and install your own locales.
I've seen people use dictionaries, as Paul mentioned. I've also seen
people use database lookups, wr
PROTECTED]> Subject:
> [ADVANCED-DOTNET] Multiple UI versionsbut not quite multilingual> To:
> ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> > I've got an application that I want to
> install for multiple clientsall> use English as the principle language
> but each
I've got an application that I want to install for multiple clientsall
use English as the principle language but each client has (different)
specific terms for specific domain specific things...
e.g. what is ones clients 'IS department' is 'Technology' for another
client.
so the functionality
12 matches
Mail list logo
