Family Historian User Group

The FH7 report writer honors italicization, bolding, and underlining when they appear in notes, but apparently it isn’t possible to get such formats into tag fields or exhibit captions. For example, I have a number of of ship photographs whose names should be displayed as, say, RMS Aquitanita. I have tried italicizing the name without success. Moreover, the report writer doesn’t seem to recognize <i>Aquitania</i> which in some software was the format for italicization. The same problem exists if one wishes to have a tag entry field in one of the special formats.

Am I missing the solution to this problem?

Hi Robert.
That is a current limitation in Reports. Only entire classes of text can be formatted via the Options > Format tab.
I believe that CP are aware of those restrictions.

I have even tried rich text formatting the Link Note caption on Media but the formatting is ignored in Reports.

If you can somehow incorporate the formatted text into a Note field and then use the {note} code in the Sentence Template, then the formatting will work.

Otherwise, the only alternative is to use Save Report As... > Word-Processor Document (RTF)... and insert the formatting using a word-processor such as MS Word.

Dear Mike,

Thank you. I feared that that was the case. Alas, the FH7 RTF report conversion displays exhibits above the text rather than inline.

I use LibreOffice rather than Word. It’s possible to write a macro which will do the <i> conversion to italics more or less automatically. That would leave only the problem of resetting the exhibits in the text. In Word, which I used to use, I found exhibit-handling to be a fussy, exacting process, so I haven’t learned to do it in LibreOffice.

Since reading your reply I’ve done some experimenting. This may be a workaround: save the FH7 report as a PDF. Open the PDF in LibreOffice. It opens as a drawing (ODF file), but there are limited text editing capabilities which do allow for italicization, bolding, etc. That solves the narrow problem about which I posted, but for extensive text editing the workaround is probably not useful.

I hope CP does decide that this is a problem worth fixing.

Best,

Robert