* Diagrams - text alignment

[wulliam]

My laptop recently started misbehaving - the first sign of it was the printer driver being 'generic/text only' which caused issues with printing, but at the same time FH7 diagrams also went wrong. I've downloaded and installed the latest Windows 11 update, which has sorted the printer driver issue nicely, but I'm still seeing the text in FH7 diagrams all spread out like this:

Untitled.png (57.13 KiB) Viewed 2286 times

As you can see, the text for the birth record is set to be left-justified, but it isn't.

Can you help identify what I need to do to get my diagrams looking like this again:

Untitled1.png (26.11 KiB) Viewed 2286 times

Many thanks,

[tatewise]

With a Diagram displayed, try File > Print Setup... and set the printer Name to Family Historian PDF.

[Gowermick]

You may want to check your printer driver, and ensure it is one supplied by your printer maker, and not a generic one supplied by Microsoft.

I’ve just had a new PC built, and the new Windows10 installation, assigned one of Microsoft’s generic drivers to my Brother printer. It was a disaster, and all my prints were shrunk and printed sideways, despite all the settings set otherwise.

At my wits end, I downloaded and installed the latest Brother driver, which solved the problem, and printing was back to normal.

May be worth a check

[wulliam]

With a Diagram displayed, try File > Print Setup... and set the printer Name to Family Historian PDF.

Thanks Mike, but this was the result!....

Untitled.png (14.43 KiB) Viewed 2255 times

[wulliam]

You may want to check your printer driver, and ensure it is one supplied by your printer maker, and not a generic one supplied by Microsoft.

Thanks Mike - that's worked a treat. First time I've ever tried that process, but all is good.

Many thanks to both Mikes for the suggestions

[sbell95]

@William, any chance of sharing your diagram scheme? I love how simple and clean it is!

[tatewise]

@wulliam: I don't know if it is a quirk of the font you use but all the ones (1) look like a capital I (I).
e.g. I0 Aug I908

[wulliam]

@wulliam: I don't know if it is a quirk of the font you use but all the ones (1) look like a capital I (I).
e.g. I0 Aug I908

I know - it's Centaur. It's the only downside of a lovely font, but I'm sticking with it for the time being.

[wulliam]

@William, any chance of sharing your diagram scheme? I love how simple and clean it is!

Thanks Sarah,

Following the advice from Mike Tate below, I've attached the text scheme - please adapt it as you wish.
Hope it's useful to you.

_RTResearch.fht

(76.25 KiB) Downloaded 59 times

[tatewise]

To fix those commas and simplify the templates try using the FH V7 =FactText(...) new function.
e.g.
=FactText(%INDI.BIRT%,"CS","E_Born: _, _")
and
=FactText(%INDI.BAPM%,"CS","E_Bapt: _, _")
and so on...

Regarding Census sources, wouldn't it be easier to test the Census Events exist such as %INDI.CENS[year=1841]%
e.g.
=ExistsText(%INDI.CENS[year=1841]%,"'41")
or if you need to test the source exists too
=TextIf(ContainsText(%INDI.CENS[year=1841].SOUR>TITL%,"Census 1841",STD),"'41",)

You can also attach the custom Text Scheme (.fht) file directly to your posting ATTACHMENTS tab.
Use File > Import/Export > Export > Diagram Text Scheme... to obtain the file.

[wulliam]

Thanks Mike,

I didn't know of that new FH7 function - very neat.

I don't use Ancestral Sources, and just add my own generic sources for each document I come across. I distinguish between types of source by looking at the title. So, as far as I understand it, what I'm doing now is the only way to go. If Calico Pie would allow a looping index to the Name field then it'd be easier.

I've edited my rambly post to Sarah and attached the text scheme as you suggest.

Thanks again!

[tatewise]

@wulliam: When you find a Census source document I would expect you to add a standard Census Event to each person named in the Census. Do you not do that? It is nothing to do with AS but is simply a popular practice.

Theoretically, the looping index should work as it is only available for Text Schemes.
However, you are correct that it does not work in that context. Have you reported that problem to CP?
It would also be useful in other contexts too.

[wulliam]

No, for anything I find (including census documents), I create a separate source, and then add a citation to the relevant fields. I daresay it's not normal practice, but it works for me, and it would be too much work to change thousands of previous entries.

I'll report the looping index issue to CP now.

[tatewise]

@wulliam: Creating a separate Source for each document you find is perfectly normal.
However, it is not clear to me what you consider as "the relevant fields" for the citations.
e.g. What are "the relevant fields" for the citations of Birth, Marriage & Death Certificates and in particular Census records?

@Sarah: Since the Text Scheme posted by wulliam relies on his particular citation techniques it may not work for you.
The Birth, Baptism, Marriage, Death & Burial facts should be OK, and very similar to the standard FH V7 items.
However, the Census items are probably not OK, and will need customising to your techniques.

[wulliam]

Birth certificates: I cite the source in the name field and birth field for the individual who was born. The father (and mother, where named) get the same source cited in their name fields.
I do the same for the name field and death field for death certificates, and similar for marriage certificates, and parish registers.

A census source is cited in each individual's name field, and also approximate year/place of birth if I have nothing better.

Basically, a source is cited in any field for which it provides evidence.

I'm quite happy with what I'm doing!

[Gowermick]

Wulliam,
You are not alone, I too cite a source for every fact it refers to.

e.g. Census Source is cited for Name, Age, Birthdate & Birth Place, Place & Address of Houshold, and Occupation.

[tatewise]

Mike, presumably to cite Age and Place & Address of Household you use a Census Event to hold those details?
William appears not to use Census Events.
So he cannot use the simple expression =ExistsText(%INDI.CENS[year=1841]%,"'41") which is what we were discussing.