On Fri, 30 Sep 2011, Lex Trotman wrote:
On 29 September 2011 22:03, Lex Trotman <[email protected]> wrote:
Hi Dag,
I did not finish the stylesheet-cleanup, but I did make the backend more
feature complete, adding footnote and reference support among others.
The stylesheets should be in another file included with the include1
macro with an attribute to control if they are embedded, like the html
css are. That will make odt11.conf much smaller and easier to
navigate and will make handling variations in styles easier.
I agree. I would like to use Github to list tasks as issues, structure
them and create milestones. This would be one of the tasks
There are a few issues that I don't know how to tackle at this point:
- Table support is constructed differently from HTML and I have no idea
how to make it do the necessary
I'll see if I get a chance tomorrow, ATM oasis website is down so I
can't get the standard.
If my github is good enough you should have a pull request for a
version that does basic table support and basic table header support.
Styles for these are needed, currently called tableblock and
tablehead. You seem to be able to define styles so I'll leave that
for you. :)
I will give you commit access ! For the styles, I would prefer if they
resemble the current HTML style as closely as possible, but to be honest,
that is not the most important task.
Proper naming for styles, on the other hand is something worth thinking
about before the first official release. We don't want to break styles
between releases. Also ODF understands the concept of classes, so we
should leverage that instead of using the named-styles only. Not sure if
it maps with CSS completely.
Havn't had time for anything else.
Any help is appreciated :) As soon as we can convert documents without
causing syntax errors we can announce it to a wider audience to get
feedback and tweaks. I plan to announce it on the LibreOffice mailinglist
as well.
I hope you can take ownership of the a2x integration and everything that
is related to what is needed outside of asciidoc, eg. zip files,
stylesheet merging, etc... I like to learn how this fits into the current
model.
Great work !
--
-- dag wieers, [email protected], http://dag.wieers.com/
-- dagit linux solutions, [email protected], http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
