What is the difference between the built-in NSIS Getparameters function and the custom GetParametersUnicode function used in many portable apps?
GetParametersUnicode.nsh says: "This function handles getting parameters when the EXE's path contains CJK characters".
The NSIS 2.40 changelog says: "Fixed GetParameters handling of MBCS characters"
So has GetParamtersUnicode any advantages or are they equal?
You are here
GetParameters vs. GetParametersUnicode
November 28, 2008 - 5:12am
#1
GetParameters vs. GetParametersUnicode
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
From now on, all launchers will be using the official GetParameters. We just used our own because the NSIS function was broken for so long and would completely fail if there were Chinese/Japanese/etc characters in the path. GetParametersUnicode is no longer needed.
Sometimes, the impossible can become possible, if you're awesome!
I'll use GetParameters too. (saves 1kb)
I wasn't sure if that problem is perhaps a GetParameters/GetParametersUnicode problem. Now I know it isn't. Thanks.