Am 21.08.2011 11:00, schrieb Vincent van Ravesteijn:
- I used the custom LaTeX installer page from my installer, only because
this is already translated to 22 languages. The page design is a matter of
taste, so we can also use yours if you prefer it for a certain reason.
This page doesn't fit in the framework of the installer and uses a deprecated
NSIS plug-in for the
GUI. We now have two different GUI codes in place, one using the modern
nsDialogs code and the old
code based on INI files.
If you don't mind I'll put back the nsDialogs version and we'll just transfer
the translations.
AFAICS this hasn't been done yet.
Uwe, are you still planning to revert to the nsDialogs version ?
For now not. This can be done any time later. Once this installer is ready for usage we will ask
people to translate it. Therefore the nsDialog strings are in the language files of the installer.
When we got them translated, we can switch.
Currently we have translations for 22 languages and thus should use them. For the nsDialog strings
we currently only have them for 3 languages.
Yea the detection of external programs became really messy now. We should merge
and clean this up.
What I don't like about this MiKTeX detection code is the lack of forward
compatibility (e.g.
MiKTeX 2.10 won't work) and the code duplication for each version.
What it wrong with the generic code that I used?
The problem with the generic code is that you expect every MiKTeX version to act the same. But this
was not the case in the past. Registry entries changed and even names of executables we need to
configure MikTeX. So we need to check each major release, e.g. the future MiKTeX 2.10 (which is
probably not released under this version number but as MiKTeX 3.0).
regards Uwe
