Re: [fontforge-devel] UFO Filename Handling
Philippe Cochy <[email protected]> Thu, 27 Dec 2018 07:40:58 +0100
| Newsgroups | gmane.comp.fonts.fontforge.user,gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============5595778203783657487== Content-Type: multipart/alternative; boundary="=-g26KYM9OTVJOn2z8mbcY" --=-g26KYM9OTVJOn2z8mbcY Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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 --=-g26KYM9OTVJOn2z8mbcY Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html><head></head><body><div>Hello Frank.</div><div><br></div><div>A UFO 3= file is a de facto standard, known by the tools. A UFO file 3 is understan= dable and easily modifiable, for example using a user script. These two cha= racteristics open FF, keeping it alive.</div><div>Hell is hiding in the det= ails. Its details are the missing feature bricks in the FF implementation. = UFO 2 is part of this hell.</div><div><br></div><div>Regards,</div><div> = =CF=86</div><div>Le mercredi 26 d=C3=A9cembre 2018 =C3=A0 19:58 -0600, Fran= k Trampe a =C3=A9crit :</div><blockquote type=3D"cite"><div dir=3D"ltr= ">Hello.<div><br></div><div>We are working hard to get the 2018 release of = FontForge done before the end of the year. There is one proposed change tha= t seems to require feedback and general approval from the user community.</= div><div><br></div><div>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 imp= lement UFO 3 extensions, which marks a big change from the jumbled common d= enominator 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 taki= ng the reverse approach, using ".ufo" for UFO 3 and ".ufo2" for UFO 2. I wo= uld like to pursue this path if it doesn't create any particularly difficul= t problems for our users.</div><div><br></div><div>I would appreciate feedb= ack on this proposal.</div><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></body></html> --=-g26KYM9OTVJOn2z8mbcY-- --===============5595778203783657487== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============5595778203783657487== 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 --===============5595778203783657487==--