Prince J. wrote:
Thanks Hussein,
Sorry, that was my mistake, I had run a transform on your output to
convert sections to listitems (all content of the docx file needs to go
inside a single section).
No problem.
From what I can understand from your explanation below, EULA h2 elements
(or any outline level) followed by EULA h2 elements (or the same outline
level) will be converted to bridgeheads and will be enclosed under the
same parent element. This is inline with the expectation, but the issue
I am facing is with EULA h2 elements with a EULA para in between, that
is supposed to be a part of the preceding EULA h2. Such elements are
getting separated into different sections. As per your explanation
below, w2x will always do this because of the rule mentioned below,
correct?
Yes.
Is there a workaround for this? Please let me know.
XMLmind Word To XML has been designed to be extremely customizable. You
can solve the vast majority of (even pretty complex) problems using a
few lines of XED script.
See "XMLmind Word To XML Manual, Customizing the output of w2x, The
general case",
http://www.xmlmind.com/w2x/_distrib/doc/manual/index.html#general_customize_semantic_xml
However, as explained before, we'll not write this small XED script for
you and this, even if you were a customer.
Also regarding:
*/--> To avoid this kind of problem, please do not use MS-Word styles /*
*/specifying an outline level (e.g. EULA H2) for paragraphs which are not /*
*/actual headings./*
*/ /*
*/For example, something like EULA H2 should be reserved to actual level /*
*/#2 headings./*
*/ /*
*/"11.1. Disclaimer of Warranty. TO THE EXTENT PERMITTED BY APPLICABLE /*
*/LAW, ACME Corp...." is NOT a level #2 heading./*
*/ /*
*/"11.1. Disclaimer of Warranty." is a level #2 heading followed by /*
*/paragraph "TO THE EXTENT PERMITTED BY APPLICABLE LAW, ACME Corp."./*//
Do all outline levels get converted to sections?
Yes and this makes sense.
Even if we convert the
level #2 headings to be what you have described above, I don’t want the
h2 headings to be converted to sections. From the output it looks like
if a EULA h2 is followed by a EULA para, it will be enclosed in a
section, which is not desirable.
I will work with my writers to see what can be modified in the document
to avoid such a situation. Thanks for your inputs again.
My recommendations:
1) Keep your "EULA H2" MS-Word style as is with its current outline
level and reserve it for headings starting a new sub-section. (Just like
"EULA H1" headings start a new section.)
2) Define a new MS-Word style, may be called "EULA Clause", may be a
custom numbered list style, having NO outline level, and use it for
paragraphs starting a new clause. Example:
EULA H1) Other Important Information
EULA Clause) 11.1. Disclaimer of Warranty. TO THE EXTENT PERMITTED BY
APPLICABLE LAW, ACME Corp....
EULA Clause) 11.2. Limitation of Liability. SOME STATES AND JURISDICTION...
EULA Para) TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND...
EULA Clause) 11.3. Proprietary Rights. ACME Corp. retains ownership...
EULA Clause) 11.4. Force Majeure. ACME Corp. shall not be response...
Thanks
Prince
From now on, I'm really sorry but I'll not answer to any of your
support requests. More information in "XMLmind Word To XML support
policy", http://www.xmlmind.com/w2x/support_policy.html
--
XMLmind Word To XML Support List
w2x-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/w2x-support
