Fred:
Those 3 documents were written specifically based on my experience creating
multilingual sites for the Canadian Government (as well as a number of
triligual sites). You obviously brushed over it very quickly - there is no
automatic translation going on...the cultures are just used to identify
which xml file/database to pull the CUSTOM content from. Localization
doesn't mean automatic translation...localization is exactly what you are
doing...targetting for specific locales, your way just isn't very good.
2 - The application was poorly written...whether you wrote it or someone
else did, .NET is being used in a poor way.
3 - The examples are fully available in VB.NET. The difference between C#
and VB.NET is so minimal that all developers should be able to easily pick
up either language within hours.
Best of luck with your problem,
Karl
--
http://www.openmymind.net/ http://www.fuelindustries.com/
"Fred Flintstone" <id**********@nospam.comwrote in message
news:9g********************************@4ax.com...
Cool, I see what you're saying. There's only 2 problems:
- You can't use localization for Canadian French. French Canadians
will flip out completely if even one accent is off and they all agree
that the MS implementation of Canadian French is not entirely correct.
We have to use the text they send us or they lose it. I mean, flaming
four letter emails if one character is off. I do use localization but
only for date and time formats.
- I can't re-write the entire application to simply solve the ___o
problem.
- Those docs are all in C#, I'm in vb.
I'll repost the question.
Thanks anyways.
On Thu, 14 Sep 2006 14:17:00 -0400, "Karl Seguin [MVP]" <karl REMOVE @
REMOVE openmymind REMOVEMETOO . ANDME netwrote:
>>It's ironic that I happened to answer this question...
http://openmymind.net/index.aspx?documentId=3
http://openmymind.net/index.aspx?documentId=4
http://openmymind.net/index.aspx?documentId=52
Karl