Re: [Gnumed-devel] write documents

[Karsten Hilbert]

On Tue, Apr 19, 2011 at 02:45:45PM +0200, Hilbert, Sebastian wrote:

> > > 2. The gnumed has generated pdf document and is saved in temporary
> > > directory.
> > 
> > OK, good. I assume that PDF *does* contain the medication
> > list you expected ?
> > 
> 
> That means generating the document works.

No, it doesn't mean that. It means that *some sort of PDF*
was generated, not necessarily an exactly correct one.

> Now we need to handle that document.

The problem is rather in how to determine whether the PDF is
actually usable despite the fact the Windows is unable to
provide us with a reliable exit code from the pdflatex run.

I am ready to "just accept" what you assumed above as well -
namely that the PDF is just fine if it exists after the
pdflatex run - but I want vbanait to confirm that at least
by one-time visual inspection.

Then I'm prepared to simply ignore Windows' follies and take
a bet and go on assuming the PDF is fine.

> handling means printing, showing etc.
> 
> For Windows there is no such thing as gtklp which means no standard way to 
> bring up a print dialog.
>
> A few weeks back I did some research on that and found that basic 
> functionality can be achieved by some sort of batch file.
> 
> This means in most cases one needs to install Adobe reader since this is used 
> to handle the printing part.

That's documented in the gm-print_doc script file. Take
those hints and create a gm-print_doc.bat which GNUmed
automatically uses if it's in the path.

> The other option would be to write a program in python (e.g. python QT) and 
> make this a standalone exe binary which can be called to handle the printing 
> stuff.

There's always "PrintFile" for Windows.

> If anyone could do some research on how a small programm can be written in QT 
> (Nokia) that could handle printing on Windows it would be very helpful.
> 
> Until this has been written I could work on a batch file that would open the 
> generated pdf in Adobe reader.

See external-tools/gm-print_doc

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