Hello
On https://wiki.logos.com/PB_%e2%80%93_Warnings_$26_Errors#Unrecognized_character some images are not visible. Only a replacement is there.
And the Warning "[Warning] Bad character in string: 0x000A" isn't discussed.
If I'm correct this is if an image is in the .docx. And the warnings come twice per image.
Thanks for the fix.
the Saturday bump of posts without responses ...
The content was last updated 6 years ago by user NB. Mick. Images were lost because of an Admin change 3 years ago (to using Amber).
NB. Mick may be able to assist and update the content (Logos 4 era!), and I will alert him to this post.
And the Warning "[Warning] Bad character in string: 0x000A" isn't discussed
Where do you see this? There is a Warning for string: 0xFFFD that is discussed.
Images were lost because of an Admin change 3 years ago (to using Amber).
They were lost due to a hard disk failure. The images on the wiki weren't stored redundantly and a number were lost when the disk failed. We recovered all that we could and uploaded them to Amber. We also switched the wiki to using Amber for all new images because it uses cloud storage with 99.999999999% (11 9's) annual durability.
Hello Dave
May it is a misunderstanding here. I have seen the
There is a Warning for string: 0xFFFD
[Warning] Bad character in string: 0x000A
Thanks.
Fabian
Images were lost because of an Admin change 3 years ago (to using Amber). They were lost due to a hard disk failure. The images on the wiki weren't stored redundantly and a number were lost when the disk failed. We recovered all that we could and uploaded them to Amber. We also switched the wiki to using Amber for all new images because it uses cloud storage with 99.999999999% (11 9's) annual durability.
Hello Bradley
Thanks for the explanation.
The content was last updated 6 years ago by user NB. Mick. Images were lost (...) 3 years ago (...) NB. Mick may be able to assist and update the content (Logos 4 era!), and I will alert him to this post.
My change to this page was an update due to the fact that the Empty Heading (a paragraph formatted in Heading Style in the text processor not containing any text besides the paragraph mark) was treated by the then-current Logos version as a build-breaking error. I kept the already existing picture in this one entry on the page and much of the entry text and just moved it on the page from the Warnings to the Errors and updated as needed. I could try to reproduce the picture in my version of Word 2016, but it is installed in German language - but moreover, the Logos PB Compiler currently just puts a Warning into the log "Skipping Empty Article", there's no actual need for the PB author to do anything.
I think, this wiki page from many years ago needs an update:
EDIT: I started updating the page and made changes to the intro as well as the entry about empty articles in the wiki. The other warnings still need to be updated.
I guess it would be anyway great to use current images from Logos 10.
May it is a misunderstanding here. (...) My goal was to say it would be good if the [Warning] Bad character in string: 0x000A would be discussed too. Then I gave an explanation when I encountered this warning...
0x000A (and 0x000D) are explained here i.e. "The Unicode standard does not prescribe specific meanings for the control codes 0x000D (carriage return) and 0x000A (linefeed). These codes are not required to be used in combination. If used individually, either code can represent itself only or both codes together. The application must always determine what these codes represent."
I can provide an explanation along these lines and summarize by stating that it doesn't stop compilation of the PB (I think you can display these as symbols in your source file and determine how they affect the formatting)? You could upload the file with that warning if necessary.
The content for Warnings/Errors may never be complete, and could be out of date e.g. Mick's update of Empty Paragraph. The (updated) general comment at the start of the wiki should suffice for this.
Fabian, please respond
I can provide an explanation along these lines and summarize by stating that it doesn't stop compilation of the PB (I think you can display these as symbols in your source file and determine how they affect the formatting)? You could upload the file with that warning if necessary. Fabian, please respond
Hello Dave,
Thanks, I have seen yesterday your post, but I was out. I have seen this post from Microsoft before as I searched for the issue. Unfortunately I haven't seen any special character. I Have only the paragraph mark before the image and one after. I found out I have 8 errors. Two before the Bible and six after. So I came to the conclusion it must be due the images. After I have deleted one image the Error was away.
I found out not all images produces this issue. 8838.White Image above the text.docx But this and others do. If I'm correct only images which still have the full content even it is cut.
With this there is no image 1106.Meine Bibel.docx
Hello Dave and NB.Mick
Many thanks for updating the wiki page.
I have another warning to add.
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.26.40.44 from https://community.logos.com/forums/p/225369/1316630.aspx#1316630. It would be good to mention https://wiki.logos.com/Logos_Bible_Book_Names in the solution to find the issue. In this case Ezekiel 40:44.
Also to shorten the PB to find issues is a good way. But the issue with the re-import should be fixed. it is a pain to work with PBB, every time close and reopen Logos.
I don't know if you want to add this too as it is not a Warning or Error. More a fix if this happens to others. Except Logos fixes it. https://community.logos.com/forums/p/225990/1320129.aspx#1320129
Thanks
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
