Hi Marin,
I'd like to see VS.NET generate two identical RESX files for French and
English version of my application/form/usercontrol. Once done, I could
send RESX files to a professional transaltor... Hopefully, I'd like to
use VS.NET functionnalities.
I understand that I can do all this process manually but I still prefer
to use VS.NET to do that... I suppose that I don't catch something
about Localization in .NET... Also, I have to keep the property
Localization at True in order to use regional settings...
Best Regards,
Martin
[quoted text, click to view] Marin Millar wrote:
> Hi Martin,
> The behavior you are seeing is the result of setting the form property
> "Localizable" to True. Setting Localizable to True will generate the
> localized value in the default .resx file. It's possible to turn that off
> by setting Localizable to False, however, that turns off all localization
> functionality. You would then not be able to localize your other .resx
> files using the designer and would have to do all the work manually without
> any help from the designer.
> Hope this answers your question,
> Marin Millar [MSFT]
Hi Martin,
The behavior you are seeing is the result of setting the form property
"Localizable" to True. Setting Localizable to True will generate the
localized value in the default .resx file. It's possible to turn that off
by setting Localizable to False, however, that turns off all localization
functionality. You would then not be able to localize your other .resx
files using the designer and would have to do all the work manually without
any help from the designer.
Hope this answers your question,
Marin Millar [MSFT]
[quoted text, click to view] > I'd like to see VS.NET generate two identical RESX files for French and
> English version of my application/form/usercontrol.
....
> I understand that I can do all this process manually but I still prefer
> to use VS.NET to do that... I suppose that I don't catch something
> about Localization in .NET...
Just copy the English resx on top of the French one.
There is nothing to catch, I don't like the VS behavior either, but this is
how it is.
[quoted text, click to view] > Also, I have to keep the property
> Localization at True in order to use regional settings...
Correct.
--
Mihai Nita [Microsoft MVP, Windows - SDK]
http://www.mihai-nita.net ------------------------------------------