On 23/12/12 12:02 -0500, Odicha wrote:
> Hi.
> trytond can not open unoconv in a .
> In a linux box works fine. Command in report.py is:
>         cmd = ['unoconv', '--connection=%s' % CONFIG['unoconv'],
>             '-f', oext, '--stdout', path]
> 
> This code doesn't run on a windows box, because it needs python exe
> & path. (you must run unoconv with libreoffice python exe)
> It might be something like this:
>         cmd = ['c:/archivos de programa/libreoffice
> 3.6/program/python.exe', 'c:/archivos de programa/libreoffice
> 3.6/program/unoconv', '--connection=%s' % CONFIG['unoconv'],
>             '-f', oext, '--stdout', path]
> 
> I think the best approach for this is add some extra config value,
> something like LIBREOFFICE_PATH so it could be parsed if trytond is
> running on a win32 box. I'll open an issue, but I'd like to know
> what do you think before writing a patch.
> I could be something like:
>             if sys.platform == "win32":
>                 cmd= ['%s' % CONFIG['libreoffice_path.......

For me, it is windows who sucks and we should not hack Tryton for that.
A simple solution is to put a "unoconv" executable in the current
directory.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/

Attachment: pgpAt8YjQvlb5.pgp
Description: PGP signature

Reply via email to