Quote:
Originally Posted by GeoffR
The current firmware has a funcion
Code:
Migration125_ReplaceMorisawaFontsSettings::migrate(Device const&, QSqlDatabase&)
which executes this SQL
Code:
UPDATE content_settings SET ReadingFontFamily='%1' WHERE ReadingFontFamily='%2';
There is another one that executes
Code:
UPDATE content_settings SET ReadingFontFamily='OpenDyslexic' WHERE ReadingFontFamily='Dyslexie';
from back when the Dyslexie font was removed. I think these must be done sometime during the upgrade process.
|
I stand corrected. The "Migration125_..." methods should be run when migrating the database to DBversion 125. I'm sure I saw a reference to Gothic or Ryumin in one of my databases after it reached 125. But, that might be an issue with the beta firmware versions if the above code wasn't in the firmware that did the rest of the migration.
Quote:
The font sizes though might be done when the book is next opened, as you say, and I guess there is nothing to prevent it continuing to use a size that is no longer available on the font size slider.
|
That's correct. The sizes are just points, so if the font and renderer can handle it, it works. I took advantage of this with the Glo at some point as the best size for me was one of the missing numbers.