Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

Building fonts on OS X has name collision issue #55

Open
ghost opened this issue Jun 12, 2015 · 2 comments
Open

Building fonts on OS X has name collision issue #55

ghost opened this issue Jun 12, 2015 · 2 comments

Comments

@ghost
Copy link

ghost commented Jun 12, 2015

Due to the glif default file naming scheme in Robofab glyphs like 'LJ' and 'Lj' are overwritten by one another. The UFO, OTF and TTF generated only have one of 'LJ' and 'Lj' or 'NJ' and 'Nj' instead of both in both pairs, or makeotf fails to produce them because of a key error.

We made a pull request to address the issue in robofab: robofab-developers/robofab#35
Another fix would be to use uninames for those glyphs.

@rsms
Copy link

rsms commented Dec 3, 2016

I'm using macOS as well and have found this work-around:

  • Using Disk Utility, create a new sparse disk image
  • Because of a bug in Disk Utility on macOS 10.11, even if you select "case-sensitive" during creation, a case-_in_sensitive partition is created, so
  • Select the new partition in the left sidebar of Disk Utility and select the "Erase" toolbar option
  • Choose OS X Extended (Case-sensitive, Journaled)
  • in your roboto directory, remove any out folder and ln -s /Volumes/my-disk-image out
  • make in roboto dir

@veryhappythings
Copy link

You can also build this with docker - here's the file I used:

FROM python:2.7

RUN mkdir /src
COPY . /src
WORKDIR /src

RUN pip install -r requirements.txt
RUN make

You can then docker build..., docker create..., and docker cp... the resulting files off the container as demonstrated in https://medium.com/@alexeiled/docker-pattern-the-build-container-b0d0e86ad601

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants