On 10/10/2017 11:43 AM, Philip Ridout wrote:
As part of my pathlib refactors I've been considering how to make
things like themes and services more portable. Part of the solution
I've been working on is to make any paths relative where it makes
sense. (I.e. inside of a theme file)
Because of this I've been thinking of enhancing the way we package
themes. One of the issues I've come across is that we do not package
fonts with themes. Maybe it's a bit premature (I haven't finished my
pathlib refactors ATM) but I've been thinking about implementing this.
Although, as it's pointed out on Wikipedia embedding fonts is a bit
controversial (https://en.m.wikipedia.org/wiki/Font_embedding).
This got me thinking about Google web fonts
(https://fonts.google.com/) their about page states that all the fonts
are free and open source. Of the ones I looked at all seem to be
licenced with the Open Font licence
(https://en.m.wikipedia.org/wiki/SIL_Open_Font_License).
How would you guys feel about including these fonts with OpenLP? Maybe
packaging them as a separate download (so as not to bloat OpenLP)? Any
other thoughts?
I think that people that customize their themes changing fonts and such
should be capable of installing fonts on different machines. I don't
think OpenLP needs to sync fonts. If you start making sure (some of the)
fonts are being synced, you will run into issues with people using
"custom" fonts that you don't sync, making them wonder why it doesn't work.
About packaging: If I'm not mistaken debian doesn't like you to include
"common" things in your package. I'm not sure if that would complicate
the packaging process...
My solution would be to include fonts in a theming section in the docs
and tell people where they can get nice fonts, and that they should make
sure to install them on all their machines using OpenLP
_______________________________________________
openlp-dev mailing list
[email protected]
https://lists.openlp.io/mailman/listinfo/openlp-dev
