UFO Filename Handling

--===============0869830172570917380==
Content-Type: multipart/alternative; boundary="000000000000b9faf9057df74a29"

--000000000000b9faf9057df74a29
Content-Type: text/plain; charset="UTF-8"

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

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

<div dir=3D"ltr">Hello.<div><br></div><div>We are working hard to get the 2=
018 release of FontForge done before the end of the year. There is one prop=
osed change that seems to require feedback and general approval from the us=
er community.</div><div><br></div><div>The adoption of UFO 3 has finally bo=
th allowed and compelled us to make a clean break between UFO 2 and UFO 3 a=
nd to fully implement UFO 3 extensions, which marks a big change from the j=
umbled common denominator output that we have been using up to this point. =
Because of the way the scripting interfaces work, the only way to different=
iate 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 =
be 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 U=
FO 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 t=
o pursue this path if it doesn&#39;t create any particularly difficult prob=
lems 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>

--000000000000b9faf9057df74a29--


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


--===============0869830172570917380==
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

--===============0869830172570917380==--