[discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Enrique Castro
> Daniel Carrera wrote: >> I don't know how easy it is. The OOo API is not exactly straight >> forward. But even if it's not hard, it would make OOo a dependency. >> Would you want a command-line tool to have a 300MB dependency? (all this >> assuming that OOo doesn't require an X server if you prov

[discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Enrique Castro
Daniel Carrera wrote: > One of our members has been working on an XSLT transformation to turn > ODT files into HTML. It's already well advanced. So, if we can find a > tool that converts HTML to PDF, we could combine them. > > Do you know of any program to convert HTML to PDF? > HTMLDoc? It is

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Daniel Carrera
Enrique Castro wrote: What about the -headless mode? It still requires X. By invoking OOo from commandline with -headless will be possible to run a macro _without_ X being up and running? (but perhaps installed) It certainly has to be installed. And there's no good reason why a server shou

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Daniel Carrera
Enrique Castro wrote: HTMLDoc? It is included in several linux distributions Homepage is http://www.easysw.com/htmldoc/ There is a GPL license option Thanks. We've been discussing this on the ODF developers list. And although it would be easier to convert HTML->PDF, we decided it wouldn't be

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Henrik Sundberg
2006/1/15, Daniel Carrera <[EMAIL PROTECTED]>: > Enrique Castro wrote: > > What about the -headless mode? > > It still requires X. > > > By invoking OOo from commandline with -headless will be possible to run a > > macro _without_ X being up and running? (but perhaps installed) > > It certainly has

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Daniel Carrera
Henrik Sundberg wrote: Did Arend Beelen use dispatching or regular API calls? Look, you're missing the point: 1. Even when run headless, OOo needs X to install. Yes, even if you use API calls. This is an *installation* requirement. 2. Even when run headless, OOo needs X to run. Even if it doe

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-15 Thread Daniel Carrera
Daniel Carrera wrote: 1. Even when run headless, OOo needs X to install. Yes, even if you use API calls. This is an *installation* requirement. 2. Even when run headless, OOo needs X to run. Even if it doesn't actually display a GUI. 3. Even if the above changed, OOo alone is still a huge depen

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-21 Thread Mathias Bauer
Daniel Carrera wrote: > Henrik Sundberg wrote: >> Did Arend Beelen use dispatching or regular API calls? > > Look, you're missing the point: > > 1. Even when run headless, OOo needs X to install. Yes, even if you use > API calls. This is an *installation* requirement. > 2. Even when run headless

Re: [discuss] Re: commandline tool: render ODT into PS or PDF

2006-01-21 Thread Daniel Carrera
Mathias Bauer wrote: The dependency on an X-Server is indeed annoying and we hope that in a not so far future we can drop it at least for parts of the API (others then will refuse to work). But this is not an official goal that is worked on permanently, just something we keep in mind when we are