klepas / open-baskerville Goto Github PK

Hi, including "em dash" and "en dash" would be a great improvement!

Some glyphs were already merged in from Century Catalogue:

8ae0cf1

With the following remarks:

The curly braces are too low, the lesser than greater then
signs too thin… The square brackets look about right.

The dashes should be made to match the hyphen.

The ordinal, degree, currency look about right,
as do other geometrical glyphs.

What do you think of the single and double quote?

The divide glyph is unsymmetric and needs to be fixed.

Paragraph and section might need slight restyling
to fit into Open Baskerville style.

If I look in RoboFont’s editor window, we need:

mu, onequarter, onehalf, threequarters
guillemotleft guillemotright
backslash
minus plusminus
yen
hungarumlaut
breve
macron
threesuperior onesuperior twosuperior

I suggest everyone is free to contribute missing glyphs and @rbmntjs is in charge of maintaining the overall style.

@ichosis is doing the cedille’s #3

If we manage to get all these glyphs in, and in a consistent style, at least we will have one coherent and consistent weight-albeit a weird one, our Display Baskerville! That’s MileStone 0.1.0 Then afterwards we can expand to new weights and styles!

In getting clean diffs in-between FontForge and RoboFab (RoboFont, Fontlab etcetera) based commits, FontForge has already implemented a similar pretty printing for the GLIF files (issue #5)

The remaining problem is that FontForge doesn’t keep track of the glyphname glyphfile relation as stored in glyphs/contents.plist , so that when you save the UFO file (which is generating the UFO over the old one), FontForge chooses filenames based on the glyph names and a predetermined algorithm, disregarding the existing filenames.

The algorithm being used by FontForge is the default one described in the UFO2 specs
http://unifiedfontobject.org/versions/ufo2/glyphs.html

The spec also states ‘There is no one standard glyph name to file name conversion’ and indeed the algorithm being used in the RoboFab Fontlab UFO export method is a different one.

It is called glyphNameToShortFileName
http://code.robofab.com/browser/trunk/Lib/robofab/objects/objectsFL.py#L950
The source is here:
http://code.robofab.com/browser/trunk/Lib/robofab/tools/glyphNameSchemes.py

So if a UFO is generated from Fontlab (like the initial Open Baskerville sources), and then modified in FontForge, FontForge will ignore the contents.plist and because of the differing glyph to filename conversions resave the glyphs under different filenames then in the original UFO.

When using Adobe InDesign 15, applying the font results in the forward slashes not shown. InDesign would warn and show the slash using the base font. If I force apply the font (by pressing Ctrl+Alt), glyph box would appear.

Similar to fontsquirrel.

Use fontforge scripting and ttf2woff.

Our build script requires FontForge with the Python extension. (Or alternatively, the Adobe Font Development Kit in combination with the RoboFab and UFO2FDK packages. AFDKO is closed-source and also non-trivial to install.) To make the build scripts accessible on OS X, a proper HomeBrew Formula is required.

I’ve had no luck adding the python extension to the formula:

https://github.com/mxcl/homebrew/issuesearch?state=open&q=fontforge#issue/4689

I would be very happy if someone with more experience with makefiles and distutils (the documentation is really bad, no?) could take a look at this.

In the Rakefile we use a command like

zip -r OpenBaskerville-0.0.56.zip build/OpenBaskerville-0.56

Which produces a zipfile, alright, but it includes the build folder.

How would we go about to get just the OpenBaskerville-0.0.56
folder in there?

https://github.com/klepas/open-baskerville/blob/master/Rakefile

With command line script via distutils entry points

To accept patches from FontForge users, the data needs to be formatted the same as the existing data—otherwise it becomes hard to track changes in the versioning system.

This is a Robofab generated font roundtripped through fontforge:
http://schr.fr/tlkng/ufo-roundtrip.html
There’s some more issues here but they should be addressed in separate tickets.

Robofab uses Python XML Sax which seems to work similar to Libxml2: as using Nokigiri on the ufo data works very well in maintaining the same pretty-print.

Here’s how Fontforge ideally should output the Glyph XML:

• When the curve is unsmooth, this is default, so you don’t mention it:

   <point x="424" y="489" type="curve" smooth="no"/>
   -->
   <point x="419" y="678" type="curve"/>
  

• hex value’s should be uppercase

  <unicode hex="00d6"/>
  --> 
  <unicode hex="00D6"/>
  

• outline components should be organised alphabetically:

  <component base="grave" xOffset="205" yOffset="228"/>
  <component base="O" xOffset="1"/>
  -->
  <component base="O" xOffset="1"/>
  <component base="grave" xOffset="205" yOffset="228"/>
  

Great work, gorgeous fonts, and specially, thanks for including the long s glyph, its ligatures and ct and st ligatures, no one ever did so. But one problem: Including especial characters or numbers on the font name makes it not work in XeTeX, so could you remove it please? It will be great to see "Open Baskerville" only on the font name. Thanks.

Christopher Adams notes, to make the font ideographically complete for Western Latin (which, I suppose, is our main target now), we need:

U+00c7 (Ç), U+00e7 (ç)

In fact, one would only need to make a cedille accent glyph: the two cedille glyphs can then be created by juxtaposition.

Meta

I wrote the ticket as a phrase that would fit in a ‘to do’ list—this is what would be the easiest if we want to be pulling these tickets in to the site. A heading CONTRIBUTE, and underneath little links like: ‘design the cedille’, ‘make a template for the italic’, ‘sketch the body weight’ etc.

You’d have to write a little sinatra / flask app for that that generates a javascript since we’re using static hosting on gh-pages.

So uhm, moving the tickets to Gh. Well, obviously it’s more barebones than Lighthouse. I’d miss the opportunity to upload pictures, the ability to plan milestones and the ability to leave messages.

But the large and obvious advantage is that it’s integrated with the code hosting, and people need only one account. No login required. I suppose that does make it a good idea.

d

The download link on the web page has been broken for a while. If I remember correctly, that was a current .otf link..? An alternate one would be greatly appreciated...