* Font standardisation

[RogerF]

First, sorry if this has been raised before -- if so, I couldn't find it. I'm perplexed about the FH use of fonts. Basically, I would expect a consistent font family to be used across the entire online interface, with some possible choice over sizes. Printed reports might value from using a different family, but... basically, that's it. There should be one place to select the default online font, and one for reports, across the entire program. I find this a bit hard to reconcile with what I'm seeing. Specifically, my Focus Window settings appear to be Arial and M/S sans serif (neither if which I'd ever choose), while other windows default to Tahoma (ditto). Why can't I just select Verdana (my online font of choice) in one place?

[tatewise]

Roger, a similar topic was raised by me during the FH V6 Beta testing, but those topics are only visible to Beta Testers so I have reproduced it here:

Problems with UTF-8 Character Displays

The support for UTF-8 is a great step forward.
However, few character Fonts support all the same codes.

The problem is that FH has so many default Fonts that it is easy to enter UTF-8 characters in one window that are displayed incorrectly in another window.
(When only ANSI CP 1252 characters were allowed there was no problem as all Fonts supported them all.)
e.g.
The Property Box, Records Window & Query Window use Tahoma.
The Focus Window uses mostly Microsoft Sans Serif and some Arial.
The Diagrams default to Arial.
The Reports default to Times New Roman.

Changing all these to one Font that supports a required character set is a pain.
All except Times New Roman are Sans Serif fonts, so why not plump for just one?

One overriding Preference to alter all the defaults to one Font would solve the problem.

If you want an example from many, then use the Property Box tool to open the Character Map.
By default this opens with your Windows Font usually Segoe UI Light which is different from any FH Fonts.
In any case select any Segoe UI Font, scroll right to the bottom, and select & copy some of the white digits in a black circle.
These are NOT faithfully reproduced in any FH Fonts.

It was suggested that Tahoma would be a good default font, because it supports more Unicode characters than most others, and is a font that most clearly distinguishes between numeral 1, upper-case I, and lower-case l.

If Tahoma was also the default Font in Reports (at least for the Section Data) then it would help with columnar tabulated text.
See how_to:tabulate_multiline_text_in_records_and_reports|> Tabulate Multiline Text in Records and Reports under Report Options.