Wiki Logos issues

Fabian said:

On https://wiki.logos.com/PB_%e2%80%93_Warnings_$26_Errors#Unrecognized_character some images are not visible. Only a replacement is there. 

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.

Fabian said:

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.

Dave Hooton said:

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:

• checking of the respective Warnings and Errors (are they still valid? is the list complete?) and of the activities users need to do to get rid of those (if they want or need to).
• update of some of the language (one of the few wiki pages that make first-person statements)
• inclusion of meaningful pictures where needed and broken.    

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.

Fabian said:

May it is a misunderstanding here. (...) My goal was to say it would be good if the 

Dave Hooton said:

[Warning] Bad character in string: 0x000A

would be discussed too. Then I gave an explanation when I encountered this warning...

Fabian said:

If I'm correct this is if an image is in the .docx. And the warnings come twice per image.

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.