Hi Nicolas,
Nicolas Boulenguez píše v St 30. 01. 2013 v 19:56 +0100:
In class sw/source/filter/ww8/docxattributeoutput.hxx or its parent
sw/source/filter/ww8/attributeoutputbase.hxx, the possible orders in
which the EndURL, RunText, EndRun (and probably StartURL) callbacks
may be executed when exporting an hyperlink is not explicit. This has
already caused at least four bugs: 47669, 52610, 53175 and 55820.
Docs.libreoffice.org only confirms what the names suggest:
* StartURL() and EndURL() are called in this order by
SwWW8AttrIter::OutAttrWithRange() and
MSWord_SdrAttrIter::OutEEField()
* RunText() and EndRun() are called in this order by
MSWordExportBase::OutputTextNode.
Could someone tell me what can be asserted about the calling order, or
give me a link to some documentation?
Do you mean documentation about the DOCX export as we have it in the
code, or about the fileformat in general, please?
If you mean the former - I tried to document as much as possible when
splitting the original .doc exporter into its .doc and .docx parts, like
here:
http://docs.libreoffice.org/sw/html/classDocxAttributeOutput.html
but to learn details about the calling order of various things, the best
is just to read the sources.
Do you have a case in mind that you'd like to fix? Or are you just
interested in helping improving the DOCX export in general? - in that
case it would be awesome to improve our DOCX export test coverage by
slowly copying the import tests to the import/export tests + fix
whatever is not preserved during the roundtrip :-)
All the best,
Kendy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.