Re: UFO Filename Handling

--===============8584018648544450709==
Content-Type: multipart/alternative; boundary="0000000000004baff7057e0e5600"

--0000000000004baff7057e0e5600
Content-Type: text/plain; charset="UTF-8"

There seems to be near universal support for making UFO 3 the default. The
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 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
>
>

--0000000000004baff7057e0e5600
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">There seems 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">The code</a> and <a href=3D"http://fontforge.github.io/e=
n-US/bulletins/ufo3_2018_1/">the technical bulletin</a> are so updated. Rev=
iew and testing would be most appreciated.<div><br></div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr">On Wed, Dec 26, 2018 at 7:58 PM Frank T=
rampe &lt;<a href=3D"mailto:[email protected]">[email protected]<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr">Hello.<div><br></div><div>We are working hard to get the 20=
18 release of FontForge done before the end of the year. There is one propo=
sed change that seems to require feedback and general approval from the use=
r community.</div><div><br></div><div>The adoption of UFO 3 has finally bot=
h allowed and compelled us to make a clean break between UFO 2 and UFO 3 an=
d to fully implement UFO 3 extensions, which marks a big change from the ju=
mbled common denominator output that we have been using up to this point. B=
ecause of the way the scripting interfaces work, the only way to differenti=
ate UFO 2 from UFO 3 on output is via the directory name extension. One of =
the two cannot end in &quot;.ufo&quot;. The least disruptive change would b=
e to keep &quot;.ufo&quot; for UFO 2 and to use &quot;.ufo3&quot; for UFO 3=
. However, given the widespread adoption of UFO 3 and the limitations of UF=
O 2, there would be a lot of upsides to taking the reverse approach, using =
&quot;.ufo&quot; for UFO 3 and &quot;.ufo2&quot; for UFO 2. I would like to=
 pursue this path if it doesn&#39;t create any particularly difficult probl=
ems 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><d=
iv>Frank</div><div><br></div></div>
</blockquote></div>

--0000000000004baff7057e0e5600--


--===============8584018648544450709==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8584018648544450709==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html

--===============8584018648544450709==--