Hi Jay,
I think there is no problem in doing it the one way or the other.
Especially as I desire to change a lot in the XML based filter
framework. If you have the patience, take a look at the 45 min video of
the XML based filters presentation I held in Lyon (France) last Wednesday.
Here the list of all videos available:
http://ooocon-arnes.kiberpipa.org/media/index-talk-2006.html
PS: I have sent the presentation documents this morning, they might not
have added it, yet.
Regards,
Svante
Jay Sacco wrote:
Thanks for the reponse. When I have a possible submission ready I will
need to determine if my company is willing to donate the work to the Open
community. Assuming that goes well I'll look into the process below.
Here's a design question: rather than use standard named OO styles, I'm
currently defining my own styles in a .ott template to use with the import
filter, the idea being to isolate the filter from possible future OO style
changes that might impact the filter. Is this worthwhile or should I just
use the standard styles (preferable as this is less work for me)?
Regards,
Jay Sacco
Svante Schubert <[EMAIL PROTECTED]>
09/15/2006 10:58 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: [xml-dev] (replyTo: OOo and Docbook) -- How to bring changes of XML
based filter into the OpenOffice.org product by using tasks including test
documents for QA
Hi Jay!
I am the Co-lead of the XML project and I think I speak for the whole
OpenOffice.org community, when I say that it is a gorgeous idea of you
to contribute your work to the OpenOffice.org product.
We ARE still interested in the Docbook filter and I have to apologize
for the lack of documentation (e.g. on http://xml.openoffice.org/) that
shows you how to proceed, in case you want to bring your work into
OpenOffice.org. (Anybody who has some link is invited to correct me,
otherwise I try to correct the documentation in timely manner - for the
likely case that nobody helps me).
As a first step, it might be of great help for us that you let us know
what you have changed.
Basically we think it is a good idea to split the development from the
QA (quality assurance). Therefore I would suggest that you write
yourself some Issuezilla tasks - usually done for every enhancement you
made, but if you made everything already one for all do it as well.
Issuezilla might loook on the first gaze like overhead, on a second it
is not such bad, as the changes are being documented and we are able to
discuss changes.
If you explain what you have changed it would be great and most
important, attach simple sample documents to this issue(s) for the QA,
so they may see if your changes work as you thought they do.
We do not want to make it too complex, but the reason for this is, that
we want to check if your changes have not incidentally broken existing
functionality. If this happens, we usually talk of regression and you
have to adapt your work. No worry, such things might happen.
This regression can be seen if we compare a set of test documents with
the earlier version of the filter and your new one.
We have to test this visual (by opening in the office) and as well by
comparing the information in the XML (e.g. Metadata is usually not being
seen, but still exist in the document format).
The best way for doing this are automated tools:
I really want this visual compare tool (we internally call 'ConvWatch' -
from conversion) easily being used for the OOo XML filter community, but
my colleague is still working on the user interface.
For the automated regression test of the XML information set, we
currently have no tool. :/
That should be all for now. To summarize it:
We are very eager for your changes, and the correct way for you to bring
them into the product is to write issue(s) to yourself (with me
[EMAIL PROTECTED] on CC) and explain the problem you have fixed, while
adding test documents proofing your fix.
Any questions left for now?
If not, I am hoping to see some enhancement/issue from you and... even
if I repeat myself, we are delighted to have you in our XML filter
community. ;-)
Kind regards,
Svante
Jay Sacco wrote:
Hello everyone,
I've been spending some time upgrading sofftodocbookheadings.xsl and
docbooktosoffheadings.xsl to the current OOo XML format and modifying
them
to improve their functionality. I've got some reasonable functionality
at
this point and am wondering what the level of interest in this might be.
A
quick search for "docbook" in the archive shows that the last time
anyone
mentioned it was in early 2005. Have all the efforts to use OOo to edit
docbook files been terminated? If so, is this due to lack of time and
energy, or is there a technical reason, or has everyone found a better
GUI
editing tool for docbook files?
Regards,
Jay Sacco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
