You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(16) |
Jul
(26) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
|
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(17) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: panagiotis f. <wor...@ou...> - 2022-03-19 23:10:29
|
Hello, I would like to start reading the nsis code, but I do not know where to start. Could anyone provide me some pointers? I have looked the wiki, the dev-mail but nothing. How the code is organized. thank you, gio |
From: Fernando C. <fc...@gm...> - 2020-01-25 02:02:22
|
I was sadly astonished to read https://nsis.sourceforge.io/NSIS_False_Positives surely to blame to a series of "news articles" that started making the rounds two or three years ago: https://www.microsoft.com/security/blog/2017/03/15/ransomware-operators-are-hiding-malware-deeper-in-installer-packages/ https://www.mcafee.com/blogs/other-blogs/mcafee-labs/ransomware-families-use-nsis-installers-to-avoid-detection-analysis/ https://isc.sans.edu/forums/diary/Quick+analysis+of+malware+created+with+NSIS/23703/ It's been a while since I used NSIS. I used NSIS 2.x last time, I was very happy to find NSIS in active development and a v3.x out already. When I used, I remember using some third party quick GUI tool to create the NSIS script, I believe it was this: https://nsis.sourceforge.io/NSIS_Quick_Setup_Script_Generator but maybe it was this? https://sourceforge.net/projects/nsei/ Not sure. The last one shows "malware detected, download at your own risk". I wonder if it' s related to the "false positives" issue described in the URLs above, or if indeed NSEI includes some malware. In any case why would SourceForge leave a piece of malware available for download?? So, can anyone please point me to any qucik way to do an Installer with NSIS 3.x where I only want to 1. Display a logo/license 2. Copy a single exe to C:\program files\appname 3. Create a desktop shortcut and folder in the windows start button hierarchy Thanks in advance... FC -- ---- During times of Universal Deceit, telling the truth becomes a revolutionary act Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto Revolucionario - George Orwell |
From: Suresh J. <sj...@ge...> - 2016-10-24 15:45:19
|
Hello all, I am trying to use NullSoft to create setups for our product. Is it possible to create "Merge Modules" (MSM) using NullSoft? And is it possible to merge the MSMs into MSI setup using NullSoft? Thank you for your help, Suresh _______________________________ Suresh Jakka GeoCue Corporation 9668 Madison Blvd., Suite 202 Madison, AL 35758 (256) 461-8289 Telephone (256) 461-8249 Fax www.geocue.com<http://www.geocue.com> Integrating the Geospatial Workplace... |
From: Jon H. <squ...@gm...> - 2016-06-06 17:07:14
|
This is occurring on the Army Gold Master image for Windows 7, and thanks to your input, I've been able to track it down: * Force XP compatbility mode in the installers Properties->Compatbility * Rename the installer * Move the installer to C:\ * Use another user (preferably with only English letters in its name) * Try on a different Windows 7 computer Same result on all systems with this image. * Disable your AV * Run the version test suite on your -- https://github.com/kichik/nsis/blob/51e74df6c950cd8176ded182d09fc2553481f1ba/Source/Tests/winver.nsi Bingo - that got it. The issue is with McAfee Host Intrusion Prevention and McAfee VirusScan. Winver copies dll files to %TEMP% including a system.dll file. It then begins executing within a new folder in %TEMP%. McAfee configuration information is available here: https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/22000/PD22818/en_US/Access_Protection_Rules.pdf p. 6 starting with the section “Prevent all programs from running files from the Temp folder” And the STIG rule for the fully unclassified side is available at: https://www.stigviewer.com/stig/mcafee_virusscan_8.8_managed_client/2015-06-18/finding/V-59363 So, the moral of the story: NSIS version checking does not work on a DoD-STIG'd system using McAfee VirusScan or HIP. I'm cross-posting this on the texlive list so that their developers know that the issue has been tracked down, and it's an issue with the U.S. DoD + McAfee, not with NSIS. Thanks again, Jon On Mon, Jun 6, 2016 at 11:37 AM, Amir Szekely <ki...@gm...> wrote: > We use relative version comparison to avoid issues like the one you're > describing. There is no list where Windows 7 SP1 is missing. I have > developed this feature on Windows SP1 and have worked with it for the past 3 > years without seeing this issue. Yours is also the first report of such an > issue. I am therefore under the working assumption that this is a local > issue with your computer or that specific installer. > > Here is a list of a few things you can try to pinpoint the issue: > > * Force XP compatbility mode in the installers Properties->Compatbility > * Rename the installer > * Move the installer to C:\ > * Disable your AV > * Use another user (preferably with only English letters in its name) > * Try on a different Windows 7 computer > * Run the version test suite on your -- > https://github.com/kichik/nsis/blob/51e74df6c950cd8176ded182d09fc2553481f1ba/Source/Tests/winver.nsi > > On Mon, Jun 6, 2016 at 7:43 AM, Jon Hood <squ...@gm...> wrote: >> >> I can confirm that the installer is not being run in compatibility mode. >> >> C:\>ver >> Microsoft Windows [Version 6.1.7601] >> >> On Sat, Jun 4, 2016 at 4:10 PM, Amir Szekely <ki...@gm...> wrote: >> > Sounds like you're running your installer in Windows 2000 compatibility >> > mode. Right click the executable, go to the Compatibility tab and make >> > sure >> > everything is unchecked. >> > >> > On Fri, Jun 3, 2016 at 12:14 PM, Jon Hood <squ...@gm...> wrote: >> >> >> >> I had the following exchange with the texlive people who use nsis and >> >> downloaded the latest nsis subversion trunk. The Windows 7 Enterprise >> >> w/ SP 1 version appears to be missing from Include/WinVer.nsh: >> >> >> >> Mine: "Microsoft Windows NT 6.1.7601 Service Pack 1" >> >> >> >> Can you please make sure Windows 7 with Service Pack 1 (version >> >> 6.1.7601) is supported with nsis so that ${AtMostWin2000} evaluates >> >> that I'm using at least Windows XP? (line 72 of >> >> >> >> >> >> http://www.tug.org/svn/texlive/trunk/Master/tlpkg/libexec/install-tl.nsi?revision=33535&view=markup >> >> begins the block that I'm tripping up on). >> >> >> >> Additional reference for Windows 7 version: >> >> http://www.jrsoftware.org/ishelp/index.php?topic=winvernotes >> >> >> >> Thanks! >> >> Jon >> >> >> >> ---------- Forwarded message ---------- >> >> From: Siep Kroonenberg <si...@cy...> >> >> Date: Thu, Jun 2, 2016 at 9:05 AM >> >> Subject: Re: [tex-live] Unable to use install-tl-windows.exe: "Windows >> >> XP earliest supported version; aborting..." >> >> To: Jon Hood <squ...@gm...> >> >> Cc: tex...@tu... >> >> >> >> >> >> On Tue, May 31, 2016 at 02:06:52PM -0500, Jon Hood wrote: >> >> > When trying to run install-tl-windows.exe from >> >> > https://www.tug.org/texlive/acquire-netinstall.html I receive an >> >> > immediate pop-up stating, "Windows XP earliest supported version; >> >> > aborting..." >> >> > >> >> > My platform: Windows 7 Enterprise Service Pack 1 64-bit >> >> > >> >> > Current workaround: open install-tl-windows.exe in 7zip and extract >> >> > the install-tl-20160405 folder. Run install-tl-windows.bat from the >> >> > extracted folder >> >> > >> >> > Thanks, >> >> > Jon >> >> >> >> I cannot reproduce this with a freshly-downloaded >> >> install-tl-windows.exe on Windows 10 64-bit, and have no idea what >> >> may have caused this. >> >> >> >> -- >> >> Siep Kroonenberg >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> >> traffic >> >> patterns at an interface-level. Reveals which users, apps, and >> >> protocols >> >> are >> >> consuming the most bandwidth. Provides multi-vendor support for >> >> NetFlow, >> >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> >> planning reports. >> >> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e >> >> _______________________________________________ >> >> Nsis-devel mailing list >> >> Nsi...@li... >> >> https://lists.sourceforge.net/lists/listinfo/nsis-devel >> > >> > > > |
From: Amir S. <ki...@gm...> - 2016-06-06 16:37:49
|
We use relative version comparison to avoid issues like the one you're describing. There is no list where Windows 7 SP1 is missing. I have developed this feature on Windows SP1 and have worked with it for the past 3 years without seeing this issue. Yours is also the first report of such an issue. I am therefore under the working assumption that this is a local issue with your computer or that specific installer. Here is a list of a few things you can try to pinpoint the issue: * Force XP compatbility mode in the installers Properties->Compatbility * Rename the installer * Move the installer to C:\ * Disable your AV * Use another user (preferably with only English letters in its name) * Try on a different Windows 7 computer * Run the version test suite on your -- https://github.com/kichik/nsis/blob/51e74df6c950cd8176ded182d09fc2553481f1ba/Source/Tests/winver.nsi On Mon, Jun 6, 2016 at 7:43 AM, Jon Hood <squ...@gm...> wrote: > I can confirm that the installer is not being run in compatibility mode. > > C:\>ver > Microsoft Windows [Version 6.1.7601] > > On Sat, Jun 4, 2016 at 4:10 PM, Amir Szekely <ki...@gm...> wrote: > > Sounds like you're running your installer in Windows 2000 compatibility > > mode. Right click the executable, go to the Compatibility tab and make > sure > > everything is unchecked. > > > > On Fri, Jun 3, 2016 at 12:14 PM, Jon Hood <squ...@gm...> wrote: > >> > >> I had the following exchange with the texlive people who use nsis and > >> downloaded the latest nsis subversion trunk. The Windows 7 Enterprise > >> w/ SP 1 version appears to be missing from Include/WinVer.nsh: > >> > >> Mine: "Microsoft Windows NT 6.1.7601 Service Pack 1" > >> > >> Can you please make sure Windows 7 with Service Pack 1 (version > >> 6.1.7601) is supported with nsis so that ${AtMostWin2000} evaluates > >> that I'm using at least Windows XP? (line 72 of > >> > >> > http://www.tug.org/svn/texlive/trunk/Master/tlpkg/libexec/install-tl.nsi?revision=33535&view=markup > >> begins the block that I'm tripping up on). > >> > >> Additional reference for Windows 7 version: > >> http://www.jrsoftware.org/ishelp/index.php?topic=winvernotes > >> > >> Thanks! > >> Jon > >> > >> ---------- Forwarded message ---------- > >> From: Siep Kroonenberg <si...@cy...> > >> Date: Thu, Jun 2, 2016 at 9:05 AM > >> Subject: Re: [tex-live] Unable to use install-tl-windows.exe: "Windows > >> XP earliest supported version; aborting..." > >> To: Jon Hood <squ...@gm...> > >> Cc: tex...@tu... > >> > >> > >> On Tue, May 31, 2016 at 02:06:52PM -0500, Jon Hood wrote: > >> > When trying to run install-tl-windows.exe from > >> > https://www.tug.org/texlive/acquire-netinstall.html I receive an > >> > immediate pop-up stating, "Windows XP earliest supported version; > >> > aborting..." > >> > > >> > My platform: Windows 7 Enterprise Service Pack 1 64-bit > >> > > >> > Current workaround: open install-tl-windows.exe in 7zip and extract > >> > the install-tl-20160405 folder. Run install-tl-windows.bat from the > >> > extracted folder > >> > > >> > Thanks, > >> > Jon > >> > >> I cannot reproduce this with a freshly-downloaded > >> install-tl-windows.exe on Windows 10 64-bit, and have no idea what > >> may have caused this. > >> > >> -- > >> Siep Kroonenberg > >> > >> > >> > ------------------------------------------------------------------------------ > >> What NetFlow Analyzer can do for you? Monitors network bandwidth and > >> traffic > >> patterns at an interface-level. Reveals which users, apps, and protocols > >> are > >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, > >> J-Flow, sFlow and other flows. Make informed decisions using capacity > >> planning reports. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > >> _______________________________________________ > >> Nsis-devel mailing list > >> Nsi...@li... > >> https://lists.sourceforge.net/lists/listinfo/nsis-devel > > > > > |
From: Jon H. <squ...@gm...> - 2016-06-06 14:43:37
|
I can confirm that the installer is not being run in compatibility mode. C:\>ver Microsoft Windows [Version 6.1.7601] On Sat, Jun 4, 2016 at 4:10 PM, Amir Szekely <ki...@gm...> wrote: > Sounds like you're running your installer in Windows 2000 compatibility > mode. Right click the executable, go to the Compatibility tab and make sure > everything is unchecked. > > On Fri, Jun 3, 2016 at 12:14 PM, Jon Hood <squ...@gm...> wrote: >> >> I had the following exchange with the texlive people who use nsis and >> downloaded the latest nsis subversion trunk. The Windows 7 Enterprise >> w/ SP 1 version appears to be missing from Include/WinVer.nsh: >> >> Mine: "Microsoft Windows NT 6.1.7601 Service Pack 1" >> >> Can you please make sure Windows 7 with Service Pack 1 (version >> 6.1.7601) is supported with nsis so that ${AtMostWin2000} evaluates >> that I'm using at least Windows XP? (line 72 of >> >> http://www.tug.org/svn/texlive/trunk/Master/tlpkg/libexec/install-tl.nsi?revision=33535&view=markup >> begins the block that I'm tripping up on). >> >> Additional reference for Windows 7 version: >> http://www.jrsoftware.org/ishelp/index.php?topic=winvernotes >> >> Thanks! >> Jon >> >> ---------- Forwarded message ---------- >> From: Siep Kroonenberg <si...@cy...> >> Date: Thu, Jun 2, 2016 at 9:05 AM >> Subject: Re: [tex-live] Unable to use install-tl-windows.exe: "Windows >> XP earliest supported version; aborting..." >> To: Jon Hood <squ...@gm...> >> Cc: tex...@tu... >> >> >> On Tue, May 31, 2016 at 02:06:52PM -0500, Jon Hood wrote: >> > When trying to run install-tl-windows.exe from >> > https://www.tug.org/texlive/acquire-netinstall.html I receive an >> > immediate pop-up stating, "Windows XP earliest supported version; >> > aborting..." >> > >> > My platform: Windows 7 Enterprise Service Pack 1 64-bit >> > >> > Current workaround: open install-tl-windows.exe in 7zip and extract >> > the install-tl-20160405 folder. Run install-tl-windows.bat from the >> > extracted folder >> > >> > Thanks, >> > Jon >> >> I cannot reproduce this with a freshly-downloaded >> install-tl-windows.exe on Windows 10 64-bit, and have no idea what >> may have caused this. >> >> -- >> Siep Kroonenberg >> >> >> ------------------------------------------------------------------------------ >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e >> _______________________________________________ >> Nsis-devel mailing list >> Nsi...@li... >> https://lists.sourceforge.net/lists/listinfo/nsis-devel > > |
From: Amir S. <ki...@gm...> - 2016-06-04 21:10:12
|
Sounds like you're running your installer in Windows 2000 compatibility mode. Right click the executable, go to the Compatibility tab and make sure everything is unchecked. On Fri, Jun 3, 2016 at 12:14 PM, Jon Hood <squ...@gm...> wrote: > I had the following exchange with the texlive people who use nsis and > downloaded the latest nsis subversion trunk. The Windows 7 Enterprise > w/ SP 1 version appears to be missing from Include/WinVer.nsh: > > Mine: "Microsoft Windows NT 6.1.7601 Service Pack 1" > > Can you please make sure Windows 7 with Service Pack 1 (version > 6.1.7601) is supported with nsis so that ${AtMostWin2000} evaluates > that I'm using at least Windows XP? (line 72 of > > http://www.tug.org/svn/texlive/trunk/Master/tlpkg/libexec/install-tl.nsi?revision=33535&view=markup > begins the block that I'm tripping up on). > > Additional reference for Windows 7 version: > http://www.jrsoftware.org/ishelp/index.php?topic=winvernotes > > Thanks! > Jon > > ---------- Forwarded message ---------- > From: Siep Kroonenberg <si...@cy...> > Date: Thu, Jun 2, 2016 at 9:05 AM > Subject: Re: [tex-live] Unable to use install-tl-windows.exe: "Windows > XP earliest supported version; aborting..." > To: Jon Hood <squ...@gm...> > Cc: tex...@tu... > > > On Tue, May 31, 2016 at 02:06:52PM -0500, Jon Hood wrote: > > When trying to run install-tl-windows.exe from > > https://www.tug.org/texlive/acquire-netinstall.html I receive an > > immediate pop-up stating, "Windows XP earliest supported version; > > aborting..." > > > > My platform: Windows 7 Enterprise Service Pack 1 64-bit > > > > Current workaround: open install-tl-windows.exe in 7zip and extract > > the install-tl-20160405 folder. Run install-tl-windows.bat from the > > extracted folder > > > > Thanks, > > Jon > > I cannot reproduce this with a freshly-downloaded > install-tl-windows.exe on Windows 10 64-bit, and have no idea what > may have caused this. > > -- > Siep Kroonenberg > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
From: Jon H. <squ...@gm...> - 2016-06-03 19:15:06
|
I had the following exchange with the texlive people who use nsis and downloaded the latest nsis subversion trunk. The Windows 7 Enterprise w/ SP 1 version appears to be missing from Include/WinVer.nsh: Mine: "Microsoft Windows NT 6.1.7601 Service Pack 1" Can you please make sure Windows 7 with Service Pack 1 (version 6.1.7601) is supported with nsis so that ${AtMostWin2000} evaluates that I'm using at least Windows XP? (line 72 of http://www.tug.org/svn/texlive/trunk/Master/tlpkg/libexec/install-tl.nsi?revision=33535&view=markup begins the block that I'm tripping up on). Additional reference for Windows 7 version: http://www.jrsoftware.org/ishelp/index.php?topic=winvernotes Thanks! Jon ---------- Forwarded message ---------- From: Siep Kroonenberg <si...@cy...> Date: Thu, Jun 2, 2016 at 9:05 AM Subject: Re: [tex-live] Unable to use install-tl-windows.exe: "Windows XP earliest supported version; aborting..." To: Jon Hood <squ...@gm...> Cc: tex...@tu... On Tue, May 31, 2016 at 02:06:52PM -0500, Jon Hood wrote: > When trying to run install-tl-windows.exe from > https://www.tug.org/texlive/acquire-netinstall.html I receive an > immediate pop-up stating, "Windows XP earliest supported version; > aborting..." > > My platform: Windows 7 Enterprise Service Pack 1 64-bit > > Current workaround: open install-tl-windows.exe in 7zip and extract > the install-tl-20160405 folder. Run install-tl-windows.bat from the > extracted folder > > Thanks, > Jon I cannot reproduce this with a freshly-downloaded install-tl-windows.exe on Windows 10 64-bit, and have no idea what may have caused this. -- Siep Kroonenberg |
From: Amir S. <ki...@gm...> - 2012-12-19 07:42:24
|
You're right. The tracker is probably a better option than the forums. I used to go over the forum and add new stuff, but haven't in a while. I tried always including the original translator's opinion, manually verifying changes myself and keeping everyone in the loop with nsis-translations mailing list. But the process is problematic for all the reasons you have mentioned and translators do tend to disappear, even immediately after the initial submission. It's not usually their interest to stick around. They simply want to share their translation which was only for their installer. I always thought the ideal solution would be a website where people can upload and vote on translations. Each language can have multiple translations and we will only include the best one. New translations will have to get a certain number of votes before inclusion in the installer, but can still be downloaded. Maybe we can use something like http://translatewiki.net/ ...? On Wed, Dec 12, 2012 at 1:57 PM, Oleksandr Gavenko <gav...@gm...>wrote: > On 2012-12-12, Amir Szekely wrote: > > > Damn. I can't believe I left the database locked for so long. Sorry :( > > > > It's unlocked now and you can add those much needed piece of > > information on translation. > > > Thanks. I successfully register and update: > > http://nsis.sourceforge.net/Can_I_submit_/_correct_translations > > Most valuable thing - I add link to tracker as *first*, next to forum. > > I think that tracker is better way for holding pending for inclusion > translations then forum... > > Also I found a lot of translations awaiting for inclusion: > > * http://forums.winamp.com/showthread.php?t=347292 (Tatar translation) > * http://forums.winamp.com/showthread.php?t=344736 (Uyghur, China) > * http://forums.winamp.com/showthread.php?t=338620 (fixes for a Turkish) > * etc... > > Who responsible for integration of new translation? > > Who monitor "NSIS Translations forum" on regular basic (or there are mail > notification)? > > How about of asking to get mail from translators if they agree for future > reviews (In Russian and Ukrainian files - links to dead sites, some of > authors > I found at LinkedIn and other social sites, but still hard to contact to > original submitters)? > > How to trust to translation? Perform basic checks of free translation > services? > > -- > Best regards! > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
From: Anders <and...@us...> - 2012-12-16 04:54:27
|
"scons UNICODE=yes" does not mean you cannot generate ANSI installers but it does mean that makensis.exe is unicode and will not run on Win9x. Files in contrib\language should probably be utf8 but since the .nlf specifies the codepage, makensis should have enough information to convert the string from wchar_t back to the correct codepage when generating ANSI installers... |
From: Oleksandr G. <gav...@gm...> - 2012-12-14 17:16:32
|
On 2012-12-14, Amir Szekely wrote: > We want to remove the UNICODE=no option, so INSTALL probably needs to > be updated. The plan is to have makensis.exe always unicode capable, but > able to choose between ANSI and Unicode installers. That does mean "choose between ANSI and Unicode installers"? Does this mean only that .nsi input file to makensis interpreted as UNICODE or ANSI so this is effected: MessageBox MB_OK "Привет/გამარჯობა/नमस्ते" like commands? While current .nsh/.nlf files in UTF-8 this: Docs/src/usefulinfos.but:440: There are two macros that can help you write scripts that work for both Unicode and ANSI installers. To figure out if the script is being compiled to generate a Unicode installer, use !ifdef check for $\{NSIS_UNICODE\}. To see what the size of the default character is, use $\{NSIS_CHAR_SIZE\}. It will be 1 for ANSI and 2 for Unicode installers. say that internally all string converted to UCS-16-le (or UTF-16-le if full Unicode support provided). It is interesting to have two different coding system - one for source files another for variable values... I work of translation of Ukrainian.nsh (changes still has not been commited) and introduce use of French quotes - «». While cp1251 copdepage have appropriated codepoint I want to check that conversion of .nsh performed successfully (if they are performed at all for ANSI build...). -- Best regards! |
From: Anders <and...@us...> - 2012-12-14 17:05:27
|
> Ok. So what MSVC version used to build official NSIS 3.0 release? > > nsis-trunk/Docs/src/build.but suggest MSVC6 with February 2003 Platform SDK. I'm guessing it would still be MSVC6+PP+SP5 > Link to MSVC 6.0 service pack 5 is valid but refer to web.archive.org. I found > official link to SP6 (which also have smaller size due to stripping OS > patches): We use the processor pack and that does not work with SP6. > Link for SDK is broken. This article: > > http://en.wikipedia.org/wiki/Microsoft_Windows_SDK#Versions > > point to direct download links (from download.microsoft.com): > > http://social.msdn.microsoft.com/Forums/en/windowssdk/thread/e1147034-9b0b-4494-a5bc-6dfebb6b7eb1 > > Is that right tool-chain to build UNICODE NSIS? > > I come to software development in late 2005 in time when > > http://blogs.msdn.com/b/publicsector/archive/2005/12/07/501169.aspx > Visual Studio 6.0 removed from MSDN download on 12/16/2005 > > so I can't become legal user of MSVC 6... I fall into case of: > > http://en.wikipedia.org/wiki/Abandonware > > How about MSVC Express editions? Are they supported for release build or we > have some limitations to do this? I'm currently mostly using 2003Toolkit/Express but you have to search to find it since MS removed the official link. It is also a little tricky to setup and you need to use "scons MSTOOLKIT=yes" so it knows to search for a SDK. > What target OS list for NSIS? Makensis: Win2000+, Posix Generated installers: Win95+ >> When building with MinGW it links to msvcrt.dll and so you probably >> need Vista+ for Unicode file support. >> > So this means that I can't perform release build with MinGW as users of WinXP > may have some problems? This problem needs to be fixed before we release. >> The hack used when building with UNICODE=no will probably go away. >> > Does this mean that 'UNICODE=no' become unsupported build configuration for > trunk? Yes (So you need Win2000+ to run makensis, should be OK to require this in 2013) |
From: Oleksandr G. <gav...@gm...> - 2012-12-14 16:04:19
|
On 2012-12-14, Anders wrote: > When you build with UNICODE=yes the code that reads text files is in > the C run-time so what happens actually depends on the version of > Visual Studio and the Windows version. > Ok. So what MSVC version used to build official NSIS 3.0 release? nsis-trunk/Docs/src/build.but suggest MSVC6 with February 2003 Platform SDK. Link to MSVC 6.0 service pack 5 is valid but refer to web.archive.org. I found official link to SP6 (which also have smaller size due to stripping OS patches): http://www.microsoft.com/en-us/download/details.aspx?id=9183 Service Pack 6 for Visual Basic 6.0, Visual C++ 6.0 with Visual Source Safe 6.0d I think that appropriate text of 'build.but' may be updated... Link for SDK is broken. This article: http://en.wikipedia.org/wiki/Microsoft_Windows_SDK#Versions point to direct download links (from download.microsoft.com): http://social.msdn.microsoft.com/Forums/en/windowssdk/thread/e1147034-9b0b-4494-a5bc-6dfebb6b7eb1 Is that right tool-chain to build UNICODE NSIS? I come to software development in late 2005 in time when http://blogs.msdn.com/b/publicsector/archive/2005/12/07/501169.aspx Visual Studio 6.0 removed from MSDN download on 12/16/2005 so I can't become legal user of MSVC 6... I fall into case of: http://en.wikipedia.org/wiki/Abandonware How about MSVC Express editions? Are they supported for release build or we have some limitations to do this? What target OS list for NSIS? Are there exist Microsoft discount program with images of Windows OS for free or low cost to help independent developers? > When building with MinGW it links to msvcrt.dll and so you probably > need Vista+ for Unicode file support. > So this means that I can't perform release build with MinGW as users of WinXP may have some problems? > The hack used when building with UNICODE=no will probably go away. > Does this mean that 'UNICODE=no' become unsupported build configuration for trunk? > We need to fix the way we read text files before we can do a release... > I can help only with testing. -- Best regards! |
From: Anders <and...@us...> - 2012-12-13 23:29:25
|
Support for compiling with UNICODE=no will go away, we cannot maintain 4 versions of makensis (Ansi and Unicode on Windows and Posix) r6218 or something like that is probably a good spot if you wanted to use something post 2.46 to compile installers on Win9x... On Wed, Dec 12, 2012 at 10:07 PM, Oleksandr Gavenko <gav...@gm...> wrote: > Previously I successfully build with 'UNICODE=yes' (which is by default for > trunk). > > I try to build by: > > $ scons UNICODE=no > > and get error: > > g++ -o build\release\MakeLangId\MakeLangId.exe -static-libgcc -static-libstdc++ \ > -Wl,--file-alignment,512 -Wl,-Map,build\release\MakeLangId\MakeLangId.map \ > -mwindows -Wl,--file-alignment,512 -s -Wl,--subsystem,windows -Wl,-e_NSISWinMainNOCRT \ > build\release\MakeLangId\MakeLangId.o build\release\MakeLangId\resource-rc.o -lkernel32 -luser32 -lcomctl32 > > c:/opt/mingw/bin/../lib/gcc/mingw32/4.7.0/../../../libmingw32.a(main.o):main.c:(.text.startup+0xa7): undefined reference to `_WinMain@16' > collect2.exe: error: ld returned 1 exit status > scons: *** [build\release\MakeLangId\MakeLangId.exe] Error 1 > scons: building terminated because of errors. > > Seems that they come from '-Wl,--subsystem,windows' and '-mwindows' flags and > '-Wl,-e_NSISWinMainNOCRT' wasn't got in account. But for 'UNICODE=yes' scons > emit same command line call. Very strange... > > 'INSTALL' file written in so way that seems that 'UNICODE=no' is supported > configuration for trunk. Is that true? > > -- > Best regards! > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel |
From: Amir S. <ki...@gm...> - 2012-12-13 23:25:02
|
We want to remove the UNICODE=no option, so INSTALL probably needs to be updated. The plan is to have makensis.exe always unicode capable, but able to choose between ANSI and Unicode installers. On Wed, Dec 12, 2012 at 1:07 PM, Oleksandr Gavenko <gav...@gm...>wrote: > Previously I successfully build with 'UNICODE=yes' (which is by default for > trunk). > > I try to build by: > > $ scons UNICODE=no > > and get error: > > g++ -o build\release\MakeLangId\MakeLangId.exe -static-libgcc > -static-libstdc++ \ > -Wl,--file-alignment,512 > -Wl,-Map,build\release\MakeLangId\MakeLangId.map \ > -mwindows -Wl,--file-alignment,512 -s -Wl,--subsystem,windows > -Wl,-e_NSISWinMainNOCRT \ > build\release\MakeLangId\MakeLangId.o > build\release\MakeLangId\resource-rc.o -lkernel32 -luser32 -lcomctl32 > > > c:/opt/mingw/bin/../lib/gcc/mingw32/4.7.0/../../../libmingw32.a(main.o):main.c:(.text.startup+0xa7): > undefined reference to `_WinMain@16' > collect2.exe: error: ld returned 1 exit status > scons: *** [build\release\MakeLangId\MakeLangId.exe] Error 1 > scons: building terminated because of errors. > > Seems that they come from '-Wl,--subsystem,windows' and '-mwindows' flags > and > '-Wl,-e_NSISWinMainNOCRT' wasn't got in account. But for 'UNICODE=yes' > scons > emit same command line call. Very strange... > > 'INSTALL' file written in so way that seems that 'UNICODE=no' is supported > configuration for trunk. Is that true? > > -- > Best regards! > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
From: Anders <and...@us...> - 2012-12-13 23:20:00
|
When you build with UNICODE=yes the code that reads text files is in the C run-time so what happens actually depends on the version of Visual Studio and the Windows version. When building with MinGW it links to msvcrt.dll and so you probably need Vista+ for Unicode file support. The hack used when building with UNICODE=no will probably go away. We need to fix the way we read text files before we can do a release... |
From: Oleksandr G. <gav...@gm...> - 2012-12-12 21:57:15
|
On 2012-12-12, Amir Szekely wrote: > Damn. I can't believe I left the database locked for so long. Sorry :( > > It's unlocked now and you can add those much needed piece of > information on translation. > Thanks. I successfully register and update: http://nsis.sourceforge.net/Can_I_submit_/_correct_translations Most valuable thing - I add link to tracker as *first*, next to forum. I think that tracker is better way for holding pending for inclusion translations then forum... Also I found a lot of translations awaiting for inclusion: * http://forums.winamp.com/showthread.php?t=347292 (Tatar translation) * http://forums.winamp.com/showthread.php?t=344736 (Uyghur, China) * http://forums.winamp.com/showthread.php?t=338620 (fixes for a Turkish) * etc... Who responsible for integration of new translation? Who monitor "NSIS Translations forum" on regular basic (or there are mail notification)? How about of asking to get mail from translators if they agree for future reviews (In Russian and Ukrainian files - links to dead sites, some of authors I found at LinkedIn and other social sites, but still hard to contact to original submitters)? How to trust to translation? Perform basic checks of free translation services? -- Best regards! |
From: Oleksandr G. <gav...@gm...> - 2012-12-12 21:07:46
|
Previously I successfully build with 'UNICODE=yes' (which is by default for trunk). I try to build by: $ scons UNICODE=no and get error: g++ -o build\release\MakeLangId\MakeLangId.exe -static-libgcc -static-libstdc++ \ -Wl,--file-alignment,512 -Wl,-Map,build\release\MakeLangId\MakeLangId.map \ -mwindows -Wl,--file-alignment,512 -s -Wl,--subsystem,windows -Wl,-e_NSISWinMainNOCRT \ build\release\MakeLangId\MakeLangId.o build\release\MakeLangId\resource-rc.o -lkernel32 -luser32 -lcomctl32 c:/opt/mingw/bin/../lib/gcc/mingw32/4.7.0/../../../libmingw32.a(main.o):main.c:(.text.startup+0xa7): undefined reference to `_WinMain@16' collect2.exe: error: ld returned 1 exit status scons: *** [build\release\MakeLangId\MakeLangId.exe] Error 1 scons: building terminated because of errors. Seems that they come from '-Wl,--subsystem,windows' and '-mwindows' flags and '-Wl,-e_NSISWinMainNOCRT' wasn't got in account. But for 'UNICODE=yes' scons emit same command line call. Very strange... 'INSTALL' file written in so way that seems that 'UNICODE=no' is supported configuration for trunk. Is that true? -- Best regards! |
From: Amir S. <ki...@gm...> - 2012-12-12 20:47:16
|
Actually, it is a semi-colon in English.nsh. The problem is, again, the BOM. If I remove the BOM from English.nsh, I get to the next issue of CHM not building. Anders, care to chime in on this? On Wed, Dec 12, 2012 at 12:33 PM, Oleksandr Gavenko <gav...@gm...>wrote: > I try build complicate .nsi file (because it uses 'MUI_LANGUAGE'): > > cmd# cd c:\opt\nsis\Examples > cmd# ..\makensis makensis.nsi > ... > !insertmacro: MUI_PAGE_WELCOME > !insertmacro: end of MUI_PAGE_WELCOME > !insertmacro: MUI_PAGE_LICENSE > > and I get 100% CPU load. I break build by Ctrl-c: > > Aborting on Ctrl+C... > > I comment licence macro usage: > > ; !insertmacro MUI_PAGE_LICENSE "..\COPYING" > > ================================================================ > > Next i get error: > > ... > Error: Invalid language file. > Error in macro MUI_LANGUAGE on macroline 9 > Error in script "makensis.nsi" on line 99 -- aborting creation process > > MUI_LANGUAGE macro have line: > > LoadLanguageFile "${NSISDIR}\Contrib\Language files\${LANGUAGE}.nlf" > > and error come from 'Source/lang.cpp': > > // NSIS Language File parser > LanguageTable * CEXEBuild::LoadLangFile(TCHAR *filename) { > ... > #ifndef _UNICODE > char fencoding = 0; // 0 = ansi, 8 = utf-8 (16/17 for uft-16le/be not > supported) > if (IsUTF8BOM(f)) fencoding = 8; > #endif > > // Check header > TCHAR buf[NSIS_MAX_STRLEN]; > buf[0] = SkipComments(f); > _fgetts(buf+1, NSIS_MAX_STRLEN, f); > > if (_tcsncmp(buf, _T("NLF v"), 5)) { > ERROR_MSG(_T("Error: Invalid language file.\n")); > return 0; > } > ... > > I put: > > ERROR_MSG(buf); > > before "if-error" and get such output: > > i╗?# Header, don't edit > > I save it to file first 3 symbol is 0xef-bb-bf - UTF-8 BOM. > > As by default UNICODE=yes (from "scons -h") '_UNICODE' macro defined and > 'IsUTF8BOM' does not executed... > > I delete '#ifdef'. This '#ifdef' introduced by: > > r6196 | anders_k | 2011-12-06 01:44:26 +0200 (Tue, 06 Dec 2011) | 2 lines > > Basic UTF-8 support in ansi build so it can read UTF-8 .nlf files and > LangStrings > > Seems that 'IsUTF8BOM' call required in any case... Can anyone look to > this? > > ================================================================ > > Next error is: > > !insertmacro: MUI_LANGUAGE > Error: Label declaration not valid outside of function/section > !include: error in script: "C:\opt\NSIS\Contrib\Language > files\English.nsh" on line 1 > Error in macro LANGFILE_INCLUDE_WITHDEFAULT on macroline 12 > Error in macro MUI_LANGUAGE on macroline 12 > Error in script "makensis.nsi" on line 99 -- aborting creation process > > So from 'Contrib/Modern UI 2/Localization.nsh': > > !insertmacro LANGFILE_INCLUDE_WITHDEFAULT "${NSISDIR}\Contrib\Language > files\${LANGUAGE}.nsh" "${NSISDIR}\Contrib\Language files\English.nsh" > > call macro: > > !macro LANGFILE_INCLUDE_WITHDEFAULT FILENAME FILENAME_DEFAULT > > from 'Include/LangFile.nsh' where line 12 is: > > !include "${FILENAME}" > > First line of "English.nsh" is: > > ;Language: English (1033) > > so it really have ':' - label char! Can any help with this also? > > ================================================================ > > I stop, think enough for today )) > > -- > Best regards! > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel > |
From: Oleksandr G. <gav...@gm...> - 2012-12-12 20:33:46
|
I try build complicate .nsi file (because it uses 'MUI_LANGUAGE'): cmd# cd c:\opt\nsis\Examples cmd# ..\makensis makensis.nsi ... !insertmacro: MUI_PAGE_WELCOME !insertmacro: end of MUI_PAGE_WELCOME !insertmacro: MUI_PAGE_LICENSE and I get 100% CPU load. I break build by Ctrl-c: Aborting on Ctrl+C... I comment licence macro usage: ; !insertmacro MUI_PAGE_LICENSE "..\COPYING" ================================================================ Next i get error: ... Error: Invalid language file. Error in macro MUI_LANGUAGE on macroline 9 Error in script "makensis.nsi" on line 99 -- aborting creation process MUI_LANGUAGE macro have line: LoadLanguageFile "${NSISDIR}\Contrib\Language files\${LANGUAGE}.nlf" and error come from 'Source/lang.cpp': // NSIS Language File parser LanguageTable * CEXEBuild::LoadLangFile(TCHAR *filename) { ... #ifndef _UNICODE char fencoding = 0; // 0 = ansi, 8 = utf-8 (16/17 for uft-16le/be not supported) if (IsUTF8BOM(f)) fencoding = 8; #endif // Check header TCHAR buf[NSIS_MAX_STRLEN]; buf[0] = SkipComments(f); _fgetts(buf+1, NSIS_MAX_STRLEN, f); if (_tcsncmp(buf, _T("NLF v"), 5)) { ERROR_MSG(_T("Error: Invalid language file.\n")); return 0; } ... I put: ERROR_MSG(buf); before "if-error" and get such output: i╗?# Header, don't edit I save it to file first 3 symbol is 0xef-bb-bf - UTF-8 BOM. As by default UNICODE=yes (from "scons -h") '_UNICODE' macro defined and 'IsUTF8BOM' does not executed... I delete '#ifdef'. This '#ifdef' introduced by: r6196 | anders_k | 2011-12-06 01:44:26 +0200 (Tue, 06 Dec 2011) | 2 lines Basic UTF-8 support in ansi build so it can read UTF-8 .nlf files and LangStrings Seems that 'IsUTF8BOM' call required in any case... Can anyone look to this? ================================================================ Next error is: !insertmacro: MUI_LANGUAGE Error: Label declaration not valid outside of function/section !include: error in script: "C:\opt\NSIS\Contrib\Language files\English.nsh" on line 1 Error in macro LANGFILE_INCLUDE_WITHDEFAULT on macroline 12 Error in macro MUI_LANGUAGE on macroline 12 Error in script "makensis.nsi" on line 99 -- aborting creation process So from 'Contrib/Modern UI 2/Localization.nsh': !insertmacro LANGFILE_INCLUDE_WITHDEFAULT "${NSISDIR}\Contrib\Language files\${LANGUAGE}.nsh" "${NSISDIR}\Contrib\Language files\English.nsh" call macro: !macro LANGFILE_INCLUDE_WITHDEFAULT FILENAME FILENAME_DEFAULT from 'Include/LangFile.nsh' where line 12 is: !include "${FILENAME}" First line of "English.nsh" is: ;Language: English (1033) so it really have ':' - label char! Can any help with this also? ================================================================ I stop, think enough for today )) -- Best regards! |
From: Amir S. <ki...@gm...> - 2012-12-12 19:35:05
|
Fixed with r6287. On Wed, Dec 12, 2012 at 10:28 AM, Amir Szekely <ki...@gm...> wrote: > Build definitions are passed to the script so it can work with > different NSIS builds. > Look in SConstruct for nsis-defines.h that's written to build/urelease/config/. > > Now, as for the two different strings. They are necessary. > When that config is set to True, nothing happens when you position > your mouse over a component. > The only way to get a description for the component is to click it. > > I checked and there are only two language files where the text is > actually different. > This was OK before the language files were moved from Contrib\Modern > UI\Language Files to Contrib\Language Files. > The problem is with commits 5228 that added the new, defected, > language files and 5229 that remove the old ones. > The old MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO should be copied > back from the old files. > > On Wed, Dec 12, 2012 at 5:39 AM, Oleksandr Gavenko <gav...@gm...> wrote: >> During checking Ukrainian translation side by side with English.nsh I found >> this block of code: >> >> !ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE >> ${LangFileString} MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO "Position your mouse over a component to see its description." >> !else >> ${LangFileString} MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO "Position your mouse over a component to see its description." >> !endif >> >> I grep for 'NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE' keyword into project: >> >> $ ack-grep NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE >> >> Source/exehead/Ui.c >> 1225:#ifdef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE >> 1259:#ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE >> >> SCons/config.py >> 65: 'NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE', >> 460:AddBoolDefine('NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE') >> >> ... >> Contrib/Language files/English.nsh >> 48: !ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE >> ... >> *** 61 time repeated in other .nsh files *** >> ... >> >> I am not expert but have idea that build definition does not available when >> >> Contrib/Language files/*.nsh >> >> files processed. Is that true? >> >> "svn ann" shown first changes to this file by: >> >> r5228 | joostverburg | 2007-08-09 04:12:21 +0300 (Thu, 09 Aug 2007) | 3 lines >> >> New language files for localization of user interfaces and plug-ins. >> These files currently contain translations of the MUI and will be shared between different MUI versions. >> >> but I believe that this code introduced match early. >> >> In any case *then* and *else* leaves have duplicated text which all >> translators also translate by same text (totally 62 duplications, I have only >> brief look for text similarity and check only few cases literary). >> >> If anyone agree with me (that this condition is unnecessary) I remove it in >> all language files... >> >> -- >> Best regards! >> >> ------------------------------------------------------------------------------ >> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >> Remotely access PCs and mobile devices and provide instant support >> Improve your efficiency, and focus on delivering more value-add services >> Discover what IT Professionals Know. Rescue delivers >> http://p.sf.net/sfu/logmein_12329d2d >> _______________________________________________ >> Nsis-devel mailing list >> Nsi...@li... >> https://lists.sourceforge.net/lists/listinfo/nsis-devel |
From: Amir S. <ki...@gm...> - 2012-12-12 18:34:17
|
Damn. I can't believe I left the database locked for so long. Sorry :( It's unlocked now and you can add those much needed piece of information on translation. On Tue, Dec 11, 2012 at 2:22 PM, Oleksandr Gavenko <gav...@gm...> wrote: > Currently I work on fixing Russian and Ukrainian translations. > > And doesn't found formal reference what to do. > > Firstly I: > > $ grep -R translation nsis-trunk > > Docs/src/intro.but > Docs/src/history.but > > Next I discover: > > http://nsis.sourceforge.net/Can_I_submit_/_correct_translations > > This page have only 2 sentence and 2 links. > > One point to: > > http://forums.winamp.com/forumdisplay.php?f=159 > NSIS Translations > > I want to add some valuable points for translators that help them: > > * http://www.microsoft.com/Language/en-US/Default.aspx - computer dictionary > with thesaurus (from authoritative source, say no to crappy > translate.google.com!!) from English to every Windows supported > translation. > > * http://www.microsoft.com/Language/en-US/StyleGuides.aspx - Style Guides for > every Windows supported translation. > > I try to register at http://nsis.sourceforge.net/mediawiki/ to update page but > get error: > > The database is currently locked to new entries and other modifications, > probably for routine database maintenance, after which it will be back to > normal. > > The administrator who locked it offered this explanation: Upgrading to > MediaWiki 1.20.1 > > Is it possible to register to wiki? > > Is nsis wiki right place for info? May be better update docs in SVN and > publish it online? > > -- > Best regards! > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel |
From: Amir S. <ki...@gm...> - 2012-12-12 18:28:30
|
Build definitions are passed to the script so it can work with different NSIS builds. Look in SConstruct for nsis-defines.h that's written to build/urelease/config/. Now, as for the two different strings. They are necessary. When that config is set to True, nothing happens when you position your mouse over a component. The only way to get a description for the component is to click it. I checked and there are only two language files where the text is actually different. This was OK before the language files were moved from Contrib\Modern UI\Language Files to Contrib\Language Files. The problem is with commits 5228 that added the new, defected, language files and 5229 that remove the old ones. The old MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO should be copied back from the old files. On Wed, Dec 12, 2012 at 5:39 AM, Oleksandr Gavenko <gav...@gm...> wrote: > During checking Ukrainian translation side by side with English.nsh I found > this block of code: > > !ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE > ${LangFileString} MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO "Position your mouse over a component to see its description." > !else > ${LangFileString} MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO "Position your mouse over a component to see its description." > !endif > > I grep for 'NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE' keyword into project: > > $ ack-grep NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE > > Source/exehead/Ui.c > 1225:#ifdef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE > 1259:#ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE > > SCons/config.py > 65: 'NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE', > 460:AddBoolDefine('NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE') > > ... > Contrib/Language files/English.nsh > 48: !ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE > ... > *** 61 time repeated in other .nsh files *** > ... > > I am not expert but have idea that build definition does not available when > > Contrib/Language files/*.nsh > > files processed. Is that true? > > "svn ann" shown first changes to this file by: > > r5228 | joostverburg | 2007-08-09 04:12:21 +0300 (Thu, 09 Aug 2007) | 3 lines > > New language files for localization of user interfaces and plug-ins. > These files currently contain translations of the MUI and will be shared between different MUI versions. > > but I believe that this code introduced match early. > > In any case *then* and *else* leaves have duplicated text which all > translators also translate by same text (totally 62 duplications, I have only > brief look for text similarity and check only few cases literary). > > If anyone agree with me (that this condition is unnecessary) I remove it in > all language files... > > -- > Best regards! > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > Nsis-devel mailing list > Nsi...@li... > https://lists.sourceforge.net/lists/listinfo/nsis-devel |
From: Oleksandr G. <gav...@gm...> - 2012-12-12 13:39:12
|
During checking Ukrainian translation side by side with English.nsh I found this block of code: !ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE ${LangFileString} MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO "Position your mouse over a component to see its description." !else ${LangFileString} MUI_INNERTEXT_COMPONENTS_DESCRIPTION_INFO "Position your mouse over a component to see its description." !endif I grep for 'NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE' keyword into project: $ ack-grep NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE Source/exehead/Ui.c 1225:#ifdef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE 1259:#ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE SCons/config.py 65: 'NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE', 460:AddBoolDefine('NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE') ... Contrib/Language files/English.nsh 48: !ifndef NSIS_CONFIG_COMPONENTPAGE_ALTERNATIVE ... *** 61 time repeated in other .nsh files *** ... I am not expert but have idea that build definition does not available when Contrib/Language files/*.nsh files processed. Is that true? "svn ann" shown first changes to this file by: r5228 | joostverburg | 2007-08-09 04:12:21 +0300 (Thu, 09 Aug 2007) | 3 lines New language files for localization of user interfaces and plug-ins. These files currently contain translations of the MUI and will be shared between different MUI versions. but I believe that this code introduced match early. In any case *then* and *else* leaves have duplicated text which all translators also translate by same text (totally 62 duplications, I have only brief look for text similarity and check only few cases literary). If anyone agree with me (that this condition is unnecessary) I remove it in all language files... -- Best regards! |
From: Oleksandr G. <gav...@gm...> - 2012-12-11 22:22:24
|
Currently I work on fixing Russian and Ukrainian translations. And doesn't found formal reference what to do. Firstly I: $ grep -R translation nsis-trunk Docs/src/intro.but Docs/src/history.but Next I discover: http://nsis.sourceforge.net/Can_I_submit_/_correct_translations This page have only 2 sentence and 2 links. One point to: http://forums.winamp.com/forumdisplay.php?f=159 NSIS Translations I want to add some valuable points for translators that help them: * http://www.microsoft.com/Language/en-US/Default.aspx - computer dictionary with thesaurus (from authoritative source, say no to crappy translate.google.com!!) from English to every Windows supported translation. * http://www.microsoft.com/Language/en-US/StyleGuides.aspx - Style Guides for every Windows supported translation. I try to register at http://nsis.sourceforge.net/mediawiki/ to update page but get error: The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal. The administrator who locked it offered this explanation: Upgrading to MediaWiki 1.20.1 Is it possible to register to wiki? Is nsis wiki right place for info? May be better update docs in SVN and publish it online? -- Best regards! |