Compatability Issue
Help appreciated: I am compiling Madame Guyon's Autobiography and I get this error six times:
[Error] Document contains an unsupported VML image which will not appear in the final document. To use this embedded image, open the document in Word, select "Save As...", and deselect the "Maintain compatibility with previous versions of Word" option. Then rebuild the book.
I am using Word-2016 and for the life of me cannot figure out how to turn off the compatibility option. I've spent way more time on it than it is worth.
Anybody run into this or just know how to do this?
Comments
-
I've seen this error in the past (even in documents with no pictures at all that compiled without error previously) and came to think this is a spurious bug of the compiler. I couldn't find a way to fix it either (with Word 2007) and choose to just ignore that.
Faithlife never commented, I think.
Have joy in the Lord!
0 -
Thanks. The docx has no pictures in it. I'll ignore it.
0 -
I am using Word-2016 and for the life of me cannot figure out how to turn off the compatibility option. I've spent way more time on it than it is worth.
If the file has "Maintain Compatibility" selected, then this option will show up when you choose "Save as". If Maintain Compatibility is already switched off then nothing will display.
Does the document seem to work correctly? If it does, it might be better to ignore the errors rather than try and fix them.
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 -
Mark:
Thanks. That does not show up, so compatibility must be turned off, but I still get the error. Thanks.
0 -
Calvin,
I think I may have figured it out.. It seems to be a "Microsoft 2016 improvement/Bug".
I guess your process is:
- copy your html direct into Word 2016
- (maybe save as rtf)
- save and reopen in Word 2016
- process/adjust
- save
- then compile PB
The error seems to be being caused by the paste into word function in 2016, and unlike previous version saving to rtf don't fix it..
If you want to remove the error there appears to be a way to work around it though, is working for me:
- Use Explorer and not Edge
- Copy and paste into Word as normal
- Also Save Page as "HTML complete" so images get saved
- use following macro to replace all graphics with a placeholder [Image:#]
- manually re-add the pictures from the saved page directory in appropriate places
- Save
- Error not present on compile
Macro is:
Sub SetPicPlaceholder()
Dim Pic As InlineShape
Dim Idx As Integer
For Each Pic In ActiveDocument.InlineShapes
Idx = Idx + 1
ActiveDocument.Range(Pic.Range.Start, _
Pic.Range.End).Text = _
"[Image:" & Idx & "]"
Next
End SubHope that helps
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
Actually I don't think so. I have a PB source I built privately which definitely was never exposed to recent MS Word versions such as 365 or 2016, which does not contain pictures and did not come from html, but originally from a pdf. Still L6 one day started to show this non-error on the compile logs. To me it's a PB compiler bug.
Have joy in the Lord!
0 -
well, all I can say is its helped me remove over 140 VML errors in one book.. and over 200 since I adopted the process..
We will have to agree to disagree on the cause, but since adopting this process it has worked every time for me in removing this error.. in my books, silly thing like horizontal lines and drop capitals as images are the main culprits so far..
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
We will have to agree to disagree on the cause, but since adopting this process it has worked every time for me in removing this error..
I don't disagree with you on the error resolution (or workaround), just on the cause of it.
Your description of the cause ("a Microsoft 2016 bug") sounds to me as if Microsoft changed something in their Word 2016 generation of the docx file which throws the compiler off. Actually we don't know if Microsoft changed anything in the docx creation that would be relevant for the Logos PB compiler - what we do know is that the compiler now throws this spurious error. And that even for files that haven't changed and haven't been saved with Word 2016.
So this is not a Word 2016 bug, but a change/bug in the PB compiler (maybe in reaction to MS changes, which we don't know). Maybe there always was slightly buggy or superfluous data within the docx that the compiler ignored, and now points out (which should be a warning rather than an error).
I am very glad that you found a way to get rid of the error - nevertheless, I personally don't want to invest that much unnecesary work on my PBs if I can help it, so I choose to ignore that message. If the error one day really prevents the build of a PB, I'll be happy to come back and use your workaround. My wish would be for Logos to display this as a warning only or don't display it at all.
Have joy in the Lord!
0 -
this is also in Word 2010
0 -
This is happening to me too, now in 2021, getting two such 'errors' while trying to build my first ever Personal Book.
I opened a DOC file in Word 2010, saved it as DOCX, had no 'maintain compatibility ...' checkbox in the save window.
I realize that 'image' may not be a picture in the traditional sense, but there is nothing like that in this text document (its web hyperlinks become 'disfunctioned').
When the build is completed, I do get the 'Logos is indexing' notification; typing a word or phrase in the SEARCH box afterwards does NOT find the string in "Your Documents" and "Your Personal Documents" -- copy/pasting either a word or phrase into the box does get found.(I also get an error telling me that the Font [family] 'Goudy Old Style' is not a valid font for use in resources.)
Win 10 x64 [19042 (from system info)] updd; i7 7700, 32GB, 2T.
Logos 9.2.0.0014 updd.
Office 2010, updd. (Security)0
