Re: UFO Filename Handling

--===============0562250412141698096==
Content-Type: multipart/alternative; boundary="000000000000223dc4057e03995e"

--000000000000223dc4057e03995e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Philippe.

I still don't understand your argument. What are the specific deficiencies
in FontForge UFO 2 support to which you refer? And how do the proposed
changes affect your workflow?


On Thu, Dec 27, 2018 at 8:27 AM Philippe Cochy <[email protected]> wrote=
:

> To be clear, I think UFO2 support does not make sense.
>
> Le jeudi 27 d=C3=A9cembre 2018 =C3=A0 07:40 +0100, Philippe Cochy a =C3=
=A9crit :
>
> 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,
> =CF=86
> Le mercredi 26 d=C3=A9cembre 2018 =C3=A0 19:58 -0600, Frank Trampe a =C3=
=A9crit :
>
> 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 t=
he
> 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 [email protected]://=
lists.sourceforge.net/lists/listinfo/fontforge-develhttp://fontforge.10959.=
n7.nabble.com/Developer-f3.html
>
> _______________________________________________
> fontforge-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fontforge-devel
> http://fontforge.10959.n7.nabble.com/Developer-f3.html
>

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

<div dir=3D"ltr">Hi, Philippe.<div><br></div><div>I still don&#39;t underst=
and your argument. What are the specific deficiencies in FontForge UFO 2 su=
pport to which you refer? And how do the proposed changes affect your workf=
low?</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr">On Thu, Dec 27, 2018 at 8:27 AM Philippe Cochy &lt;<a href=3D"mailto:ac=
[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div><div>To be clear, I think UFO2=
 support does not make sense.</div><div><br></div><div>Le jeudi 27 d=C3=A9c=
embre 2018 =C3=A0 07:40 +0100, Philippe Cochy a =C3=A9crit=C2=A0:</div><blo=
ckquote type=3D"cite"><div>Hello Frank.</div><div><br></div><div>A UFO 3 fi=
le is a de facto standard, known by the tools. A UFO file 3 is understandab=
le and easily modifiable, for example using a user script. These two charac=
teristics open FF, keeping it alive.</div><div>Hell is hiding in the detail=
s. 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, Frank T=
rampe a =C3=A9crit=C2=A0:</div><blockquote type=3D"cite"><div dir=3D"ltr">H=
ello.<div><br></div><div>We are working hard to get the 2018 release of Fon=
tForge done before the end of the year. There is one proposed change that s=
eems 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 com=
pelled us to make a clean break between UFO 2 and UFO 3 and to fully implem=
ent UFO 3 extensions, which marks a big change from the jumbled common deno=
minator 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 UF=
O 3 on output is via the directory name extension. One of the two cannot en=
d 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 UFO 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 problems for our users=
.</div><div><br></div><div>I would appreciate feedback on this proposal.</d=
iv><div><br></div><div>Best wishes,</div><div><br></div><div>Frank</div><di=
v><br></div></div>
<pre>_______________________________________________
fontforge-devel mailing list
<a href=3D"mailto:[email protected]" target=3D"_blank">=
[email protected]</a>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/fontforge-devel" ta=
rget=3D"_blank">https://lists.sourceforge.net/lists/listinfo/fontforge-deve=
l</a>
<a href=3D"http://fontforge.10959.n7.nabble.com/Developer-f3.html" target=
=3D"_blank">http://fontforge.10959.n7.nabble.com/Developer-f3.html</a>
</pre></blockquote></blockquote></div>_____________________________________=
__________<br>
fontforge-devel 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-devel" re=
l=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/list=
info/fontforge-devel</a><br>
<a href=3D"http://fontforge.10959.n7.nabble.com/Developer-f3.html" rel=3D"n=
oreferrer" target=3D"_blank">http://fontforge.10959.n7.nabble.com/Developer=
-f3.html</a><br>
</blockquote></div>

--000000000000223dc4057e03995e--


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


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

--===============0562250412141698096==--