Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
Received-SPF: pass (nike.apache.org: domain of dgerard@gmail.com designates
 209.85.220.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAODHd3wDpoPCkXp-t6qcrDCaNTHav5Z28jBSKXtGFu4+PGdsHA@mail.gmail.com>
References: 
 <CAODHd3wDpoPCkXp-t6qcrDCaNTHav5Z28jBSKXtGFu4+PGdsHA@mail.gmail.com>
From: David Gerard <dgerard@gmail.com>
Date: Wed, 28 Aug 2013 10:30:29 +0100
Message-ID: 
 <CAJ0tu1He5x2zBv=w=TZ5ThruhaKDS43=V_hX3=XrVr076UGL_Q@mail.gmail.com>
Subject: Re: Regarding Rtf to PDF conversion using openoffice
To: dev@openoffice.apache.org
Content-Type: text/plain; charset=UTF-8

We actually do DOC to PDF conversion at my work. This involves running
the DOC through OOo 3.2 on the Ubuntu 10.04 server in question. (OOo
3.2 is the Ubuntu distro version, so actually Go-oo; we previously did
the same thing in OOo 3.1 on a Solaris server using Sun OOo.)

We wanted to go directly from RTF to PDF, but the RTF import filter in
any of OOo, AOO or LO was not up to the task of reading the broken RTF
generated by Apache FOP.

The way we do it is to shell out to soffice from a Perl CGI. This is
pretty heavyweight, but the conversion doesn't run very often.

(Apparently you can set up OOo and descendants to work as a daemon,
but we could never get that to work properly.)


- d.


On 28 August 2013 09:48, prajakta chalak <praj.chalak@gmail.com> wrote:
> Hi sir,
>    This is regarding rtf to PDF conversion using openoffice,which all dll's
> or assembly's are required.
>
>
> Thanks in anticipation
>
> Regards,
> Prajakta Chalak
> <9987551476>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org