|
It is possible add localization support to
one install database, I’m just not sure if that’s what we should
do. I would personally like to see
different databases and error templates for each language. That way dialogs/errors/action text would
not look weird if the display of a certain language exceeds the display of
another, since you could define specific width/height properties for each control
in the localized database. The
downside to this is that updates to each install database would become repetitive
and tedious. I would like to leave
this open to debate though… Also, relevant MSDN links are below: Steps for how to localize: http://msdn.microsoft.com/library/default.asp?url=""> A localization example: http://msdn.microsoft.com/library/default.asp?url=""> Jim From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David I will need to create a German setup program at some point
in the future. So I will have to translate everything anyways and would like to
somehow contribute that back to the public… Can’t promise when
though ;) But we could start thinking on how to do that now already,
right? I guess I could just create a new msi template file, so that there will
be different templates for different languages. But that doesn’t look
really great to me… Ideally I would like to have one msi file in the end
that can display its UI in different languages, depending on the platform it is
executed on. Is that something for a transform?!? If anybody could point
me in the right direction how to do it in a way that I can integrate it into
NAntContrib, it would be very cool. Thanks David |
