On 1-8-2012 19:18, Martin wrote: > On 01/08/2012 17:41, Reinier Olislagers wrote: >> On 1-8-2012 15:42, Reinier Olislagers wrote: >>> Those lines appear to have been there since r6092 (svn blame)... perhaps >>> it's the fact I'm using Unicode Inno Setup or something I'm not seeing? >> I think it's using Inno Setup Unicode. >> from >> http://www.jrsoftware.org/ishelp/ > Possible. So far the installer are build with the ansi setup. Certain ;) Got the installer to run with unicode setup after some changes.
> Migrating to the unicode is on the list. > >> I'll try to fix the script, then run the installer, then install ANSI >> InnoSetup, do the same, and if it works, submit a patch. Unfortunately I don't think we can have 1 script for both ansi and unicode inno setup.... unless PascalScript supports ifdefs and there's a compiler define for the unicode and one for the ansi version. Assuming nobody is building on win9x, requiring unicode Inno (instead of ANSI Inno) shouldn't be a problem, I think. > Big step is to look at includes such as the Russian translation. If they > can move into the [language] section, then inno should deal with it.... Will have to have a look at what you mean... been a while since I used Inno. AFAIU from the docs, Inno Unicode can read UTF8 files without BOM (and more); currently the Russian translation seems to be encoded using some ANSI codepage (1251 by heart?). Meanwhile I have a working setup.exe but it seems to mix 2.6.0 and 2.6.1 directories below Lazarus (I'm using a 2.6.0 bootstrap and a 2.6.1 svn dir... don't know if that influences things). Going to stop now... back tomorrow to have another go. Regards, Reinier -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
