On Sun, 19 May 2019 13:34:54 +0200 Pascal Obry <pas...@obry.net> wrote:
> And let me add that there is no Roboto issue at all. > > 1. the default theme does not use it > > 2. the elegant theme use it as first proposal but there is many other > fallbacks. If none found the system font will be picked. > > 3. fact is that Gtk has a but and select either Roboto if found and if > not the system font. The fallback are not propoerly checked. This bug > has been fixed and will be in next minor release IIRC. What bug? I don't quite get this point > > So at the end Roboto is not mandatory even on elegant theme so all this > is a non issue. That's not the impression I got from every response about elegant theme - basically each time it was said that you have to install Roboto, because elegant theme was designed for it. And you still haven't answered how custom user themes would work. Or is there no plan to support custom themes and we will only allow themes included with dt itself? That seems to unnecessary limit usefulness of the whole theming refactoring IMHO. For me as macOS packager there's actually no difference in how we answer that last question, because I still have to find a way to allow dt to use a non-system font - I'm not planning to install anything system-wide (aside that I don't like that idea, it's just not possible with DMG package format anyway and I have no plans to switch to other packaging options). Or of course I can just take your word that there's no Roboto problem and just ignore it altogether, so that elegant theme will use available system fonts. I'm not sure what is the plan with Windows package. Last note - bundling data like font is not the same as bundling libraries - most arguments against bundling code just doesn't work if you try to apply them to this situation. ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
