Conal-Tuohy / VMCP-upconversion

Ferdinand von Mueller's correspondence upconversion from MS Word to TEI XML
Apache License 2.0
3 stars 2 forks source link

Style problem Arthur can't resolve #35

Closed LucasHorseshoeBend closed 7 years ago

LucasHorseshoeBend commented 7 years ago

I have cleaned all but one problem in the final files.

The remaining one is with the style in the analytics labelled 'footnote reference' and affects 60 files, resulting in a style label Footnote%20text and footnote numbers suppressed in the footnote.

There was what I thought was a lucky a lucky accident that would help me see what was going on, that resulted in an earlier version of a file and its final version both present in the set, and only the final versi0n is affected:

Version with problem: http://vmcp.conaltuohy.com/xtf/view?docId=tei/1860-9/1862/62-06-06b-final.xml

Version without: http://vmcp.conaltuohy.com/xtf/view?docId=tei/1860-9/1862/62-06-06b-final.xml

I assumed it would be something to do with the styles present in each file, and although I could find a difference using the Word style listings, this was not a consistent difference between affected files and those not affected.

I tried overwriting the styles in the affected documents with the styles from the template, either one by one or en masse, and have not achieved a solution.

I am not familiar with XML coding, and don't know what to look for in those versions to try to get a handle on the issue.

It seems that it is something that has been happening when Rod was making files final, as there is an extremely low incidence of it in 'not final' files, 8 in 10,392 files compared to 60 in 5181 final files.

I would like both to remedy the problem and ideally to understand how it arises so that we can prevent more accumulating when we start setting more files to final from the week after next when Rod returns form China.

LucasHorseshoeBend commented 7 years ago

I have now found a solution. I don't understand what has happened to cause the problem, but if I copy and paste the offending file into a new blank template file and then save that in the place of the offending one, the problem disappears.

I think you can safely close this issue.