I have separated out
for all customised language-specific dialog text for the msi setup. There
should be no more hard-coded English in the setup dialogs. This opens the
door to localisation which I am assuming could add great value to the
package setup and make it far more professional?
Does anyone have any thoughts regarding this? Anyone oppose the idea, also
anyone want to help with localising files?
If I go ahead with this, I'd like to try just one additional localisation
first to keep it as simple as possible. For anyone considering putting
their hand up for testing a localisation, I'll need someone who is online
often and available via messenger for doing quick install tests and
The other affected files will be out
/packages/windows-WiX/BuildSubversion/pre.rtf and out
/packages/windows-WiX/BuildSubversion/post.rtf. Also, the readme that is
only included with the distributed binaries. I don't really think we'd have
to go crazy on the included licenses.
It's something that will need a little bit of thought because I will also
need to instruct the installer to retrieve a localised help chm (as well as
updating the build process to build localised chm's), so we'll have to see
how big the msi gets too. I'm assuming Subversion already automatically
picks the local language via share/locale?
The custom text for the installer is only very small - only a page or two of
text for each language, so I don't think it'd be a great deal of work to
maintain, and it wouldn't need much work from an individual to localise one
language. The only text that is likely to change is the readme distributed
with the win32 binaries. There are already volunteers doing the Subversion
Give me some feedback or tell me it could never work :).
Received on 2009-05-22 07:12:31 CEST