Version requirements about mtheme HOT 8 CLOSED

Do they only change the file name and append OT or is it also part of the family name (you could check with gnome-font-viewer or a similar application?). If it's the latter, it will be a pain to support this in a cross-platform manner. About the extra light version, yes that came with 3.1.

But anyway, what am I supposed to do? Mentioning the requirements in the README.md?

P.S.: Every time I check your blog, there's something interesting. But I forget about it soon (I am old …) because you do not have an RSS feed (I am old …) ;-)

from mtheme.

It's part of the family name, they just appended OT for no obvious reason.

That was the intention - just mention that Fira might be called Fira OT on different platforms.

I already filed a bug for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1160371

from mtheme.

I will keep this open. if time allows, I will make a package option that allows to load a different or disable to load the "Fira Sans"-based font theme.

from mtheme.

Just for the record, as soon as this mozilla-fira-fonts package update goes from testing to updates the issue will be resolved for Fedora 20.

from mtheme.

Wouldn't it be nice to have the font configurable? I mean, Fira Sans is pretty okay, but what if I'd like to have a different font?

from mtheme.

Hi, yes indeed it would be preferable and I will provide this if time allows (actually, half the work is done by splitting the font definition into its own style file). In any case, you can already override the font by using \setsansfont and friends after loading the package.

from mtheme.

I just wonder how to install the Fira fonts to other-than-linux machine to be used by mtheme. Running a beamer document with mtheme with xelatex stops when it does not find "Fira Sans Lig.cfg" file. The https://github.com/mozilla/Fira does not have this .cfg file.

from mtheme.

I cannot help you with that particular problem but will add any information to the README if you find a solution.

from mtheme.