On Sat, Jul 05, 2008 at 11:37:09AM -0400, Jim Park wrote:
> Logistically, even if I wanted to do it, with the time constraints I
> have, you will have to wait at least a year.  The amount of code
> change to get the Unicode support into NSIS by sheer number of lines
> is many more times than the amount of change the main NSIS went
> through over the whole of last year.  You are talking about reading
> through 80,000 lines of C code and making changes to make the Unicode
> version work, not to mention the conversion of NSH files and language
> files to Unicode versions which sometimes was not a straight change
> due to systems calls or file access.  But still it was simpler than
> any of the other options and I'm willing to bet that if I had to start
> all over again with a transparent Unicode / Win9x support as my goal,
> I would not have been able to finish it in the time I had.  But if
> someone leverages off what I've already done, maybe they can do it a
> bit faster?  I can imagine something quick and dirty like creating two
> exehead's for the installer that switches depending on the OS.  Even
> this change will take some time to do and no guarantee that the NSIS
> group will take it.  The scarier part of this change is that it will
> fork the code so much that I don't think I'll be able to maintain the
> code to be in sync with the main NSIS.  It would probably end up being
> a forked and frozen version.  (Frozen usually means abandoned in the
> open source world.)  So it really has to be done by the main NSIS guys
> with the committment that they will support it going forward.

I'm not highly skilled in either win32 or NSIS, so excuse me if I say
something stupid but;  how can an additional charset imply so much work?
NSIS supports a lot of charsets for different languages already.  It feeds
text with a given charset and tells the OS which charset is it.

Perhaps the problem is not about Unicode but about wide chars?  (in which
case, I wonder why they use utf-16 instead of utf-8).

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to