Personal Book Builder: "xxx is not a valid font for use in resources."

Page 1 of 1 (9 items)
This post has 8 Replies | 1 Follower

Posts 1672
Allen Browne | Forum Activity | Posted: Sat, May 2 2020 11:32 PM

Hi friends.

I'm creating a commentary on Ephesians, but the PBB complains about whatever font I use: Times New Roman or Arial, or anything.

The compile works, but this is the error log:

[Info] Starting build for PBB:9443e6f8eddd4bb580ac36119aef2e8d
[Info] Converting
[Info] Converting D:\Data\SeekingTheKingdom\Commentaries\Ephesians_KingdomPerspective.docx
[Info] Compiling
[Error] Font '#Libronix User Interface' is not a valid font for use in resources.
[Error] Font 'Georgia' is not a valid font for use in resources.
[Error] Font 'Courier New' is not a valid font for use in resources.
[Error] Font 'Verdana' is not a valid font for use in resources.
[Error] Font 'Symbol' is not a valid font for use in resources.
[Error] Font 'Cambria' is not a valid font for use in resources.
[Info] Discovering
[Info] Complete

Suggestions?

The file is:

https://allenbrowneblog.files.wordpress.com/2020/05/ephesians_kingdomperspective-1.docx 

Posts 11107
Forum MVP
NB.Mick | Forum Activity | Replied: Sun, May 3 2020 8:34 AM

Actually, Times New Roman should not come in an error message - and doesn't for me - as this is the one Logos wants us to use: it will treat Times New Roman 12 pt as "standard" and convert it into the font you select for resource display in the Logos System Settings.

Changing the fonts for standard text and headings to Times New Roman, I could reduce the build errors to four fonts. However, it's difficult to wash out fonts from a document - Word doesn't find those and thus can't replace them - but anyway, as you know, those errors are a nuisance more than a functionality issue.

Running Logos 9 latest (beta) version on Win 10

Posts 1672
Allen Browne | Forum Activity | Replied: Sun, May 3 2020 3:55 PM

NB.Mick:

Actually, Times New Roman should not come in an error message - and doesn't for me - as this is the one Logos wants us to use: it will treat Times New Roman 12 pt as "standard" and convert it into the font you select for resource display in the Logos System Settings.

Changing the fonts for standard text and headings to Times New Roman, I could reduce the build errors to four fonts. However, it's difficult to wash out fonts from a document - Word doesn't find those and thus can't replace them - but anyway, as you know, those errors are a nuisance more than a functionality issue.

Thanks for the reply, Nick.
I guess I'll just ignore the errors then.

Posts 2089
Mark | Forum Activity | Replied: Sun, May 3 2020 6:47 PM

I ignore the errors.  I use Times New Roman and yet the errors still claim I am using other fonts (which I am not).  I always thought it must be a bug

Posts 1672
Allen Browne | Forum Activity | Replied: Tue, May 5 2020 6:17 AM

Mark:

I ignore the errors.  I use Times New Roman and yet the errors still claim I am using other fonts (which I am not).  I always thought it must be a bug

Thanks, Mark. Good to know I'm not alone.

Posts 2736
DominicM | Forum Activity | Replied: Sun, May 31 2020 11:41 PM

its an error in Word, but here are 2 word macros which may help, I use them first thing after importing my raw text:
The first resets the whole document to "normal"

Sub LogosPB_SetWholeTextToNormal()
  Selection.WholeStory
  Selection.Style = ActiveDocument.Styles("Normal")
End Sub 

The second resets all the "normal" sections within document to Times New Roman 12, and set to US english

Sub LogosPB_SetNormalFonttoTNR()
With ActiveDocument.Styles("Normal")
  .LanguageID = wdEnglishUS
  .Font.Name = "Times New Roman"
  .Font.Size = 12
End With
End Sub

hope these also help reduce your errors

Never Deprive Anyone of Hope.. It Might Be ALL They Have

Posts 2736
DominicM | Forum Activity | Replied: Mon, Jun 1 2020 12:36 AM

NB.Mick:
Changing the fonts for standard text and headings to Times New Roman, I could reduce the build errors to four fonts. However, it's difficult to wash out fonts from a document - Word doesn't find those and thus can't replace them - but anyway, as you know, those errors are a nuisance more than a functionality issue.

this may or not be of use, it will highlight turquoise any non-listed fonts in your document, but does not replace them:

Sub LogosPB_ShowOddFontsinNorm()
' Highlight all fonts NOT named in the list

With ActiveDocument.Styles("Normal")

myDiffColour = wdTurquoise

nonHighlight = 5

ReDim myFont(nonHighlight) As String

myFont(1) = "Times New Roman"

' your greek font here

myFont(2) = ""

' your hebrew font here

myFont(3) = ""

' additional to skip

myFont(4) = ""

myFont(5) = ""

nowColour = Options.DefaultHighlightColorIndex

Options.DefaultHighlightColorIndex = myDiffColour

Set rng = ActiveDocument.Content

rng.Font.Shadow = True

For i = 1 To nonHighlight

  If myFont(i) > "" Then

    thisFont = myFont(i)

    With Selection.Find

      .ClearFormatting

      .Replacement.ClearFormatting

      .MatchWildcards = False

      .Text = ""

      .Replacement.Text = ""

      .Font.Name = thisFont

      .Wrap = wdFindContinue

      .Replacement.Font.Shadow = False

      .Execute Replace:=wdReplaceAll

    End With

  End If

Next i

With Selection.Find

  .ClearFormatting

  .Replacement.ClearFormatting

  .MatchWildcards = False

  .Text = ""

  .Wrap = wdFindContinue

  .Font.Shadow = True

  .Replacement.Font.Shadow = False

  .Replacement.Highlight = True

  .Execute Replace:=wdReplaceAll

End With

End With

Options.DefaultHighlightColorIndex = nowColour

End Sub

 

Never Deprive Anyone of Hope.. It Might Be ALL They Have

Posts 27
Rick Koelz | Forum Activity | Replied: Mon, Jun 1 2020 10:23 AM

THANKS, DominicM.

All 3 of the macros will help me clean up my PBB work and eliminate lots of frustration. 

Got any more macro goodies?

Rick

Posts 2736
DominicM | Forum Activity | Replied: Thu, Jun 4 2020 6:03 AM

Many :P mostly not relevant to logos

Never Deprive Anyone of Hope.. It Might Be ALL They Have

Page 1 of 1 (9 items) | RSS