Hi,
After the resource has been compiled to .resource file or resource
assembly, they'll not be changable without recompile/generate the
resource.
.... which shouldn't be much of a problem as .Net should detect the change
in the files' date and recompile them on-the-fly. At least that's what I'd
think.
Therefore, for those application which will localize the data/content
that is database driven, it is better to use database based localization
solution. Do you think so?
The background is really only the problem to hand over i.e. a base-language
to translators thus enabling them to do their work. Until now I have done
my ext-app approach for translators only with win-forms applications.
With ASP.Net (running on the web as opposed to IntraNet-Apps) I'm rather
thinking about a page (or set of pages) to let them do that right in the
application itself.
However, this also has its weaknesses in distributed scenarios, i.e. with
one web-app deployed to different/independently running websites.
I think that there should really be some built-in way of dealing with this
problem, i.e. an object that can handle a set of .resx-files. Years back,
you were doing this kind of thing with simple (unicode-) text-files ...
Alternatively, I could be learning more languages and do it myself! ;-)
Gruß,
Olaf