PBB: Bullets in the Word Document creates [Warnings]
Hello
If the PBB has bullets I get warnings. Even if they works perfect.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
Comments
-
If the PBB has bullets I get warnings. Even if they works perfect.
Fabian,
it might help if you posted an example (if necessary an excerpt) from your PBB, and the PBB-log. I only get one of those spurious font-errors (the bullet itself is font: symbol which comes with Windows - I thought FL wanted to remove those senseless messages), but no warnings.
On a more general note: the Files subforum is geared towards PBB building and you may be able to receive competent answers from other PB-makers quicker if you post PB-related issues and questions there, as well as PB sources you want to share with the community.
Have joy in the Lord!
0 -
Hallo NB.Mick
Thanks. I haven't noticed this thread.
The bullets are the standard bullets of Word.
[Error] Font 'Symbol' is not a valid font for use in resources.
The file is the LSV Bible I created.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
The bullets are the standard bullets of Word.
[Error] Font 'Symbol' is not a valid font for use in resources.
As a background: Some years ago, Faithlife changed the way it treated fonts in Logos/Verbum - maybe due to licensing contracts with font developers. Basically they stopped shipping fonts to the users' operating system, users had to acquire and install fonts if they wanted to use them outside Logos (such as UNICODE fonts for Greek and Hebrew that may not be present in the firstplace). Maybe in course of this, the PB compiler no longer assumed any given font in the PB source documents - it throws an error message for any font except Times New Roman, which is treated as "default" by Logos (i.e. replaced by whatever resource font you have configured). I wrote this is 'spurious' because this is not a real error - it does not break the build or severely impact the PB resource, actually it doesn't impact the PB resource at all, since Logos can display all installed fonts, and I believe it would even substitute others.
What can you do? Most users probably ignore the font errors.
If you really want to see 0 errors, 0 warnings as compile result, use Times New Roman for everything in your resource. I built a small PB with three bulleted items in it (Symbol font error), and then changed the bullet item in Word, remember you can freely choose the font and then the character that is used as bullet - a minus sign would do, there's also a nice black triangle pointing right in font Times New Roman.
Have joy in the Lord!
0 -
Thanks, yes I learned this earlier to use only New Times Roman. At least most of the time. One exception is a fully Greek resource.
The Hebrew gives also errors in New Times Roman and in SBL Hebrew. So either of this should be improved by Logos.
I wanted to send my file to the LSV maker and then it would be good if there is no warnings or errors.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0