i'm working with translators that just want to translate "web pages" and not
deal with resource files. i'd like to have a file structure that looks sort
of like this:

/ <- root directory where all .cs files live
/en-US/ <- english specific directory which contains aspx and ascx files
only
/jp-JP/ <- japaneses specific directory which contains aspx and ascx files
only

i'm having trouble getting Visual Studio to load the .aspx file if they are
not in the same directory as the .cs files.

is this possible? am i forced to use resource files for
internationalization?

thanks

[quoted text, click to view]
| i'm working with translators that just want to translate "web pages" and
not
| deal with resource files. i'd like to have a file structure that looks
sort
| of like this:
|
| / <- root directory where all .cs files live
| /en-US/ <- english specific directory which contains aspx and ascx files
| only
| /jp-JP/ <- japaneses specific directory which contains aspx and ascx files
| only
|
| i'm having trouble getting Visual Studio to load the .aspx file if they
are
| not in the same directory as the .cs files.
|
| is this possible? am i forced to use resource files for
| internationalization?

nevermind. this works fine, the problem is only Visual Studio itself.

[quoted text, click to view]

If you can, change the translators.

Not that they have to blindly take what you give them, but if they complain
so badly about something that is quite a standard format in the computer
world, chances are they are not technical enough to give you a good
translation anyway.

It is like you are trying to use a programmer that tells you "yes, I am
an expert in Windows programming, but I want notepad only, no Developer
Studio." or a graphic artist saying "yes, I can do what you ask, but I
cannot handle Photoshop files".

They may be ok, but I have some doubts.


--
Mihai Nita [Microsoft MVP, Windows - SDK]
------------------------------------------