JohnAustinDev / xulsword

Automatically exported from code.google.com/p/xulsword
17 stars 6 forks source link

Font sizes - should be a per module option - not global #208

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Display two Windows:
e.g.

KJV and FarHezareNoh (the latter is now in the CrossWire Main repo).

The Farsi font is far too small when xulsword has default Normal font (3).

Selecting Largest font (5) makes the KJV display text which is too large, yet 
the Farsi is only just becoming legible.

Furthermore, the fact that font size applies to the UI as well as the Bible 
text display is not a desirable coupling. IMHO, the UI font size should be a 
separate user preference.

Original issue reported on code.google.com by DFH...@gmail.com on 18 Jan 2013 at 8:49

GoogleCodeExporter commented 9 years ago
Screenshots are attached.

Original comment by DFH...@gmail.com on 18 Jan 2013 at 8:50

Attachments:

GoogleCodeExporter commented 9 years ago
cf. In the Xiphos front-end, fonts are a per module option.
This provides greater flexibility for the legible display of different scripts.

Original comment by DFH...@gmail.com on 18 Jan 2013 at 8:52

GoogleCodeExporter commented 9 years ago

Original comment by gpl.prog...@gmail.com on 4 Jun 2013 at 7:53

GoogleCodeExporter commented 9 years ago
In 3.6 the Options->Font size now only effects the text and popups and not the 
rest of the UI.

Module specific font sizes can now be set by right clicking a module tab and 
choosing "about", then click "more", then click "edit", then add something like 
"FontSizeAdjust=0.8" to the .conf file, then click save. Xulsword will need a 
restart to see the new font size.

This new .conf editing feature allows some nice debugging and testing of 
modules too, by the way.

Original comment by gpl.prog...@gmail.com on 5 Jun 2013 at 10:12

GoogleCodeExporter commented 9 years ago
Not entirely happy with installed .conf editing.

Would be preferable to have an ancillary .conf file under user control for the 
module, and leave the installed .conf untouched.

That way would preserve user changes even after a module is updated or just 
re-installed.

David

Original comment by DFH...@gmail.com on 5 Jun 2013 at 11:36

GoogleCodeExporter commented 9 years ago
I agree- font style/choice is now a high priority issue even though it will 
likely require a UI update (the most difficult kind of update is a UI update- 
getting 14 good translations of even the simplest phrases is daunting).

Conf file editing is more for debugging and experimenting and it probably 
doesn't make sense to take it further with a persistent change feature.

Original comment by gpl.prog...@gmail.com on 10 Oct 2013 at 5:04