30 June 2016. Bangalore, India.1. Admina. We had a 2-hour hangout today where we discussed everyone's 'Raisin' decks and production workflows.2. Productiona. Character Sets:
I worked on determining how many characters/glyphs in the entire character set are either 'drawn', 'composites', or 'either' (depending on the context, these could be either outlines or composites). I created a 'README.md' file containing a brief summary of the data I collected which Dave incorporated directly into the readme file for the 'GF 2016 Glyph Sets' sub-directory (found here <https://github.com/google/fonts/blob/master/tools/encodings/GF%202016%20Glyph%20Sets/README.md>).
2. Next Stepsa. Start the next sprint to expanding Vernon Adams' 'Bevan' typeface.b. Ask Dave about hosting Vernon's projects on 'https://github.com/googlefonts'c. Some questions for the team with regards to the character set.* Should we add 0x02BC (apostrophemod) to the Plus set since it's used in 'napostrophe'. We have included it the Pro set.* Not all fonts require '.case' alternates of the below marks (dotbelowcomb.case, dieresisbelowcomb.case, commaaccentcomb.case, cedillacomb.case, ogonekcomb.case, brevebelowcomb.case, macronbelowcomb.case). Maybe we make them optional but keep them in the Plus set and make a note somwhere of it.* Similarly not all fonts require 'zero.zero' (slashed zero). While this may be obvious I think we should document it somewhere (maybe in the Wiki feature on GitHub?).
b. @Alexei - I realised that since we've included the Unicode fractions ¼ (0x00BC) and ¾ (0x00BE) in the Plus set, it would be useful to include the 'foursuperior' character (0x2074) which is already included in most fonts because it is used as a component in the fractions. :|
Dave, are you OK if I expand it to GF Plus ?
Thanks Kalapi. I recommend using a sharp spike rather than a rectangle so that even a few pax of clipping is easily visible.
Hi Kalapi,
Welcome back (to our humble show)!
Number 3 is definitely too tight.
Does Glyphs calculate the metrics as you propose automatically, or is there need to add custom hhea and winAscent parameters to each instance?
--
You received this message because you are subscribed to a topic in the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/googlefonts-discuss/W4PHxnLk3JY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
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/f1984957-21d4-4954-a1ff-97ebd0146650%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Number 3 is definitely too tight.
Does Glyphs calculate the metrics as you propose automatically, or is there need to add custom hhea and winAscent parameters to each instance?
There seem to be missing from your analysis (a) linegap values and (b) this "all ink within 125% of UPM" rule that Pablo and Eben have proposed.
On Wed, Jul 20, 2016 at 01:33:41PM -0400, Dave Crossland wrote:
> Hi Khaled
>
> There seem to be missing from your analysis (a) linegap values and (b) this
> "all ink within 125% of UPM" rule that Pablo and Eben have proposed.
I always set line gap to zero and just forget about it, but others might
have different preferences.
> Is there any yet any program that will calculate the max bbox from
> stacking?
I don’t know any.
> But perhaps we could account for the combinations specified by OpenType
> layout?
I was just thinking about a way to automate this the other day (it is a
common issue in Arabic since combining marks are always placed during
layout with no recomposed forms, so the font bbox does not account for
them). I think we can either have some text with common combinations,
pass it though HarfBuzz and calculate the maximum ink box of the text
after layout, or try to generate possible combinations from the layout
tables and do the above.
The old rule was 125% of the UPM but at least with *browsers* the last time I did a check this limit was no longer in effect.
I would be happy to re-test or to provide my test fonts to others to run tests. I am not 100% sure what timeline I can offer
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/409B54AB-44A2-42C6-A944-77FF8216BAAC%40eyebytes.com.
Hi kalapi
Since nhung is out this week please could you ensure all the fonts you worked on so far are completed to their appropriate glyphs sets, and test the v metrics as described above, and then we can sync up in about 11 hours from now :)
If you manage to do all that, and be grateful if you could take a close look at fontbakery and get it running on 1 or more of your completed font projects :)
Cheers
Dave