I would like to help with this project. What I would like to do is  
build an "equivalent" css definitions page that would specify all the  
parameters for the different things. For example you specify a font  
face and font size for H1 - H6. My initial idea would be to create  
not a CSS parser, but a section that would allow me to duplicate the  
setting for a CSS file. That way when trying to get "equivalant"  
output from the browser to the Postscript one could specify similar  
style sheets that would eliminate the problems with different  
browsers rendering the content differently. I will have a try at it  
and submit it for your inspection. Unless there is a better approach  
which I am open to ideas.

Let me know what you think.

Terry R.

On Dec 28, 2005, at 11:21 AM, Tez wrote:

I think that what you propose is an excellent idea. At the moment I am
matching my elements appearance against the output from IE 6, which is
what I will continue to do. I do know that IE has a number of quirks
which I will not attempt to emulate, in which case I will "do the
sensible thing" which usually means aligning with Firefox, et al.

I am very happy to host whatever you come up on the project website.

FYI my roadmap at the moment is a follows:

Fix the implementation of <ul> and <ol> - trivial
- At the moment it is the <li> tags rather than <ul>/<ol> that cause
the indentation, which is not proper HTML behaviour.

Implement the passing of arguments into tag definitions - quite easy
- Using code similar to the options parsing mechanism in the Barcode
Writer encoders

Implement tables - Very difficult to do this correctly with rowspans
and colspans, etc.

Implement remaining HTML 4 elements - fairly simple, but long winded