I've hit a roadblock / mental exhaustion from dealing with (banging my head against) the Inkscape codebase, so I think it is very much wiser to switch gears at the moment and do some FontBakery work again for a while. And possibly get back to Inkscape later for a fresh restart. I'll take a look now at what's pending on the issue tracker for FontBakery that may be safe to work on regardless of Lasse's upcoming PR.
Last week I should have met with Tav on a chat channel (possibly IRC) but we ended up not being able to arrange a good time for that yet. So I'm still going to get some feedback/advice from him at some point in the future.
ScislaC (Josh Andler) on Inkscape IRC told me that not much people touched the text-handling code in the past decade and that Tav is probably the person who best knows it nowadays. So talking to him will probably be very good. I don't want to continue digging deeper in that code before talking to him, for instance.
I sketched a bit of each portion of the code that we need: (a) CSS attribute parsing, (b) some GTK dialog/widgets and (c) some freetype API calls for rendering the variable fonts. What I still lack is a broader overview on how all of this stitches together coherently.
The concept is not much complicated. Read coordinate values from the SVG file (as CSS attribute values), populate the UI of a dialog with sliders, and then use that info when creating font instances. Then use those values also to setup the appropriate freetype API calls. But the devil is in the details. Among this, there's a whole labyrinth of code for CSS and text handling...
Felipe Sanches
2017-06-13 9:37 GMT-03:00 Felipe Sanches <juca@...2270...>:
Cool!
I would just avoid using the term "palette" because I recently learned that the term "font-palette" is used in the CSS spec for something else (relating to color palettes in coloured font faces).
As can be seen here: https://drafts.csswg.org/css-fonts-4/#font-palette-prop
2017-06-13 9:20 GMT-03:00 Dave Crossland <dave@...1555...>:
On Jun 5, 2017 4:57 PM, "Felipe Sanches" <juca@...2270...> wrote:
There may be occasions when the user may want to modify the design-space coordinates of a given variable font globally on the document. Do you think this is a valid concern / valid usage scenario ?
I think you should postpone this for now and consider it a future possible milestone.
In that case, a variable font instance may behave like a shared resource, analogous to a shared gradient or filter-effect. But then we would need to make this an explicit user-choice, perhaps by providing a dedicated dialog for setting up such shared font resources. Like a "palette of font instances". Does it make sense ?
Yes, more sophisticated typesetting environments have "character styles" and "paragraph styles" which are such palettes and afaik inkscape doesn't have a UI for that.
Cheers Dave
-- You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsubscribe@...3168... To post to this group, send email to googlefonts-discuss@...3168... Visit this group at https://groups.google.com/group/googlefonts-discuss. To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/CAEozd0yg2SeYO00d9Mq7p....
For more options, visit https://groups.google.com/d/optout.