Tracking original font icon sources in Fluid projects

[Colin Clark]

Hi Jon,

I think it makes a lot of sense. I agree with you that whatever we need to make the modification of an icon font "from source" easy and reproducible should be stored in our repository if possible.

Colin

> On Jan 13, 2016, at 11:02 AM, Hung, Jonathan <jhung at ocadu.ca> wrote:
> 
> For the past few years, we have been using IcoMoon to generate custom icon fonts which we use in various Fluid projects. When making our icon fonts, IcoMoon generates a ZIP file which includes:
> 
> the font binaries (TTF, WOFF, and EOT font files)
> SVG files which were used to make the glyphs in the font
> selection.json file which includes metadata used by IcoMoon to make the font.
> a demo.html file with CSS
> 
> In our repositories, we only track the font binaries - which creates an issue if we ever want to modify the font. In order to modify the font, we will need the SVG files so we can edit the glyph, and the selection.json file.
> 
> I’m wondering if we should start tracking the SVG and the selection.json files within a ./font/source/ directory in our projects. This way anyone can add and modify the font set easily. We should also add a README file in that directory explaining its usage as well.
> 
> Thoughts? Yays or nays?
> 
> - Jon.
> 
> 
> Jonathan Hung
> Inclusive Designer
> Inclusive Design Research Centre
> OCAD University
> www.idrc.ocadu.ca <http://www.idrc.ocadu.ca/>
> www.ocadu.ca <http://www.ocadu.ca/>
> 
> 
> 
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20160114/3330e098/attachment.htm>