Hi! First off, thanks for DISMTools — it's the most complete free/open-source alternative to NTLite I've come across.
I'd like to ask about internationalization (i18n). I took a look at the codebase and noticed that most UI strings in the main app are hard-coded in the .vb files, while there's a LanguageHelper under Utilities/LanguageUtilities/ that doesn't seem to be wired up yet. The installer already ships several languages via the .isl files, so multi-language support is clearly something you care about.
I'm asking because a few of us (Chinese-speaking users) would love to see a Chinese localization. But rather than just handing you a translation, we'd like to help with the i18n work itself, if you think it's the right direction.
A few questions:
- Do you have any plans or a rough timeline for i18n?
- If so, which approach do you have in mind (e.g. WinForms
Localizable, or wiring up the existing LanguageHelper)?
- Would you welcome a PR from us, or would you rather lead this yourself?
Happy to contribute in whatever way is most useful. Thanks again for the great tool!
Hi! First off, thanks for DISMTools — it's the most complete free/open-source alternative to NTLite I've come across.
I'd like to ask about internationalization (i18n). I took a look at the codebase and noticed that most UI strings in the main app are hard-coded in the
.vbfiles, while there's aLanguageHelperunderUtilities/LanguageUtilities/that doesn't seem to be wired up yet. The installer already ships several languages via the.islfiles, so multi-language support is clearly something you care about.I'm asking because a few of us (Chinese-speaking users) would love to see a Chinese localization. But rather than just handing you a translation, we'd like to help with the i18n work itself, if you think it's the right direction.
A few questions:
Localizable, or wiring up the existingLanguageHelper)?Happy to contribute in whatever way is most useful. Thanks again for the great tool!