Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

where to upload the Fontforge .sfd files?

nitrofurano

I started to join the .glif files (only the .zip file provided from http://klepas.org/openbaskerville/ - but git didn't work) into a .sfd Fontforge file - where must be it uploaded? was that nice uploading to pastebin.com as text? (since .sfd is a text file)

And how were or must be the development and research process of this digital typeface, like how and where were those .glif files created?

anyway i had difficulties to import some .glif files into Fontforge, such as O_acute.glif - they seems to have offset values of accented character references, but i set them by 'eye' - which i don't know how appropriated it is...

in the file i'm attaching (trying in the first time here at lighthouseapp) - i don't know what must be writen as credits - please help me fixing it...

Posted by nitrofurano · February 17th, 2009 @ 10:37 PM

5 replies

  1. nitrofurano
    nitrofurano

    it misses some characters - tilde and cedilla are often used in portuguese, but i didn't want to 'invent' it - the hungarian acute there seems to be not that correct as well... - i'm also curious about how to draw all those characters didn't exist at the time this typeface were drawn, like '@', '#', etc. - also didn't find place for the ligatures 'ct', 'fj', etc.

    February 17th, 2009 @ 10:43 PM

  2. Simon Pascal Klein
    Simon Pascal Klein

    I believe the UFO glif files were created using FontLab. I think for cross-platform support using UFO might be better than FontForge’s SFD?

    Regarding changes, if you make one feel free to add your details in the AUTHORS file. I’ve also updated the Open Baskerville page* with additional information, mostly historical and also added a mini guide on using Git. I don’t mind if contributors don’t want to use it but I’ll definitely continue maintaining it merging changes manually back up (though getting into it isn’t that hard—I’m happy to help anyone who has any questions on Git and using it).

    Thank you for creating the OTF file. I might actually make it available for download on the Open Baskerville info page, and we’ll just update it to reflect new changes and additions.

    With characters that didn’t exist at the time, such as the at (@) sign or octothorp (#), I think giving it shot and discussing the result and possible improvement is probably the best method of tackling these. (:

    Thanks again for the contribution and sorry for the lack of info on Git. I hope the guide I added helps.

    *http://klepas.org/openbaskerville/

    February 20th, 2009 @ 03:54 AM

  3. nitrofurano
    nitrofurano

    I don't know, i confess i don't know what UFO is - not unregreting FontLab, but i have the oppinion of how interesting would be developing an open-source typeface using open-source tools for it as well - also for helping open-source tools development - i think Open-Baskerville can be great for it. As well, pernsonally, i have no interest on paying FontLab licence, or using it ilegally. Also because of this i'm using Fontforge instead...

    about GIT, i used a similar tool, Mercurial, for a Shoebot (Nodebox fork) documents hosted at freehg.org, but it's weird for me why the Open-Baskerville GIT access failed...

    And as i could try from FontLab demo versions, Fontforge seems to have a better support for .svg files, which can be useful on editing or creating gliphs on vector editors like Inkscape (and Adobe Illustator as well, for people who uses it) - personally i used to use .svg files to draw gliphs (just like mentioned on that tip at http://ospublish.constantvzw.org )

    As well, i added AUTHORS info, except the mail contact, for help avoiding mail spamming - there i placed the official Open-Baskerville url, and the author name in AUTHORS text document.

    You welcome! =) And as well, i did some fixes on that, like on the font info (the last version appeared as 'Regular Regular' in the font list when installed...) - (as well with a .ttf resulting file as well, similar to .otf) - but anyway, these files can be plenty of mistakes, which may needs some fixing help...

    And of course, thanks as well all http://klepas.org/openbaskerville/ updates for helping people! =)

    February 21st, 2009 @ 02:53 AM

  4. nitrofurano
    nitrofurano

    Talking about open-source tools, since Fontforge can generate .svg fonts, i converted it to a .svg Inkscape drawing, which can be imported back to Fontforge (fits fine in the ascent and descent, since the measures and vertical coordinates are the same) - this can be useful on people may want to draw new characters based on previous gliph drawings, and helping people more familiar with vector editors than typeface editors.

    February 21st, 2009 @ 05:29 PM

  5. Simon Pascal Klein
    Simon Pascal Klein

    The Inkscape → FontForge workflow is the one I’m most (if at all) accustomed to. A type student at the Royal Academy of Arts in The Hague has also added some ligatures and tilde characters, notably the Œ ligature and is working also on the commercial at sign (‘@’), which as a rather recent addition to our keyboards lacks a specimen example to even glance at.

    I’m going to pull the changes later today, so with the updated mini-howto on the Open Baskerville info page, try checking out the Git repository. If you like I can for now merge in your changes and update the repo for you from your ZIP archive.

    Cheers! (:

    February 25th, 2009 @ 03:53 AM

You must be logged in as a project member to reply.