BUG: PBB {{Field Syntax}}
The codes at the end of my test docx file show a few things wrong with the {{ }} syntax for Fields.
To get the space after the 3:15 milestone and footnote 2 I had to expand the character spacing (Ctrl+D in Word 2007) by 2 points, else there is no space as per the 3:16 milestone.
The compiled resource shows Search Fields for footnote, but not bible text. The Basic Search drop-down shows no fields.
The syntax to ignore the Jn 3:16 reference had to be amended.
Headwords no longer appear as an active reference (they did with @Topic).
NB. makes no difference if the document is built as Bible Notes or Bible.
Dave
===
Windows 11 & Android 13
Comments
-
Dave Hooton said:
Headwords no longer appear as an active reference (they did with @Topic).
They are no longer recognised in RC2.
Dave
===Windows 11 & Android 13
0 -
I've downloaded your source document and compiled the book, but have not had a chance to review the field syntax. I'll try to do that by tomorrow.
Update: I retyped the headword milestones in your document and they were recognized in the resulting book. I typed them in Normal style above the headings.
0 -
Things just got worse in RC3 as the reference I want to be ignored is now detected using the correct syntax of spaces either side the reference.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Things just got worse in RC3 as the reference I want to be ignored is now detected using the correct syntax of spaces either side the reference.
I downloaded the file above to make sure I had your latest version of it and compiled the book. The 'John 3:12' reference at the end of the book, with the escape syntax, is not being detected as a hyperlink in the book. I'm testing this in a post-4.3 build, but it shouldn't have changed from 4.3. I will also bring it over to a 4.3 RC3 build and retest to make sure.
Regarding the first milestone in the document, [[@headword:Blessed Ones]] -- did you retype or copy and paste? It's still using the 'Heading 2' style with the font size decreased. I'm not sure that is where the problem is, or whether Word has added some other tagging we're not seeing, but I think if you retype it in Normal style, it will be recognized as a milestone.
0 -
Melissa Snyder said:
Regarding the first milestone in the document, [[@headword:Blessed Ones]] -- did you retype or copy and paste?
It was a copy/paste/resize + clean the document. I changed it because the other headers (also Heading 2) were not recognised after Beta 13 + the ignore code was not recognised in RC3.
Changing it to Normal style has not resolved the situation, so something has changed since Beta 13 that affected the codes that worked quite well in several betas before then.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
It was a copy/paste/resize + clean the document. I changed it because the other headers (also Heading 2) were not recognised after Beta 13 + the ignore code was not recognised in RC3.
Changing it to Normal style has not resolved the situation, so something has changed since Beta 13 that affected the codes that worked quite well in several betas before then.
Please try 'retyping' it and let me know if that works for you as it does for me.
0 -
Retyping and cleaning the file made no difference.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Retyping and cleaning the file made no difference.
Could you attach the revised document?
0 -
It's now much revised, but still misbehaving with headword milestones and ignoring a reference.
Dave
===Windows 11 & Android 13
0 -
It's now much revised, but still misbehaving with headword milestones and ignoring a reference.
Dave
===Windows 11 & Android 13
0 -
Dave
Headwords need to be on the line under the reference/topic with a capital "H" in normal style
ie:
PEACE ON EARTH
Headword:Peace on Earth]]"Your text here
---------------
and internal link of
[[Text2show >> Headword:Peace on Earth]]
Hope that sorts that half of issue for you
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
DominicM said:
with a capital "H"
Thanks Dom, that worked; I didn't need to change style or position.
Logos have introduced a subtle bug because lower case "h" worked until Beta 13.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
It's now much revised, but still misbehaving with headword milestones and ignoring a reference.
Look at this version as the Headwords are fixed by using cap "H". Note that lower case "h" worked until RC1. That leaves the reference {{~ Jn 3:12 }} as not being ignored.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
To get the space after the 3:15 milestone and footnote 2 I had to expand the character spacing (Ctrl+D in Word 2007) by 2 points, else there is no space as per the 3:16 milestone.
I am seeing the same lack of space issue and will report it.
0 -
ok I think I have tracked the other issue down also:
IMO (which may be wrong) there is a flaw in the compile process...
if I highlight the tag "{{~ " including space and clear formatting and also the close " }}" then the link now is hidden
if I add the tag but leave the style alone it does not work, this link should hide regargless of formatting I choose
so IMO it has to be a flaw in the parsing process where the logic for the hide bit isnt being run, and realistically why should we have to change our formatting style just to get it working.. seems daft to me...
posted tweaked version, perhaps it will hep the coders
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
I too cannot get the escape syntax to work. I wanted Genesis 49 on a line by itself not to be detected as a hyperlink. I tried the syntax as documented:
{{~ Genesis 49 }}
But it didn't work. It showed up as a hyperlink in the resulting book.
Interestingly, when I tried putting any text immediately after it (with no space)
{{~ Genesis 49 }}foo
...it worked. Showed up as Genesis 49foo. (That's probably because it doesn't parse as a valid Scripture reference.) But I don't want the "foo" there, and as soon as I remove it, the thing goes back to not working.
0 -
good catch, maybe a non-breaking space would do same as workaround - until its fixed
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
DominicM said:
good catch, maybe a non-breaking space would do same as workaround - until its fixed
Nope, that didn't work. Good suggestion, though.
0 -
Rosie Perera said:DominicM said:
good catch, maybe a non-breaking space would do same as workaround - until its fixed
Nope, that didn't work. Good suggestion, though.
Development is looking into some bugginess with the Escape syntax. I can get it to work most of the time, but not every time, which is our goal, of course.
0
