11-02-2018, 08:27 AM | #1 |
Bookish
Posts: 889
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
|
calibre 3.33.1 [64bit] editor preferences anomaly
Trying to change in the editor preferences, for the preview window the "style for standard text" settings does not work for any of the options "sans text", "serif text" or "mono text" in calibre 64bit.
It works in the 32bit version. Perhaps a bug? |
11-02-2018, 10:50 PM | #2 |
Bibliophagist
Posts: 34,236
Karma: 144198474
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Not much consolation for you but on my Windows 10 install, I can change editor font preferences. I closed Calibre, re-opened and the preferences were still as I set them.
|
11-03-2018, 03:44 AM | #3 |
creator of calibre
Posts: 43,744
Karma: 22446736
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
works for me as well with calibre 64bit and I cant think of any reason it would work with 32bit but not 64bit -- it's a simple boolean setting stored ina json config file.
|
11-03-2018, 09:24 AM | #4 |
Bookish
Posts: 889
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
|
Strange.
I can see my selection being entered in config file "tweak_book_gui.json" for option "preview_standard_font_family":
I can change the "font family for serif text" setting, though, which is immediately shown after pressing "ok", but that is it. |
11-03-2018, 09:35 AM | #5 |
Bookish
Posts: 889
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
|
There is an option setting order difference in the 32 & 64 bit version, though (see attachments):
|
11-03-2018, 05:52 PM | #6 |
....
Posts: 1,547
Karma: 18068960
Join Date: May 2012
Device: ....
|
On the face of it mine also seems to have this problem but I think it is because I don't understand how the font selection for the preview window works. However, I have not spent much time trying to figure it out as the default Times Roman serif (or what looks like Times Roman serif) is just fine by me. So the following is not meant as an explanation but just as a lead in for someone to perhaps fully explain.
It seems to me that it works maybe something like this. If there is no font-family in the books stylesheet then the font selected in the Editor's options for the preview window are used - so the selection in the Editor's preferences appear to work. If there is a font-family: serif;, for example, in the stylesheet then the selection for serif in the Editor's preferences are used in the preview window for the serif cases in the book. So it appears to work for them. If there is a font-family: Times New Roman, serif;, for example in the stylesheet then the style in the book is used for them in the preview window instead of the font in the Editor's preferences. Now, on first blush I assumed that whatever was set in the Editor's preferences was overriding so was what one got regardless of the book's styles, and if one has that belief then it appears that if there is a font declared in the book (even if not embedded) that the Editor's preferences are not working because the Editor's style is not being applied. I hope that makes sense. As I said I just mean this as a lead in to someone giving a correct and clearer explanation by either rubbishing this or clarifying this. However, getting to the nub of the original question, if the OP is under the same belief that I was, then its appearing not to work is because the book they are editing has a font declared in the stylesheet and that takes priority. If there is no font-family in the stylesheet the Editor's preferences then "appear to work". Last edited by AnotherCat; 11-03-2018 at 05:57 PM. |
11-03-2018, 08:56 PM | #7 | |
null operator
Posts: 20,415
Karma: 25894272
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
But what's even odder is that I see sans/serif/mono (top-to-bottom) in 32, 64 and Portable editions of version 3.33.1 Weird - the 32bit and portable installs are fresh - i.e. installed today BR Last edited by BetterRed; 11-03-2018 at 09:35 PM. |
|
11-03-2018, 10:12 PM | #8 |
....
Posts: 1,547
Karma: 18068960
Join Date: May 2012
Device: ....
|
I have Sans, Serif, Mono as the order from top to bottom too in 64 bit, Windows 10.
I wonder if it was different in older Editor versions? Or between Windows and Linux? |
11-03-2018, 10:42 PM | #9 |
Well trained by Cats
Posts: 29,659
Karma: 54369090
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
BR
What got me, was the Icons are different on Portable |
11-04-2018, 01:19 AM | #10 |
creator of calibre
Posts: 43,744
Karma: 22446736
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
the order being different is unrelated and an artifact of the random order of python dictionaries, I have fixed it.
|
11-04-2018, 01:01 AM | #11 | |
null operator
Posts: 20,415
Karma: 25894272
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
My "32/64 bit installed calibre" config has Prefs->L&F->Icon theme set to classic and some icon overrides in ..\resources\images. Whereas my portable has Prefs->L&F->Icon theme set to Default icons and no overrides.
Quote:
But now I know mine eyes did in fact see the glory of a randomly ordered python dictionary I think I'll stick to the OED and Ayto's Word Origins. BR |
|
11-04-2018, 06:11 AM | #12 | |
Bookish
Posts: 889
Karma: 1803094
Join Date: Jun 2011
Device: PC, t1, t2, t3, aura 2 v1, clara HD, Libra 2, Nxtpaper 11
|
Quote:
Code:
font-family: serif; So the priority is:
And I admit, that is not what I expected My expectation is more that the editor should be able to override book settings, as the editor is supposed to make change possible. So in the end, it works as intended, but not as expected. |
|
11-04-2018, 11:00 AM | #13 |
creator of calibre
Posts: 43,744
Karma: 22446736
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
|
Those settings are for what fonts to use when the book does not define its own fonts, when *previewing* the book. It has nothing to do with editing it. There are identical settings present int he calibre viewer as well, that have identical effects.
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Moving from Calibre 32bit to Calibre 64bit | wjBLqf-_9 | Calibre | 3 | 08-31-2018 05:32 PM |
Calibre latest Update - calibre 3.2.1 64bit version | Al Adams | Library Management | 9 | 07-07-2017 07:47 PM |
2.67 - editor preferences squeezed | DrChiper | Editor | 1 | 09-08-2016 10:23 AM |
Editor (1.37 64bit) not responding | JLius | Editor | 6 | 05-23-2014 05:41 AM |
Anomaly in calibre.ebooks.metadata.book ? | Jesse Chisholm | Development | 4 | 04-28-2012 08:38 AM |