Re: UFO Filename Handling
"Hugh S. Myers" <[email protected]> Fri, 28 Dec 2018 03:58:29 -0700
| Newsgroups | gmane.comp.fonts.fontforge.user,gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <CAFkCg7-hsX3hZrKURWUGefurktau6_3_JmrE9yq-R_5BvwBzZw@mail.gmail.com> |
--===============1317288740451770113== Content-Type: multipart/alternative; boundary="0000000000003ed456057e12f3e3" --0000000000003ed456057e12f3e3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Frank, If Coffeescript can get away with an extension of .coffee. Then it follows that you've got a free hand in the situation. From your description of the situation, it looks as though UFO 3 is pretty much the winner. Sort of a nice idea=E2=80=94software version matching file extension=E2=80=A6 On Thu, Dec 27, 2018 at 10:31 PM Frank Trampe <[email protected]> wrote: > There seems to be near universal support for making UFO 3 the default. Th= e > code > <https://github.com/fontforge/fontforge/tree/sil_ufo_fixes_20181103_1> > and the technical bulletin > <http://fontforge.github.io/en-US/bulletins/ufo3_2018_1/> are so updated. > Review and testing would be most appreciated. > > > On Wed, Dec 26, 2018 at 7:58 PM Frank Trampe <[email protected]> > wrote: > >> 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 an= d >> 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-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fontforge-users > http://fontforge.10959.n7.nabble.com/User-f8781.html --0000000000003ed456057e12f3e3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Frank,<div>If Coffeescript=C2=A0can get away with an exten= sion of .coffee. Then it follows that you've got a free hand in the sit= uation. From your description of the situation, it looks as though UFO 3 is= pretty much the winner. Sort of a nice idea=E2=80=94software version match= ing file extension=E2=80=A6</div></div><br><div class=3D"gmail_quote"><div = dir=3D"ltr">On Thu, Dec 27, 2018 at 10:31 PM Frank Trampe <<a href=3D"ma= ilto:[email protected]">[email protected]</a>> wrote:<br></div= ><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border= -left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">There s= eems to be near universal support for making UFO 3 the default. <a href=3D"= https://github.com/fontforge/fontforge/tree/sil_ufo_fixes_20181103_1" targe= t=3D"_blank">The code</a> and <a href=3D"http://fontforge.github.io/en-US/b= ulletins/ufo3_2018_1/" target=3D"_blank">the technical bulletin</a> are so = updated. Review and testing would be most appreciated.<div><br></div></div>= <br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Dec 26, 2018 at 7:5= 8 PM Frank Trampe <<a href=3D"mailto:[email protected]" target=3D"_= blank">[email protected]</a>> wrote:<br></div><blockquote class=3D"= gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20= 4,204,204);padding-left:1ex"><div dir=3D"ltr">Hello.<div><br></div><div>We = are working hard to get the 2018 release of FontForge done before the end o= f the year. There is one proposed change that seems to require feedback and= general approval from the user community.</div><div><br></div><div>The ado= ption of UFO 3 has finally both allowed and compelled us to make a clean br= eak 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 wo= rk, the only way to differentiate UFO 2 from UFO 3 on output is via the dir= ectory name extension. One of the two cannot end in ".ufo". The l= east disruptive change would be to keep ".ufo" for UFO 2 and to u= se ".ufo3" for UFO 3. However, given the widespread adoption of U= FO 3 and the limitations of UFO 2, there would be a lot of upsides to takin= g the reverse approach, using ".ufo" for UFO 3 and ".ufo2&qu= ot; for UFO 2. I would like to pursue this path if it doesn't create an= y particularly difficult problems for our users.</div><div><br></div><div>I= would appreciate feedback on this proposal.</div><div><br></div><div>Best = wishes,</div><div><br></div><div>Frank</div><div><br></div></div> </blockquote></div> _______________________________________________<br> fontforge-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/fontforge-users" re= l=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/list= info/fontforge-users</a><br> <a href=3D"http://fontforge.10959.n7.nabble.com/User-f8781.html" rel=3D"nor= eferrer" target=3D"_blank">http://fontforge.10959.n7.nabble.com/User-f8781.= html</a></blockquote></div> --0000000000003ed456057e12f3e3-- --===============1317288740451770113== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1317288740451770113== 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 --===============1317288740451770113==--