Did some reworking so there are almost no hard coded strings, this includes section titles, section descriptions, etc. (about 55) (about 3 left in some macros for errors downloading dictionaries and all the strings in the NSIS plugins). There are several defines that can be set (the current setup matches the previous NSIS 1 setup, but that will change soon) to enable/ disable all downloadable components, the list of dictionaries (which are added to the archive if NODOWNLOADS is set, otherwise downloaded during install), (for the future) optional inclusion of plugins, whether the installer executable portion is compressed with upx, whether a CRT DLL is included (or downloadable), and determining if the Modern UI should be used or current classic (note: multi language is only supported with the use of the Modern UI [not because NSIS doesn't support it, but because it already has all the NSIS specific stuff translated]).
The last step needed for the multi-language installer is to place the strings into another file (and hopefully eventually get them translated) and write a script that generates a NSIS specific file with all the strings (using the English as a fallback). For the time being (until I get around to some Makefile work) most of these settings will only work if you manually run a locally installed NSIS (plus the untgz plugin 1.0.3 or later). Jeremy CVS: ---------------------------------------------------------------------- CVS: Enter Log. Lines beginning with `CVS:' are removed automatically CVS: CVS: Committing in . CVS: CVS: Modified Files: CVS: Makefile AbiWord2.nsi CVS: ---------------------------------------------------------------------- string extraction to enable translations
