If nobody minds a non-programming gripe, here goes:

I am an American living in Belgium (fr-BE, nl-BE).  Your kind of CultureInfo
interests me, since, really, there's no reason not to have (en-BE) or any
other combination...  From my point of view, I would like to see _words_ in
english, numbers using english formatting (1,234.5 = one thousand two
hundred thirty four point five) and maybe even dates in mm/dd/yy format
(belgian is dd/mm/yy).  Of course, all of this makes programming immensely
more difficult, but much more satisfying for me, the end-user.

Another distressingly common site is the following scenario on websites:

Please choose a language: []FR []NL []GB

This is commonly shown with the national flags of France, the Netherlands
and England.  I'm not sure since when you had to be from these countries to
speak the respective languages, but a certain flare rises in me when i have
to click 'GB' or sometimes 'UK' to view a website in my own language.  In
Belgium these choices are odd since 'BE' doesn't show up as a language
choice (and wouldn't have any sense anyway).

I say, get rid of the annoying 'country' selection and have something like:

Language: [] Français [] ('Dutch' in Dutch) [] English
(I don't know how to say 'Dutch' in Dutch)

That way, the choice of language is at least understood by the person who
would want to choose that language.  An old website I saw had:

Language: [] French [] Dutch [] English (current language = English)
or
Language: [] Français [] Neerlandais [] Anglais (current language = French)

which is even worse.

My $0.02 (or is it "My 0.02?", or worse "?0.02"? Oh, I give up!
Scott

Hello Altaf,

Thanks for the answer. I will typically be fetching texts in different
languages for a specific countries. For example, we need to send a mail to a
German user who chose English as preferred language. We can't just set the
culture to en-GB because that would fetch localized text for British users
which may contain information that is not relevant for German customers. But
if I set culture to en-DE, then I will access resources for Germany but
translated in English.

Vagif
 "S.M. Altaf [MVP]" <smaltaf@PLEASEDONTSPAMMEmsn.com> wrote in message
news:OygvZKB2FHA.3720@TK2MSFTNGP14.phx.gbl...
 Hi Vagif,

 If it's just your own routine doing the retrieving, then there shouldn't
be a problem.  You said that you won't be applying it to the thread either,
so there shouldn't be a problem at all.

 Can you elaborate... What mechanism will you be using then, for cases such
as en-DE?

 -Altaf

------------------------------------------------------------------------------
 All that glitters has a high refractive index.
 www.mendhak.com
   "Vagif Abilov" <vagif@online.no> wrote in message
news:uUYVW1V1FHA.2132@TK2MSFTNGP15.phx.gbl...
   Hello,

   I need to store culture-specific resources in my application that are
not
   limited by standard cultures recognized by .NET. For example, a German
   customer can specify his preferred language as English, and in such case
he
   will receive messages in English but still tailored for Germany. So I
really
   need to create a resource for en-DE (English language, Germany). I don't
   need to set this culture to application thread, this is just to retrieve
   specific message text. Is this right thing to do? Won't such custom
culture
   confuse some .NET localization routines?

   Thanks in advance

   Vagif Abilov