Uwe Sthr wrote:
Hello Paul,
I implement a solution that checks which program is associated to the
.pdf file extension. Could you please thest if this installer finds
Adobe Reader on your computer:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v15-2.exe
thanks in advance and
Paul A. Rubin wrote:
In the Software summary dialog, where
it lists the paths it will set as defaults, it runs the paths for
Acrobat and Python together. This appears to be just cosmetic (a missed
newline).
Thanks for the feedback.
After installation, acrord32 is listed as the viewer for
Uwe Stöhr wrote:
Hello Paul,
I implement a solution that checks which program is associated to the
.pdf file extension. Could you please thest if this installer finds
Adobe Reader on your computer:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v15-2.exe
thanks in advance and
Paul A. Rubin wrote:
In the "Software summary" dialog, where
it lists the paths it will set as defaults, it runs the paths for
Acrobat and Python together. This appears to be just cosmetic (a missed
newline).
Thanks for the feedback.
After installation, acrord32 is listed as the viewer
Uwe Stöhr wrote:
Hello LyXers,
again an update to the installer:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v14-2.exe
Angus Leeming wrote:
In other words, I think that the installer should lead the user
through the installation. It shouldn't just do it for him. That's
I wrote:
But we need also the entries
\viewer pdf2 acrobat
\viewer pdf3 acrobat
Simple fix attached, please apply.
I've a better solution. The entries should only be made if pdflatex and
dvipdfm does really exists. The attached patch works for me.
Angus, two questions about the configure
Uwe Sthr wrote:
I wrote:
But we need also the entries
\viewer pdf2 acrobat
\viewer pdf3 acrobat
Simple fix attached, please apply.
I've a better solution. The entries should only be made if pdflatex and
dvipdfm does really exists. The attached patch works for me.
This is overkill and
- I need the registry path for Acroread. If anybody has installed it,
please send it to me.
I started working on this. My thoughts was to extract the pdf viewer
associated with pdf's on the windows machine.
With:
Function getFileAssociation
Exch $R1
Uwe == Uwe Stöhr [EMAIL PROTECTED] writes:
Uwe - If Acrobat/Acrored if found by LyX's configure script the
Uwe following entry is made to lyxrc.defaults:
Uwe \viewer pdf acrobat
Isn't there a way in NSIS to check whether the pdf extension is
registered? There is no reason to force the user to
Jean-Marc Lasgouttes a écrit:
Isn't there a way in NSIS to check whether the pdf extension is
registered? There is no reason to force the user to use acrobat if he
prefers gsview or whatever.
Good idea. The actual version:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v15.exe
Angus Leeming wrote:
- I need the registry path for Acroread. If anybody has installed it,
please send it to me.
Under HKLM I have
Software\Adobe\Acrobat\Exe
which stores
C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe
so perhaps you can use the same test for both?
Don't know
Paul A. Rubin wrote:
Don't know if it makes a difference, but it might be safer to use
HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\7.0\InstallPath
Hello Paul,
I implement a solution that checks which program is associated to the
.pdf file extension. Could you please thest if this
Uwe Stöhr wrote:
Hello LyXers,
again an update to the installer:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v14-2.exe
Angus Leeming wrote:
In other words, I think that the installer should lead the user
through the installation. It shouldn't "just do it" for him. That's
I wrote:
But we need also the entries
\viewer pdf2 "acrobat"
\viewer pdf3 "acrobat"
Simple fix attached, please apply.
I've a better solution. The entries should only be made if pdflatex and
dvipdfm does really exists. The attached patch works for me.
Angus, two questions about the
Uwe Stöhr wrote:
I wrote:
But we need also the entries
\viewer pdf2 "acrobat"
\viewer pdf3 "acrobat"
Simple fix attached, please apply.
I've a better solution. The entries should only be made if pdflatex and
dvipdfm does really exists. The attached patch works for me.
This is overkill
>- I need the registry path for Acroread. If anybody has installed it,
please send it to me.
I started working on this. My thoughts was to extract the pdf viewer
associated with pdf's on the windows machine.
With:
Function getFileAssociation
Exch $R1
> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
Uwe> - If Acrobat/Acrored if found by LyX's configure script the
Uwe> following entry is made to lyxrc.defaults:
Uwe> \viewer pdf "acrobat"
Isn't there a way in NSIS to check whether the pdf extension is
registered? There is no reason to
Jean-Marc Lasgouttes a écrit:
Isn't there a way in NSIS to check whether the pdf extension is
registered? There is no reason to force the user to use acrobat if he
prefers gsview or whatever.
Good idea. The actual version:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v15.exe
Angus Leeming wrote:
- I need the registry path for Acroread. If anybody has installed it,
please send it to me.
Under HKLM I have
"Software\Adobe\Acrobat\Exe"
which stores
"C:\Program Files\Adobe\Acrobat 7.0\Reader\AcroRd32.exe"
so perhaps you can use the same test for both?
Don't
Paul A. Rubin wrote:
Don't know if it makes a difference, but it might be safer to use
HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\7.0\InstallPath
Hello Paul,
I implement a solution that checks which program is associated to the
.pdf file extension. Could you please thest if this
Hello LyXers,
again an update to the installer:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v14-2.exe
Angus Leeming wrote:
In other words, I think that the installer should lead the user
through the installation. It shouldn't just do it for him. That's
why I think a summary
Hello LyXers,
again an update to the installer:
http://fkurth.de/uwest/LyX/Installer/lyx_setup_136proposal-v14-2.exe
Angus Leeming wrote:
In other words, I think that the installer should lead the user
through the installation. It shouldn't "just do it" for him. That's
why I think a
22 matches
Mail list logo