{"id":9752,"date":"2020-06-13T15:43:41","date_gmt":"2020-06-13T15:43:41","guid":{"rendered":"https:\/\/fhug.org.uk\/kb\/?post_type=kb_article&p=9752"},"modified":"2024-02-17T16:29:48","modified_gmt":"2024-02-17T16:29:48","slug":"tabulate-multiline-text-in-records-and-reports","status":"publish","type":"kb_article","link":"https:\/\/www.fhug.org.uk\/kb\/kb-article\/tabulate-multiline-text-in-records-and-reports\/","title":{"rendered":"Tabulate Multiline Text in Records and Reports"},"content":{"rendered":"

Introduction<\/h2>\n

Important note<\/strong>: As of Family Historian\u00a0 V7, this article is redundant, as V7 supports formatting and tables in Notes.<\/p>\n

\n

The multiline text fields, which include Address<\/em>, Note<\/em>, and Text From Source<\/em>, do not support any text formatting other than preset left tab stops. Font styles such as Bold<\/strong>, Italic<\/em>, Underline<\/span>, font face, point size, or adjustable tab settings, as in a basic word-processor, are not available.<\/p>\n

This poses a number of problems when attempting to create text that is neatly presented in both on-screen Records and printed or online web page Reports.<\/p>\n

In particular, using tab characters to tabulate Text From Source<\/em> to imitate, say a Census record form, is challenging. The tab width in Property Box fields is fixed, and does not correspond to the Tab Width<\/em> settings in Reports. Thus, tidy tabulated data in the Property Box usually results in poorly tabulated data in Reports.<\/p>\n

So here are some tips and tricks to make tabulating columns more successful.<\/p>\n<\/div>\n

Column Separators<\/h2>\n
\n

\"\"Some users avoid the tabulated column problem by using a column separator character such as COMMA (,) or BAR (|) as in Comma Separated Value (CSV) files. The benefit being that if user adjustable tab settings were introduced by Family Historian (\u0192h<\/span><\/span>), then these column separator characters could be automatically replaced by a single tab character to create tidy columns. However, in the meantime, this precludes neatly tabulated columns, looks untidy, and it is difficult to tell which text is in which column.<\/p>\n

Another snag with the default COMMA (,) separator is where any column text contains a COMMA (,) such as a place in Where Born<\/em>. One workaround is to protect such text by enclosing it in string quotes (“). Another way is to use an alternative comma as the separator, which can be created by holding down the ALT key and entering 0130<\/em> on the number keypad.<\/p>\n

\"\" To neatly tabulate a multiline text field, varying numbers of tab characters must be used in each column, depending on how much text there is in the column. When some columns have no text, it is then not clear whether multiple tab characters indicate multiple columns, or one wide column. If user adjustable tab settings were introduced by \u0192h<\/span><\/span>, then such multiple tab characters per column make it tedious to adjust to one tab per column to honour the new tab settings.<\/p>\n

\"\" A useful trick is to combine the above two approaches by using a multi-character column separator such as COMMA (,) TAB or alternatively TAB BAR (|) SPACE. Then a neat column layout can be achieved by adding extra tab characters, and yet they can be automatically removed if adjustable tab settings become available. The TAB BAR (|) SPACE alternative looks particularly neat, as it imitates the vertical column separators found on real Census forms.<\/p>\n

Ancestral Sources allows Text From Source<\/em> Auto Text Transcript<\/a> column separators to be user-defined for the Census Grid. To specify the multi-character separators suggested above, enter ,{TAB}<\/code> or {TAB}|<\/code> into the Other:<\/em> separator box of the Grid Column Separator<\/em> option.<\/p>\n<\/div>\n

Record Fields<\/h2>\n
\n

\"\"The Property Box multiline text fields may also be edited in an adjustable popup window.<\/p>\n

Unfortunately, the character size and tab settings are not quite identical in the two modes. Thus, it is occasionally necessary to add one or two extra space characters to the end of a text string, in order to obtain tidy columns in both modes.<\/p>\n<\/div>\n

Report Options<\/h2>\n
\n

If a Report includes tabulated multiline text fields, and uses the default Report Options<\/em>, then the tabulated fields are often not in neat columns. This is caused by the Font<\/em> and Tab Width<\/em> not having the same relationship as in the Property Box<\/em> fields.<\/p>\n

\"Report<\/p>\n

The solution is to adjust the Report Options<\/em> settings for the Format<\/em> tab > Section Data<\/em> > Font<\/em> and the Page Layout<\/em> tab > Tab Width<\/em> and Para. Indent<\/em>.<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

<\/div>\n

The following Font<\/em> and Tab Width<\/em> settings usually work well, providing the Tools > Preferences > Property Box<\/a> Text Font<\/em> is the default MS Sans Serif<\/em> or alternatively Arial<\/em>.

<\/div>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Format tab > Section Data<\/th>\n<\/th>\nPage Layout tab<\/th>\n<\/tr>\n
Font Name<\/th>\nFont Style<\/th>\nFont Size<\/th>\n<\/th>\nTab Width = Para. Indent<\/th>\n<\/tr>\n<\/thead>\n
Arial<\/td>\nNarrow<\/td>\n\u00a0 7 pt<\/td>\n<\/td>\n0.35\u201d<\/td>\n\u00a008.9 mm<\/td>\n<\/tr>\n
Arial<\/td>\nNarrow<\/td>\n\u00a0 8 pt<\/td>\n<\/td>\n0.40\u201d<\/td>\n\u00a010.2 mm<\/td>\n<\/tr>\n
Arial<\/td>\nRegular<\/td>\n\u00a0 8 pt<\/td>\n<\/td>\n0.49\u201d<\/td>\n\u00a012.5 mm<\/td>\n<\/tr>\n
Arial<\/td>\nRegular<\/td>\n\u00a0 9 pt<\/td>\n<\/td>\n0.54\u201d<\/td>\n\u00a013.7 mm<\/td>\n<\/tr>\n
Arial<\/td>\nRegular<\/td>\n10 pt<\/td>\n<\/td>\n0.59\u201d<\/td>\n\u00a015.0 mm<\/td>\n<\/tr>\n
MS Sans Serif<\/td>\nRegular<\/td>\n\u00a0 8 pt<\/td>\n<\/td>\n0.49\u201d<\/td>\n\u00a012.5 mm<\/td>\n<\/tr>\n
MS Sans Serif<\/td>\nRegular<\/td>\n\u00a0 9 pt<\/td>\n<\/td>\n0.54\u201d<\/td>\n\u00a013.7 mm<\/td>\n<\/tr>\n
MS Sans Serif<\/td>\nRegular<\/td>\n10 pt<\/td>\n<\/td>\n0.59\u201d<\/td>\n\u00a015.0 mm<\/td>\n<\/tr>\n
Tahoma<\/td>\nRegular<\/td>\n\u00a0 8 pt<\/td>\n<\/td>\n0.47\u201d<\/td>\n\u00a011.9 mm<\/td>\n<\/tr>\n
Tahoma<\/td>\nRegular<\/td>\n\u00a0 9 pt<\/td>\n<\/td>\n0.53\u201d<\/td>\n\u00a013.5 mm<\/td>\n<\/tr>\n
Tahoma<\/td>\nRegular<\/td>\n10 pt<\/td>\n<\/td>\n0.59\u201d<\/td>\n\u00a015.0 mm<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/div>\n

Strangely, the Times New Roman<\/em> default Reports Font<\/em> did not give consistent results with any single Tab Width<\/em> setting.<\/p>\n

The Para. Indent<\/em> must be 0\u201d<\/em> or 0 mm<\/em>, or equal the Tab Width<\/em>, because the Tab Width<\/em> steps start from the left margin.<\/p>\n

If Para. Indent<\/em> = 0\u201d<\/em> or 0 mm<\/em> the Sources<\/strong> reference numbers are rather obscured, but the characters per line is maximised.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

If Para. Indent<\/em> = Tab Width<\/em> the Sources<\/strong> reference numbers stand out more clearly, but the characters per line is reduced.<\/p>\n

\"\"<\/p>\n

Importantly, each multiline text field such as Text From Source<\/em> must start with a blank line, otherwise its first line in the Report follows on the same line as the Text From Source:<\/strong> heading, and does not align with the subsequent text.<\/p>\n

For wide tabulated data, such as the UK 1911 Census, it may also be necessary to minimise the page margins. Use Page Layout<\/em> tab > Margins<\/em> and set both Left:<\/em> and Right:<\/em> to 0.1\u201d<\/em> or 2.5 mm<\/em>. Alternatively, Orientation: Landscape<\/em> may be needed.<\/p>\n<\/div>\n","protected":false},"template":"","fh_version":[13,14,15],"skill_level":[18,17],"topic":[64,61,83],"class_list":["post-9752","kb_article","type-kb_article","status-publish","hentry","fh_version-v4","fh_version-v5","fh_version-v6","skill_level-advanced","skill_level-intermediate","topic-entering-data","topic-reports-and-books","topic-sources-and-citations"],"_links":{"self":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article\/9752","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article"}],"about":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/types\/kb_article"}],"wp:attachment":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/media?parent=9752"}],"wp:term":[{"taxonomy":"fh_version","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/fh_version?post=9752"},{"taxonomy":"skill_level","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/skill_level?post=9752"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/topic?post=9752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}