Jaromir Kuzelka

[Jaromir Kuzelka]

Thanks for the answer. Understood.
Unfortunately, I am not able to replicate the error exactly. There could be some problems in generation caused by problems with integrity of sections (possibly caused by Compare function in Word, as I reported separately). But after I corrected style names and updated Document settings with correct style names, problem did not appear again.

Note:
Generally, I find document settings and section definitions in document quite fragile and with potential to loose or break them down in case document is being edited in MS Word and generated iteratively.

[Jaromir Kuzelka]

Thank you for response.
Well, I think this kind of usage could be quite common. So I would suggest to investigate the behavior and make eaDocX compatible with this scenario.

I also understand that Word is behaving extremely complex and mysterious, so it is hard to make it work at any occasion.

Add “take a copy of the eaDocX generated document”: please, what is suggested long term lifecycle of documents combining both written part and generated part to avoid loss of data and structure information for eaDocX? Making copies prior to any changes does not look comfortly to me, especially in iterative tuning prior to release new version. Every wrong step could ruin the work by losing the information needed for eaDocX to generate the doc.

[Jaromir Kuzelka]

Thanks for answer. Yes, I agree, the problem is in the comparison in Word.
My question directs to how to perform the comparison correctly to avoid loss of the XML information you noticed. Or at least, what should I do to protect this information in the document, or tweak it back to document manually (copying text around Section marks?, or so).
Clients are used to this approach when reviewing new version, so I would like to use Word comparison mechanism. And it is annoying to loose all the sections and profile information and recreate it manually after every review from client.

[Author]

Posts