Re: [fontforge-devel] UFO Filename Handling
Philippe Cochy <[email protected]> Thu, 27 Dec 2018 15:26:41 +0100
| Newsgroups | gmane.comp.fonts.fontforge.user,gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============8092238106351519858== Content-Type: multipart/alternative; boundary="=-EmsN7nPrHOIIDNGHLfya" --=-EmsN7nPrHOIIDNGHLfya Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit To be clear, I think UFO2 support does not make sense. Le jeudi 27 décembre 2018 à 07:40 +0100, Philippe Cochy a écrit : > Hello Frank. > A UFO 3 file is a de facto standard, known by the tools. A UFO file 3 > is understandable and easily modifiable, for example using a user > script. These two characteristics open FF, keeping it alive.Hell is > hiding in the details. Its details are the missing feature bricks in > the FF implementation. UFO 2 is part of this hell. > Regards, φLe mercredi 26 décembre 2018 à 19:58 -0600, Frank > Trampe a écrit : > > Hello. > > We are working hard to get the 2018 release of FontForge done > > before the end of the year. There is one proposed change that seems > > to require feedback and general approval from the user community. > > > > The adoption of UFO 3 has finally both allowed and compelled us to > > make a clean break between UFO 2 and UFO 3 and to fully implement > > UFO 3 extensions, which marks a big change from the jumbled common > > denominator output that we have been using up to this point. > > Because of the way the scripting interfaces work, the only way to > > differentiate UFO 2 from UFO 3 on output is via the directory name > > extension. One of the two cannot end in ".ufo". The least > > disruptive change would be to keep ".ufo" for UFO 2 and to use > > ".ufo3" for UFO 3. However, given the widespread adoption of UFO 3 > > and the limitations of UFO 2, there would be a lot of upsides to > > taking the reverse approach, using ".ufo" for UFO 3 and ".ufo2" for > > UFO 2. I would like to pursue this path if it doesn't create any > > particularly difficult problems for our users. > > > > I would appreciate feedback on this proposal. > > > > Best wishes, > > > > Frank > > > > > > > > _______________________________________________ > > fontforge-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/fontforge-devel > > http://fontforge.10959.n7.nabble.com/Developer-f3.html --=-EmsN7nPrHOIIDNGHLfya Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html><head></head><body><div>To be clear, I think UFO2 support does not ma= ke sense.</div><div><br></div><div>Le jeudi 27 d=C3=A9cembre 2018 =C3=A0 07= :40 +0100, Philippe Cochy a =C3=A9crit :</div><blockquote type=3D"cite= "><div>Hello Frank.</div><div><br></div><div>A UFO 3 file is a de facto sta= ndard, known by the tools. A UFO file 3 is understandable and easily modifi= able, for example using a user script. These two characteristics open FF, k= eeping it alive.</div><div>Hell is hiding in the details. Its details are t= he missing feature bricks in the FF implementation. UFO 2 is part of this h= ell.</div><div><br></div><div>Regards,</div><div> =CF=86</div><div>Le mercr= edi 26 d=C3=A9cembre 2018 =C3=A0 19:58 -0600, Frank Trampe a =C3=A9crit&nbs= p;:</div><blockquote type=3D"cite"><div dir=3D"ltr">Hello.<div><br></div><d= iv>We are working hard to get the 2018 release of FontForge done before the= end of the year. There is one proposed change that seems to require feedba= ck and general approval from the user community.</div><div><br></div><div>T= he adoption of UFO 3 has finally both allowed and compelled us to make a cl= ean break between UFO 2 and UFO 3 and to fully implement UFO 3 extensions, = which marks a big change from the jumbled common denominator output that we= have been using up to this point. Because of the way the scripting interfa= ces work, the only way to differentiate UFO 2 from UFO 3 on output is via t= he directory name extension. One of the two cannot end in ".ufo". The least= disruptive change would be to keep ".ufo" for UFO 2 and to use ".ufo3" for= UFO 3. However, given the widespread adoption of UFO 3 and the limitations= of UFO 2, there would be a lot of upsides to taking the reverse approach, = using ".ufo" for UFO 3 and ".ufo2" for UFO 2. I would like to pursue this p= ath if it doesn't create any particularly difficult problems for our users.= </div><div><br></div><div>I would appreciate feedback on this proposal.</di= v><div><br></div><div>Best wishes,</div><div><br></div><div>Frank</div><div= ><br></div></div> <pre>_______________________________________________ fontforge-devel mailing list <a href=3D"mailto:[email protected]">fontforge-devel@li= sts.sourceforge.net</a> <a href=3D"https://lists.sourceforge.net/lists/listinfo/fontforge-devel">ht= tps://lists.sourceforge.net/lists/listinfo/fontforge-devel</a> <a href=3D"http://fontforge.10959.n7.nabble.com/Developer-f3.html">http://f= ontforge.10959.n7.nabble.com/Developer-f3.html</a> </pre></blockquote></blockquote></body></html> --=-EmsN7nPrHOIIDNGHLfya-- --===============8092238106351519858== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============8092238106351519858== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ fontforge-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fontforge-users http://fontforge.10959.n7.nabble.com/User-f8781.html --===============8092238106351519858==--