Mike
Sorry if this is not the correct forum for my query.
I have used Ancestral Sources using the Census Grid for most of my Census returns and the result in reports is not good, nothing lines up in columns etc. I have followed the Report Options in Tabulate Multiline Text in Records and Reports and the 1911 Census still looks a "shambles".
If I adopt the method in your reply to jmurphy on 7 December how would you suggest I set out the information?
Any help or advice would be welcomed.
Brian
* Tabulate Multiline Text in Records and Reports
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Tabulate Multiline Text in Records and Reports
I have moved this posting from the General forum thread workflow and getting organized (10946).
There may be no perfect solution, but with patience, most Census Grid transcripts can be neatly tabulated.
In how_to:tabulate_multiline_text_in_records_and_reports|> Tabulate Multiline Text in Records and Reports there is a lot of advice.
The Column Separators section talks about the pros and cons of alternative column separator options, but Brian does not say which one he has chosen.
If it is important to future proof the columns in case FH introduces adjustable tab stop settings, then multi-character column separators such as Comma (,) Tab or alternatively Tab Bar (|) Space should be used.
To insert these retrospectively, then use the Plugin Search and Replace V2.0 to replace the current Text From Source separators.
To include Tab characters in the Search or Replace text boxes then Copy & Paste them from elsewhere.
Change the Ancestral Sources Tools > Options > Census settings > Grid Column Separator to match.
Ancestral Sources only inserts one separator per Census Grid column, and this may not result in neatly tabulated columns within the FH Text From Source field.
You will need to add Tab characters by hand in the AS Auto-Text box &/or the FH Text From Source box until the columns line up.
Sometimes a few extra space characters may also be needed to line up Text From Source columns in both the embedded Property Box view and the popup Actual Text window.
Finally and importantly for Reports every multi-line Text From Source field MUST start with a blank line otherwise it does not usually look correct.
Note that this can be automated in the Ancestral Sources Auto-Text Templates.
Use the Report Options suggested in how_to:tabulate_multiline_text_in_records_and_reports|> Tabulate Multiline Text in Records and Reports and the Report Sources layout should usually be neatly tabulated.
If the Census Grid is very wide then the Report Options > Page Layout may need adjustment to reduce Left/Right Margins and use Landscape orientation.
The next version of my Improve Website or CD DVD HTML Plugin should offer to neatly tabulate web pages including Tab separated data such as a Census Grid.
There may be no perfect solution, but with patience, most Census Grid transcripts can be neatly tabulated.
In how_to:tabulate_multiline_text_in_records_and_reports|> Tabulate Multiline Text in Records and Reports there is a lot of advice.
The Column Separators section talks about the pros and cons of alternative column separator options, but Brian does not say which one he has chosen.
If it is important to future proof the columns in case FH introduces adjustable tab stop settings, then multi-character column separators such as Comma (,) Tab or alternatively Tab Bar (|) Space should be used.
To insert these retrospectively, then use the Plugin Search and Replace V2.0 to replace the current Text From Source separators.
To include Tab characters in the Search or Replace text boxes then Copy & Paste them from elsewhere.
Change the Ancestral Sources Tools > Options > Census settings > Grid Column Separator to match.
Ancestral Sources only inserts one separator per Census Grid column, and this may not result in neatly tabulated columns within the FH Text From Source field.
You will need to add Tab characters by hand in the AS Auto-Text box &/or the FH Text From Source box until the columns line up.
Sometimes a few extra space characters may also be needed to line up Text From Source columns in both the embedded Property Box view and the popup Actual Text window.
Finally and importantly for Reports every multi-line Text From Source field MUST start with a blank line otherwise it does not usually look correct.
Note that this can be automated in the Ancestral Sources Auto-Text Templates.
Use the Report Options suggested in how_to:tabulate_multiline_text_in_records_and_reports|> Tabulate Multiline Text in Records and Reports and the Report Sources layout should usually be neatly tabulated.
If the Census Grid is very wide then the Report Options > Page Layout may need adjustment to reduce Left/Right Margins and use Landscape orientation.
The next version of my Improve Website or CD DVD HTML Plugin should offer to neatly tabulate web pages including Tab separated data such as a Census Grid.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Tabulate Multiline Text in Records and Reports
Mike
Thanks for your reply.
After trying various things I have kept my original Column Separators as TAB and run the Individual Summary Report and changed the following settings in Print Options: Format, Section Data to Arial Narrow size 8. Page Layout: Tab Width to 0.4" and Para Indent to 0".
The Census reports from 1841 to 1901 look better with minor exceptions all data line up neatly under the headings, however, I have not managed total success with the 1911 Census. The Census for 1911 still has a few people's information that does not line up properly, I think the additional columns in 1911 are the cause, but is much better than my earlier attempts.
Brian
Thanks for your reply.
After trying various things I have kept my original Column Separators as TAB and run the Individual Summary Report and changed the following settings in Print Options: Format, Section Data to Arial Narrow size 8. Page Layout: Tab Width to 0.4" and Para Indent to 0".
The Census reports from 1841 to 1901 look better with minor exceptions all data line up neatly under the headings, however, I have not managed total success with the 1911 Census. The Census for 1911 still has a few people's information that does not line up properly, I think the additional columns in 1911 are the cause, but is much better than my earlier attempts.
Brian
- tatewise
- Megastar
- Posts: 27088
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Tabulate Multiline Text in Records and Reports
I am glad you are having better success.
I found I had to experiment with the Page Layout: Tab Width to get the best match between Property Box and Report tabulated Text From Source layout.
Try either 0.39" or 0.41" to see if that helps.
You are almost certainly correct that the extra 1911 Census columns are the source of the problem.
Try setting Page Layout: Margins to Left: 0.1" and Right: 0.1" to squeeze more on the page.
Another idea is to use Format: Section Data: Arial, Narrow, Size 7 and Page Layout: Tab Width: 0.35".
Although 7 is not in the drop-down list, you can type 7 into the Size box.
I found I had to experiment with the Page Layout: Tab Width to get the best match between Property Box and Report tabulated Text From Source layout.
Try either 0.39" or 0.41" to see if that helps.
You are almost certainly correct that the extra 1911 Census columns are the source of the problem.
Try setting Page Layout: Margins to Left: 0.1" and Right: 0.1" to squeeze more on the page.
Another idea is to use Format: Section Data: Arial, Narrow, Size 7 and Page Layout: Tab Width: 0.35".
Although 7 is not in the drop-down list, you can type 7 into the Size box.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Tabulate Multiline Text in Records and Reports
Mike
Thanks for your advice and guidance with my problem, I have used all your information and now have 1911 Census reports that make sense and can be easily read.
I can now set page layout etc to accommodate all Census returns for any family group or individual, absolutely brilliant.
Brian
Thanks for your advice and guidance with my problem, I have used all your information and now have 1911 Census reports that make sense and can be easily read.
I can now set page layout etc to accommodate all Census returns for any family group or individual, absolutely brilliant.
Brian