Family Historian User Group

tatewise wrote: ↑

12 Dec 2020 14:19

... The only alternative workaround is to move the <para> or <br> codes to the end of Sentence Templates.

I was wondering what might happen there. I am reasonably certain that, in v6 or earlier, I tried the codes at the end of the sentences, with some odd formatting results. Indeed I have a note that you warned that this might result in

odd side effects on the superscript cross-reference numbers to Sources. They are either too close to the following sentence, or overlay the start of the line and the next line is indented.

Putting the codes at the start worked for me (and still does in v6, of course). I guess it remains to be seen if the odd effects have gone away in v7. However, this may result in possibly minor effects for me: Some of my facts sort-of-always come in pairs - for instance baptism will always be preceded by a birth - it's just the way that I work. I can omit the <para> from the start of the Baptism narrative sentence and it runs on from the previous sentence which (late baptisms excepted!) will always be the birth. That seems OK. But a birth will not always be followed by a baptism, so I'll not be able to run the birth and following baptism narratives together. Which may not be a major issue, of course.

Just to add to the mix, I have been using occasional Narrative Sentence over-rides of I've done that where I have given up on trying to get a sensibly readable result from the generated sentence and have made the Fact Note substitute for the computerese. Remarkably, even though I have my reports to normally add the Note via the setting at the report level, rather than via all the sentences, the Note isn't printed twice.

Using <para>{note} will bring two issues - first the loss of the newline in front of my notes and secondly the loss of any Rich Text in the Note. However, based on what I just tried in v6, it looks as if will work just as well for replacing the computerese with my note text and will not (I presume) suffer the loss of the Rich Text. However, goodness knows where the new line - if any - will go in v7...

More mental implementation notes for me...

Yes, it is an unfortunate scenario that hopefully CP will fix in an update to FH v7.
In my opinion, FH v7 has been released for commercial reasons with some significant snags.
New users will take a while to discover them but meanwhile established users are inconvenienced.
It is a bit like a major Windows 10 feature update. I always wait to let others find the bugs.

A workaround that seems to work OK is to insert a non-printing character before the <para> or <br>. I've used zero width joiner by entering "U+200d" via AutoHotkey. Alternatively, you can use copy and paste from Zero Width Joiner.