PBB Problems: Confirming Rosie's theory and proposing a work-around

On another thread, Rosie suggested the fact that milestone's aren't working problem is due to Word adding a whole bunch of fluff to it's XML. She's right. I did an experiment saving files with Word 2010 and with WordPad (the one that comes with Windows 7). I was super-careful in Word, pasting milestones into the document in plaintext format, thus ensuring it wasn't editing milestones that caused problems. Here's the result (I've bolded the actual text):
Word 2010:
<w:p w:rsidR="00000000" w:rsidRPr="0006385B" w:rsidRDefault="005304EF"><w:pPr><w:pStyle w:val="NormalWeb"/></w:pPr><w:r w:rsidRPr="005304EF"><w:t>[[@Page</w:t></w:r><w:proofErr w:type="gramStart"/><w:r w:rsidRPr="005304EF"><w:t>:111</w:t></w:r><w:proofErr w:type="gramEnd"/><w:r w:rsidRPr="005304EF"><w:t>]]</w:t></w:r><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:t>EVIDENTIAL TONGUES</w:t></w:r><w:proofErr w:type="gramStart"/><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:t>:</w:t></w:r><w:proofErr w:type="gramEnd"/><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:br/><w:t>AN ESSAY ON THEOLOGICAL METHOD</w:t></w:r></w:p>
WordPad:
<w:t xml:space="preserve">[[@Page:111]]EVIDENTIAL TONGUES:</w:t><w:br /><w:t xml:space="preserve">AN ESSAY ON THEOLOGICAL METHOD</w:t>
The Word 2010 version compiles OK, but none of the page milestones are recognised. The WordPad version has the milestones recongised, but unfortunately WordPad doesn't preserve styles, so the TOC doesn't work. But, if you save your Word Document as an RTF, then close the document, and re-open it in Word, then re-save it as a docx file, you get the following:
<w:t>[[@Page:111]]</w:t></w:r><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:t>EVIDENTIAL TONGUES:</w:t></w:r><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:br/><w:t>AN ESSAY ON THEOLOGICAL METHOD</w:t>
That method gives both page numbers and TOC headings, and is now my preferred work-around for troublesome documents.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
Mark Barnes said:
<w:proofErr w:type="gramStart"/><w:r w:rsidRPr="005304EF"><w:t>:111</w:t></w:r><w:proofErr w:type="gramEnd"/>
I do not have Word to test this, but I'm wondering if you turn off the spell and grammar checker if it wont get rid of the proofErr tags?
0 -
Mark Barnes said:
But, if you save your Word Document as an RTF, then close the document, and re-open it in Word, then re-save it as a docx file, you get the following:
<w:t>[[@Page:111]]</w:t></w:r><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:t>EVIDENTIAL TONGUES:</w:t></w:r><w:r w:rsidR="004E520F" w:rsidRPr="0006385B"><w:br/><w:t>AN ESSAY ON THEOLOGICAL METHOD</w:t>
That method gives both page numbers and TOC headings, and is now my preferred work-around for troublesome documents.
Yup, I've just tried that method now, and it finally seems to get around some other link problems I was having that the WordPad method didn't work for.
Thank you!
I just added this to the Personal Books wiki page, along with instructions for building a PBB and a couple of other edits.
0 -
Jannie van Niekerk said:
I do not have Word to test this, but I'm wondering if you turn off the spell and grammar checker if it wont get rid of the proofErr tags?
Choosing "Hide spelling/grammar errors in this document only" doesn't work get rid of those tags, unfortunately. Possibly it might if you did it before you put any text in the document.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I've been getting around the need to use RTF as an intermediate step to saving the docx file. The texts I'm building resources from are Syriac texts I have stored in a morphological database. I just wrote a quick page to extract the text with some headers and the milestone tags. I then just copy from the page directly into Word. The only gotcha is that Word doesn't always properly handle converting the H1/H2/H3 tags into Heading styles. This can be worked around if you start with a document that has some text with each of the Heading styles you want in your document and then delete that text when you are done pasting.
So basically, you can get proper milestone recognition as long as the source being copied into Word is well behaved.
By the way, if anyone wants to play with these Syriac texts just goto http://syriac.tara-lu.com/syriac once on that page select the Manuscript Generator. Some of the Manuscripts do not exist in their entirety yet. The most complete are the UBS Peshitta (NT) and Aphrahat Demonstrations (63450 AphDem). The The Odes of Solomon: The Syriac Text has just snippets.
EDIT:
I have some of these texts with vowel pointing, but they are displayed without vowel pointing so that when they are imported via PBB into Logos they will display properly. Logos 4 still (after 12 months) cannot use .NET4 and so cannot properly display vocalized Syriac. Can we PLEASE get this sometime soon?
0 -
Thank you Mark. I've filed a case on these things and included the links to yours and Rosie's posts.
0 -
I had noticed the same grammar issue with many of my tags, including page numbers and headwords. The [[@Page:number]] gives a grammar error because Word wants there to be a space following the colon. If you go into the grammar checker and choose to "ignore rule" it ignores this throughout the document and doesn't put in any of the gramStart xml tags.
This hasn't solved all of my tagging problems, but it fixed a large number of them!
0 -
Mark:
How do you read the XML? Do you have a viewer of some type?
0 -
Bill Cook said:
How do you read the XML? Do you have a viewer of some type?
This is brief, but should help: http://community.logos.com/forums/p/34246/256695.aspx#256695
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
OK, very interesting...
Thanks!
0