Unicode support for all strings of install programm. It's
very dificult check special symbols (for example
German on Polish langs) when making multi-language
setup.
There are simple ways to get full Unicode (not UNICODE) support on
Win95/98/ME. Doing so will allow for a single binary that runs on all known
versions of Windows, with full access to features based on runtime
behavior. One main thing is to avoid #UNICODE, TCHAR, _T and the like.
I can assist with this, including info from Microsoft presentations circa
1998 in regards to how and why to do this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you referring to UNICOWS or something else? The problem
with UNICOWS is that it's huge. If I recall correctly, it's
about 300KB, which is almost 10 times the size of our
current stub. It is therefore out of the question.
We have some ideas about dynamically loading DialgoBoxW,
calling SetThreadLocale, etc. However, we didn't get to
implementing them yet. If you have another simple solution
which can be easily implemented, but will not bloat the
stub, I'm all ears. If you have a patch, even better.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd need unicode support in NSIS, so if anybody had some
time, I'd happily assist with the implementation. I refrain
from creating things on my own before discussing the
problem with the developer team, because I'd hate to break
things inadvertently. So, if anybody is in for adding
unicode support to NSIS, please contact me :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd need unicode support in NSIS, so if anybody had some
time, I'd happily assist with the implementation. I refrain
from creating things on my own before discussing the
problem with the developer team, because I'd hate to break
things inadvertently. So, if anybody is in for adding
unicode support to NSIS, please contact me :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oops, I didn't mean to post twice. Seems my internet
connection is a bit shaky today. I'm sorry. If possible,
please delete the duplicate post. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any news on this? I am looking ofr a solution to show Unicode text for Unicode-only languages on NSIS. I am not concerned about additional size, as the
installation packet is over 100 MB :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This was something important 2 years ago but now (end of 2008) I would expect to have only a Unicode build because it would be real hard to continue to maintain tons of codepage dependent strings and impossible to solve cross codepage issues!
Shortly: Unicode solves far more problems that it does creates.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Faq should mention:
- That there is currently no unicode support in NSIS. (v. 2.45)
- If, and when it will be added.
- That there is a unicode version of NSIS available at: http://www.scratchpaper.com/
- Which doesn't support older non unicode Windows versions. (Win95 etc.)
- And which creates slightly bigger installers (a few kb more).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=22848
There are simple ways to get full Unicode (not UNICODE) support on
Win95/98/ME. Doing so will allow for a single binary that runs on all known
versions of Windows, with full access to features based on runtime
behavior. One main thing is to avoid #UNICODE, TCHAR, _T and the like.
I can assist with this, including info from Microsoft presentations circa
1998 in regards to how and why to do this.
Logged In: YES
user_id=584402
Are you referring to UNICOWS or something else? The problem
with UNICOWS is that it's huge. If I recall correctly, it's
about 300KB, which is almost 10 times the size of our
current stub. It is therefore out of the question.
We have some ideas about dynamically loading DialgoBoxW,
calling SetThreadLocale, etc. However, we didn't get to
implementing them yet. If you have another simple solution
which can be easily implemented, but will not bloat the
stub, I'm all ears. If you have a patch, even better.
Logged In: YES
user_id=1472069
I'd need unicode support in NSIS, so if anybody had some
time, I'd happily assist with the implementation. I refrain
from creating things on my own before discussing the
problem with the developer team, because I'd hate to break
things inadvertently. So, if anybody is in for adding
unicode support to NSIS, please contact me :)
Logged In: YES
user_id=1472069
I'd need unicode support in NSIS, so if anybody had some
time, I'd happily assist with the implementation. I refrain
from creating things on my own before discussing the
problem with the developer team, because I'd hate to break
things inadvertently. So, if anybody is in for adding
unicode support to NSIS, please contact me :)
Logged In: YES
user_id=1472069
Oops, I didn't mean to post twice. Seems my internet
connection is a bit shaky today. I'm sorry. If possible,
please delete the duplicate post. Thanks!
Logged In: YES
user_id=1220105
Any news on this? I am looking ofr a solution to show Unicode text for Unicode-only languages on NSIS. I am not concerned about additional size, as the
installation packet is over 100 MB :)
Logged In: YES
user_id=584402
No.
Logged In: YES
user_id=584402
Originator: NO
RFE #1639728 adds request for unicode language files and scripts as well.
Logged In: YES
user_id=770226
Originator: NO
Today. Unicode support is becoming more important than Win9x compatibily or installer size.
Logged In: YES
user_id=584402
Originator: NO
A patch is now available by Jim Park.
https://sourceforge.net/tracker/?func=detail&atid=373087&aid=1795257&group_id=22049
Logged In: YES
user_id=770226
Originator: NO
I think that this patch should be integrated to the trunk ASAP.
Also it could be a good idea to start building NSIS in two flavors ;)
Logged In: NO
Yeah! We need Unicode!
Also requested with bug #2230926.
This was something important 2 years ago but now (end of 2008) I would expect to have only a Unicode build because it would be real hard to continue to maintain tons of codepage dependent strings and impossible to solve cross codepage issues!
Shortly: Unicode solves far more problems that it does creates.
The Faq should mention:
- That there is currently no unicode support in NSIS. (v. 2.45)
- If, and when it will be added.
- That there is a unicode version of NSIS available at: http://www.scratchpaper.com/
- Which doesn't support older non unicode Windows versions. (Win95 etc.)
- And which creates slightly bigger installers (a few kb more).
Please integrate NSIS Unicode changes to NSIS. I'm hopping this to happen for quite some time.
Need Unicode in standard NSIS: YES
Thinks Unicode support is far more important than Win9x support: YES
Done in latest CVS version, thanks.
Sir! We've got Unicode now! yay! \o/
Done in latest CVS version, thanks.