Marcin W. wrote:
I have been using single page styled (X)HTML
option in your Windows converter so I am assuming it should look quite
similar to Word document. I realize 100% accuracy would be hard to
achieve, but in case of my documents there are visible differences in
the spacing, fonts, and margins of the numbered items.
Yes, there are indeed small but noticeable differences in horizontal and
vertical spaces.
* I didn't notice much font problems (but may be I didn't look closely
enough). I don't see font Unbuntu Mono in "here is some text in the
Ubuntu Mono typeface" because I don't have this font on my computer but
<span style="font-family: "Ubuntu Mono";"> has been generated.
* In the "fancy calendar", the facts that "December 2007" is too small
and that "Sat" is gray and not blue seem to be bugs related to fancy
table styles.
* The footnote and endnote are numbered "2" and not "1" because your
DOCX file contain pseudo footnotes and endnotes (separators in fact)
numbered "0" and "1". In all our other DOCX files, these pseudo
footnotes and endnotes are numbered "-1" and "0". So this one may also
be considered to be a bug.
It's too late to fix the two above bugs in next release. We plan to
release v1.2.1 in the next few days.
Attached is one example I can share. Please turn your attention to the
Multi-level Lists paragraph, items at the 3rd list level. There is more
space between numbers and text in the original doc file, also the second
line of the paragraph has a different margin in the HTML.
In the Continued Lists section, you can see that the alignment of the
numbered items and the paragraph is off in the HTML file. I was using
Chrome to open the HTML file.
So my question is if issues similar to the one above regarded as bug and
covered by the support.
The majority of the issues are limitations, not bugs. As you wrote it,
100% accuracy is impossible to achieve. In other words, the demo.html
you sent us is very close to the best our tool can do.
After looking at the sample DOCX you sent, I can even say that I don't
see how customization through scripts could help here.
Of course, it's always possible to develop a custom CSS (in addition to
the automatically generated CSS contained in demo.html) which would
adjusts some of the faulty horizontal and vertical spaces. Example:
---
p {
line-height: 1.2;
}
---
(Your demo.docx contains "line-height: 1.5;")
Also, in the file there are floating images that are positioned out of
the flow of the text. Is this supported at all by your product?
No, not at all. This limitation is documented as follows:
---
* Text wrapping of tables and pictures other than the simplest one.
---
in "Limitations and implementation specificities",
http://www.xmlmind.com/w2x/_distrib/doc/manual/index.html#limitations
--
XMLmind Word To XML Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/w2x-support
