openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Pescetti <>
Subject Re: html code generated from Open Office
Date Sat, 13 Oct 2018 20:24:52 GMT
Howard Cary Morris wrote:
> I want the HTML5 look identical to printed code. I will have additional references to
understand the code.

I see many mixed ideas in this conversations. Let me give you some 
pointers, and sorry for being late at this.

Start here:
The slides you find there will give you all pointers (source code 
modules, issues, patches, history) for the XHTML export filter and the 
idea to repurpose it as an HTML5 export filter. The presentation is old 
(and looks very old indeed!) but it's still accurate: we didn't change 
that export in recent years.

As someone already told you, we have two filters, the HTML one and the 
XHTML one. They are in different code modules.

The work has to be done in the source code, so whatever you have done in 
PHP and HTML (?) will have to be rewritten. But I (and many others) will 
be able to read your current work, assuming you are post-processing the 
HTML or XHTML output, and we can give feedback if you make it available 

There is a fundamental error in the idea of print fidelity: HTML, and 
especially HTML5, are not designed with print fidelity in mind. I mean, 
the idea to have the printed HTML5 identical to the OpenOffice (say) PDF 
export is unfeasible since HTML rendering is done by the user-agent 
(browser) and this is by design subject to what the browser decides to 
do. If you constrain the browser too much by enforcing specific CSS, all 
advantages of an HTML export will be gone. So the idea should be to have 
a proper HTML5 export as a start, ignoring the printed output for the 
time being. Priority should be on getting the semantic level (tags) 
right, and some basic CSS transformations to get the styles right. Our 
export is currently using bad HTML style, but the XHTML one is a bit 
better than the HTML one.

For print fidelity (but this comes much later) would be the place to start. It is 
wonderful, but support from tools is still quite incomplete. And anyway 
implementation will need the ground work above to be completed beforehand.

The way is long, but we are here to help, even though we are all 
volunteers and are often less responsive than we would like to.

The first step is building OpenOffice on your system. There is no other 
way, unfortunately. Does make 
any sense to you? If you are lost, we may be able to help if you 
describe your system configuration. Linux is probably the easiest 
platform for building.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message