Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Some work I have done #9

Closed
wants to merge 19 commits into from

3 participants

@rbmntjs

Hey,

I see I need to update my own repo, but here's a bunch of things that have been bugging me for over a year, and I never committed any of it. So there.

—r

rbmntjs and others added some commits
@rbmntjs rbmntjs Removed two points from the Æ because points are for suckahs 230c0ae
@rbmntjs rbmntjs Bottom triangle in the a was too flat, needed more of the stem, still…
… does probably
578a2cb
@rbmntjs rbmntjs Updated the kerning file, kerned a whole lot 36345d2
@rbmntjs rbmntjs Cleaning up my deal: fixed a few points, made a few curves more balan…
…ced, changed some tiny particulars. Should be more sensible, once more.
f0fa9c6
@rbmntjs rbmntjs longs_t modified slightly, much more decent curve now bc03fca
@klepas Pulling in Rob’s new changes and additions. f6430f4
@codingisacopingstrategy codingisacopingstrategy Updated font name in metadata to Open Baskerville
The font menu name in the OS is not based
on the file name, but on the font metadata.

James Puckett's working title for his revival
of Fry's Baskerville was Large Frys.
aad1e8f
@codingisacopingstrategy codingisacopingstrategy Cleaning the UFO
By roundtripping through Area51.
- Floats that want to be ints become ints
- Widthname 'normal' normalised to a field value from the
  Opentype OS/2 table usWeightClass 'Medium (Normal)'
- Placeholders for PostScript hinting data
a3fc178
@codingisacopingstrategy codingisacopingstrategy Converted (through Area51) the UFO from v1 format to v2
-Extra Opentype metadata fields in fontinfo.plist
-PostScript Hint information now moved to fontinfo.plist
-OpenType features in their own file
89511d5
@codingisacopingstrategy codingisacopingstrategy added metadata 2be52ec
@codingisacopingstrategy codingisacopingstrategy Remove stray carons, fixes #3, line height
We had problems with excessive line-height in FontForge generated OTF’s. Big
thanks to Khaled Hosney: he pointed out in a discussion on fontforge-devel
that some of the characters had accents way above their normal positions. This
was causing the seemingly superfluous linespace.

The problem manifests itself in alternate versions of the Scaron, scaron,
Zcaron and zcaron glyphs. They were removed.

bug: http://openbaskerville.lighthouseapp.com/projects/24633/tickets/3-excessive-line-height#ticket-3-5
discussion: http://sourceforge.net/mailarchive/forum.php?thread_name=6D03471D-AADA-4071-837C-12F060810309%40authoritism.net&forum_name=fontforge-devel
eb03f85
@codingisacopingstrategy codingisacopingstrategy Remove other extraneous accented glyps
For accented glyphs as acute.glif there exist alternative versions
aacute_001.glif, acute_002.glif.

The versions without the suffix are the ones mapped to a unicode point, and
the ones actually used by applications. The alternative versions differ in
their exact placement of the accent.

Since having multiple variants is confusing, I’m deleting them. If you want,
you could look at these glyphs in the history and see if their accent
positions look better than those in the standard glyphs. If so, you can copy
over the coordinates to the standard glyphs.
513ea36
@codingisacopingstrategy codingisacopingstrategy ♪ Build-scripts and a Rakefile
Now you can compile a font! Works with both FontForge and the Adobe Font
Development Kit for OpenType. The former is what we aim for as our main
compiler, as the latter is closed-source, but to have both is great for
testing the UFO spec.

Run ''rake'' to generate the font. ''rake diagnostics'' will give you an
overview of your current build environment and advise you how to proceed if it
can’t find the right build tools.

If you want more control you can use tools/ufo2otf.py which provides a command
line interface: you can choose input and output files, and which compiler to
use.
27a9d4b
@codingisacopingstrategy codingisacopingstrategy Programatically generate FONTLOG.txt
Via ''rake fontlog''

The FONTLOG is SIL’s concept of a chancelog for a font. When doing a release,
we generate one automatically based on AUTHORS.txt, README.txt and the
repository history.
071d0b4
@codingisacopingstrategy codingisacopingstrategy 'rake install' installs the font
Or rather, any otf file found in the folder. I had to remove generating
OpenBaskerville.otf as a dependency, since it can conflict with the upcoming
'generate release' task. I should probably look into rake namespacing.

In the metadata, removed entries related to FOND resources, I am not sure if
they are actually useful, and they could cause conflicts when installing
multiple Open Baskervilles.
4766f56
@codingisacopingstrategy codingisacopingstrategy 'rake release' creates font with generated version number ♫
When a designer uses a font, it is critical that she or he can identify the
particular version unambigously. We also want to make sure that designers can
use our development snapshots. That’s why for every commit there needs to be a
potential version number. We could, theoretically, use git hashes as
identifiers. However, they look cryptic to end users, and they don’t provide
information about the chronology of versions.

Taking cues from the semver.org spec, our version number takes a form X.Y.Z.,
where X is the major version, Y the minor version, and Z the patch version.
Minor versions have a defined set of goals, and get tagged in Git, we started
with 0.0.0 and we are now working towards 0.1.0.

Our patch versions, are built from the source tree after each commit. So from
the first commit after 0.1.0 we can build 0.1.1.

To do a release, we use the ''git describe'' command to tell us the last tag
and the number of commits since that tag, whereupon we base a version number
that we bake into the ufo and thus into the generated font.
c01c110
@rbmntjs rbmntjs .gitignore updated for meta-files 9cb37fa
@rbmntjs rbmntjs Fixed some youthful mistakes, tweaked a few curves. 4d409c9
@rbmntjs rbmntjs In sync with klepas 733d52b
@codingisacopingstrategy

Somehow our paths had diverged, but I git cherry-picked my way through this!

( I think you need to reclone the klepas repo )

takk!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 28, 2009
  1. @rbmntjs
Commits on Mar 6, 2009
  1. @rbmntjs
  2. @rbmntjs
Commits on Apr 30, 2009
  1. @rbmntjs

    Cleaning up my deal: fixed a few points, made a few curves more balan…

    rbmntjs authored
    …ced, changed some tiny particulars. Should be more sensible, once more.
  2. @rbmntjs
Commits on Jul 29, 2011
  1. @rbmntjs

    Pulling in Rob’s new changes and additions.

    authored rbmntjs committed
  2. @codingisacopingstrategy @rbmntjs

    Updated font name in metadata to Open Baskerville

    codingisacopingstrategy authored rbmntjs committed
    The font menu name in the OS is not based
    on the file name, but on the font metadata.
    
    James Puckett's working title for his revival
    of Fry's Baskerville was Large Frys.
  3. @codingisacopingstrategy @rbmntjs

    Cleaning the UFO

    codingisacopingstrategy authored rbmntjs committed
    By roundtripping through Area51.
    - Floats that want to be ints become ints
    - Widthname 'normal' normalised to a field value from the
      Opentype OS/2 table usWeightClass 'Medium (Normal)'
    - Placeholders for PostScript hinting data
  4. @codingisacopingstrategy @rbmntjs

    Converted (through Area51) the UFO from v1 format to v2

    codingisacopingstrategy authored rbmntjs committed
    -Extra Opentype metadata fields in fontinfo.plist
    -PostScript Hint information now moved to fontinfo.plist
    -OpenType features in their own file
  5. @codingisacopingstrategy @rbmntjs

    added metadata

    codingisacopingstrategy authored rbmntjs committed
  6. @codingisacopingstrategy @rbmntjs

    Remove stray carons, fixes #3, line height

    codingisacopingstrategy authored rbmntjs committed
    We had problems with excessive line-height in FontForge generated OTF’s. Big
    thanks to Khaled Hosney: he pointed out in a discussion on fontforge-devel
    that some of the characters had accents way above their normal positions. This
    was causing the seemingly superfluous linespace.
    
    The problem manifests itself in alternate versions of the Scaron, scaron,
    Zcaron and zcaron glyphs. They were removed.
    
    bug: http://openbaskerville.lighthouseapp.com/projects/24633/tickets/3-excessive-line-height#ticket-3-5
    discussion: http://sourceforge.net/mailarchive/forum.php?thread_name=6D03471D-AADA-4071-837C-12F060810309%40authoritism.net&forum_name=fontforge-devel
  7. @codingisacopingstrategy @rbmntjs

    Remove other extraneous accented glyps

    codingisacopingstrategy authored rbmntjs committed
    For accented glyphs as acute.glif there exist alternative versions
    aacute_001.glif, acute_002.glif.
    
    The versions without the suffix are the ones mapped to a unicode point, and
    the ones actually used by applications. The alternative versions differ in
    their exact placement of the accent.
    
    Since having multiple variants is confusing, I’m deleting them. If you want,
    you could look at these glyphs in the history and see if their accent
    positions look better than those in the standard glyphs. If so, you can copy
    over the coordinates to the standard glyphs.
  8. @codingisacopingstrategy @rbmntjs

    ♪ Build-scripts and a Rakefile

    codingisacopingstrategy authored rbmntjs committed
    Now you can compile a font! Works with both FontForge and the Adobe Font
    Development Kit for OpenType. The former is what we aim for as our main
    compiler, as the latter is closed-source, but to have both is great for
    testing the UFO spec.
    
    Run ''rake'' to generate the font. ''rake diagnostics'' will give you an
    overview of your current build environment and advise you how to proceed if it
    can’t find the right build tools.
    
    If you want more control you can use tools/ufo2otf.py which provides a command
    line interface: you can choose input and output files, and which compiler to
    use.
  9. @codingisacopingstrategy @rbmntjs

    Programatically generate FONTLOG.txt

    codingisacopingstrategy authored rbmntjs committed
    Via ''rake fontlog''
    
    The FONTLOG is SIL’s concept of a chancelog for a font. When doing a release,
    we generate one automatically based on AUTHORS.txt, README.txt and the
    repository history.
  10. @codingisacopingstrategy @rbmntjs

    'rake install' installs the font

    codingisacopingstrategy authored rbmntjs committed
    Or rather, any otf file found in the folder. I had to remove generating
    OpenBaskerville.otf as a dependency, since it can conflict with the upcoming
    'generate release' task. I should probably look into rake namespacing.
    
    In the metadata, removed entries related to FOND resources, I am not sure if
    they are actually useful, and they could cause conflicts when installing
    multiple Open Baskervilles.
  11. @codingisacopingstrategy @rbmntjs

    'rake release' creates font with generated version number ♫

    codingisacopingstrategy authored rbmntjs committed
    When a designer uses a font, it is critical that she or he can identify the
    particular version unambigously. We also want to make sure that designers can
    use our development snapshots. That’s why for every commit there needs to be a
    potential version number. We could, theoretically, use git hashes as
    identifiers. However, they look cryptic to end users, and they don’t provide
    information about the chronology of versions.
    
    Taking cues from the semver.org spec, our version number takes a form X.Y.Z.,
    where X is the major version, Y the minor version, and Z the patch version.
    Minor versions have a defined set of goals, and get tagged in Git, we started
    with 0.0.0 and we are now working towards 0.1.0.
    
    Our patch versions, are built from the source tree after each commit. So from
    the first commit after 0.1.0 we can build 0.1.1.
    
    To do a release, we use the ''git describe'' command to tell us the last tag
    and the number of commits since that tag, whereupon we base a version number
    that we bake into the ufo and thus into the generated font.
Commits on Sep 19, 2011
  1. @rbmntjs
Commits on Apr 8, 2012
  1. @rbmntjs
  2. @rbmntjs

    In sync with klepas

    rbmntjs authored
Something went wrong with that request. Please try again.