pengyou
2nd July 2003 23:50 UTC

Is it OK to mix old and new NLF files ?
Are some NLF files no longer "safe" to use?

I've noticed that the *.nlf files in the "{NSIS}\Contrib\Language files" folder have various NLF version numbers (NLF v2, NLF v3, NLF v4, and NLF v5). It seems the older versions have some strings missing. Is it "safe" to build an installer using languages which happen to have differing NLF version numbers, or is it best to ensure that all of the files used have the same version number (eg only use files which have "NLF v5" at the start)?

I'm not complaining that some files are out of date, I am just wondering if it is safe to use different versions of these files in my installer.

Brian

kichik
4th July 2003 13:45 UTC

Aside from the LicenseForceSelection strings all strings, if missing from the NLF, are taken from the English NLF or the default English table (same as NLF). I don't seem to find any reason for the LicenseForceSelection strings to behave this way so I have made them use English too. It is safe to use them, but some English strings may appear if the user chooses that language.

All NLFs that have older headers and missing strings are NLFs that the authors have not updated.

pengyou
4th July 2003 18:22 UTC

Thanks for explaining how NSIS uses the NLF language files. I should have realised that NSIS would be clever enough to cope with out of date NLF files!

When I started to add other languages to my installer, I was amazed at the wide range available for NSIS - now I know I can use as many as I want and the worst that can happen is that some messages will be in English.

Brian