Re: Installing Windows fonts

2005-06-15 Thread Uwe Stöhr
Johann Kellerman wrote: I know there are only a couple of translated languages. What I propose is create the other languages as nullsoft languages. For now the installer strings can be in english until a concerned user post the correct translations. The only string we can translate for now is th

Re: Installing Windows fonts

2005-06-15 Thread Uwe Stöhr
Angus Leeming wrote: Or, perhaps more simply: StrCpy $0 "$MiKTeXPath$\r$\n$GhostscriptPath$\r$\n$ImageMagickPath$\r$\n$PythonPath$\r$\n$PerlPath" ${StrNSISToIO} $0 $0 Thanks Angus. I implemented it in the actual version: (http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v15.exe

Re: Installing Windows fonts

2005-06-15 Thread Johann Kellerman
> StrCpy $0 >"$MiKTeXPath$\r$\n$GhostscriptPath$\r$\n$ImageMagickPath$\r$\n$PythonPa th$\r > $\n>$PerlPath" > ${StrNSISToIO} $0 $0 >Note that ${StrNSISToIO} is part of StrUtils.nsh... >You don't want to manipulate (change) $GhostscriptPath et al, >because you're actually going to use them l

Re: Installing Windows fonts

2005-06-15 Thread Angus Leeming
Johann Kellerman wrote: > So after constructing and writing out the complete path variable to > anther variable, the one that you send to Angus's plugin. You should > escape al the path names: > > Push $GhostscriptPath > Call Nsis2Io > Pop $GhostscriptPath > Push $INSTDIR > Call Nsis2Io > Pop $R0

Re: Installing Windows fonts

2005-06-15 Thread Johann Kellerman
> > Create one string that contains > > the lang environment variable and just makes sure that is translated for now. > > That solves the language step in one go. You select your installation language > > and your environment variable is set according to that. > > That is not possible as w

Re: Installing Windows fonts

2005-06-15 Thread Johann Kellerman
> > and the \t issue when you write to > > !insertmacro MUI_INSTALLOPTIONS_WRITE "ioSummary.ini" "Field 2" "Text" \ > >"$INSTDIR\bin \r\n$MiKTeXPath \r\n$GhostscriptPath > > \r\n$ImageMagickPath\r\n$PythonPath\r\n$PerlPath" > > you have to quote the paths. > > What do you mean

Re: Installing Windows fonts

2005-06-14 Thread Uwe Stöhr
Johann Kellerman schrieb: For the languages I have the following suggestion. Include all the available languages in Lyx as .nsh files in the installer. I excluded the language material from the main script to LyXUtils.nsh. This is now the language database and makes the main script more conci

Re: Installing Windows fonts

2005-06-14 Thread Uwe Stöhr
Johann Kellerman schrieb: Everything seems fine. The summary of the page is nice for novice users, but I would prefer a advanced button with a more detailed explanation. It just seems wrong if it says it found everything. I mean that the standard use doesn't want to be bothered with such spec

Re: Installing Windows fonts

2005-06-14 Thread Johann Kellerman
Hi Uwe, Everything seems fine. The summary of the page is nice for novice users, but I would prefer a advanced button with a more detailed explanation. It just seems wrong if it says it found everything... the people that know what everything is will want to know where it found it (msys/cygwin iss

Re: Installing Windows fonts

2005-06-14 Thread Uwe Stöhr
I wrote: (The source code is in the attached skript) I forgot it, sorry. Now attached. Uwe ; Lyx for Windows, NSIS v2 series installer script ; File LyXWinUtils.nsi ; This file is part of LyX, the document processor. ; http://www.lyx.org/ ; Licence details can be found in the file COPYING or

Re: Installing Windows fonts

2005-06-14 Thread Uwe Stöhr
Hello Angus, hello Johann, Angus Leeming wrote: Uwe, how does this strategy compare to yours? Johann Kellerman wrote: Attached is a nsi script to install/uninstall the required fonts. You can easily change between xft-fonts and bakoma. (one line in script) I need more lines as I let the u