Re: [Gnumed-devel] write document failure on windows

[Karsten Hilbert]

On Fri, May 13, 2011 at 10:39:38PM +0200, Karsten Hilbert wrote:

> > Good example. The path to AcroRd32.exe is different in almost any language.
> > 
> > One way to do this would be have the GNUmed installer look for it in the 
> > Windows registry and edit the gm-print_doc.bat during installation to put 
> > in 
> > the correct path.
> > 
> > But this will not be neccessary I think with GNUmed 0.9+1. So before 
> > putting 
> > this into the installer I will wait for GNUmed 0.9+1
> 
> Well, even then GNUmed will know the full path to

"will *need to* know", that is

Karsten

> AcroRd32.exe (no matter whether inside gm-print_doc.bat or
> inside the code) -- unless that path is in the PATH - under
> which circumstance it would automagically work with
> GNUmed-next.
> 
> Karsten
> -- 
> GPG key ID E4071346 @ gpg-keyserver.de
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
> 
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnumed-devel

-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346