gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: LuisCapriles
Subject: Re: [Gnumed-devel] write document failure on windows
Date: Fri, 13 May 2011 06:59:00 -0700 (PDT)

I was having the same problem:  while trying to print, the gm-print_doc.bat
was missing...  So after researching the forum I came with this temporary
fix:

1)Make a gm-print_doc.bat that is in the your PATH.  In my case, I put the
file in C:\
2)The commans in the file are:

echo %1
"C:\Archivos de programa\Adobe\Reader 8.0\Reader\AcroRd32.exe" /T %2
exit 0

3)Here, 'Archivos de programa' is the spanish for 'Program files'.  Take
care of supply the actual path to AcroRd32.exe.  The /T switch prints the
file on the default printer and then closes Acrobat...
4)You need Acrobat Reader installed!!!
5)You need some TeX sw!!!  I installed MiKTeX after a suggestion of Karsten
Hilbert :)

This is working for me for menu Correspondence->Write Letter and selecting
LaTeX type...

BUT, I am getting letters in german!!!!  Is there a way to get the
translation??
Now, I am going to try OpenOffice type...

Hope this hep!!





Sebastian Hilbert wrote:
> 
> Am Donnerstag, 12. Mai 2011, 16:05:26 schrieb Karsten Hilbert:
>> > > pycommon.gmshellapi::detect_external_binary() #30): [which
>> > > gm-print_doc.bat] failed, exit code: 1
>> > 
>> > which command is of no use here
>> 
>> ...
>> 
>> > > pycommon.gmshellapi::run_command_in_shell() #99): shell command
>> > > 
>> > > >>>gm-print_doc.bat  generic_document
>> > 
>> >
>> c:\docume~1\newuse~1\locals~1\temp\gnumed\gm-r8tppv\gm-L-Template-fksvt1-
>> > in
>> > 
>> > > stance.pdf<<<
>> > 
>> > Guess this is os level shot in the dark ?
>> 
>> Sort of. The internal logic is:
>> 
>> - try a few detection methods, including "which-type" logic
>>    (which have been greatly improved in GNUmed-next)
>> - try calling the last method anyway, regardless of detection
>>    (which happens to be gm-print_doc.bat)
>> 
>> > > pycommon.gmprinting::print_file_by_shellscript() #51): print command
>> > 
>> > failed
>> > 
>> > no kidding.
>> 
>> Since - as you said - you don't ship any that's no wonder, is it ?
>> 
>> > Ok. All I see here is GNUmed trying to run the (non existant)
>> > gm-print_doc.bat
>> > 
>> > I thought there would be other means like Adobe reader and friends ?
>> Did
>> > I overlook this ?
>> 
>> You overlooked that the improved methods apply to GNUmed-next only.
>> 
>> People on 0.9 will need a gm-print_doc.bat in the PATH, or else.
>>
> 
> Ah, yes :-)
>  
> Hmm. need to ship some bat file in that case.
> 
> Sebastian
> 
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnumed-devel
> 
> 

-- 
View this message in context: 
http://old.nabble.com/-Gnumed-devel--write-document-failure-on-windows-tp31601493p31611687.html
Sent from the GnuMed - Dev mailing list archive at Nabble.com.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]