Personal Books Bug? Inconsistent warnings for field codes

Eleanor Emmott
Eleanor Emmott Member Posts: 173 ✭✭
edited November 2024 in English Forum

This post is related to the issue on this thread: http://community.logos.com/forums/t/39663.aspx

However, that thread is locked, so I am posting my comments/discoveries here.

 

While working on a Personal Book lectionary, I have been getting warnings that say: [Warning] closing field day that is already closed.

Other people have noticed these before, but I want to post some examples to show some odd behavior.  So here are three examples, with corresponding .docx files.  (I have just pasted the text from the files into this post for convenience.)


 

In this
first example, we have field-on and field-off codes for date, season, and day

All the text is in Normal style in MS Word.

The field codes all match and the text compiles
with no warnings

 

{{field-on:date}}

Sunday, December 2, 2012

{{field-off:date}}

 {{field-on:season}}ADVENT{{field-off:season}}

{{field-on:day}}

First Sunday of Advent

{{field-off:day}}

 

0412.pb field bug example 1 - on&off codes, no styles.docx

 


In this second
example, we have field-on and field-off codes for date, season, and day

The date uses Word Heading 2.  The liturgical day using Word Heading 3.

The field codes all match, but the compiler gives
warnings:

[Warning] closing field date
that is already closed.

[Warning] closing field day
that is already closed.

Despite the warnings, I
believe that Logos treats the fields as well-formed.

 

{{field-on:date}}

Sunday, December 2, 2012

{{field-off:date}}

 {{field-on:season}}ADVENT{{field-off:season}}

{{field-on:day}}

First Sunday of Advent

{{field-off:day}}

6646.pb field bug example 2 - on&off codes, with styles.docx


 

In this third example, The date uses Word
Heading 2.  The liturgical day using Word
Heading 3.

Note that
we have field-on and field-off codes for season, but only field-on codes for
date and day.  The field codes do not
match, and we should expect to see a compiler warning
.

Instead,
the text compiles without any warnings or errors, and the PB treats the fields
as well-formed.

 

{{field-on:date}}

Sunday, December 2, 2012

{{field-on:season}}ADVENT{{field-off:season}}

{{field-on:day}}

First Sunday of Advent

 

8463.pb field bug example 3 - field-on codes without field-off.docx

 

So, is it a bug or a feature?  My thought is that there should not be a warning in example two and there should be a warning in example three.