Re: [fontforge-users] UFO Filename Handling

--===============6694075290882235353==
Content-Type: multipart/alternative; boundary="000000000000251546057e1b3231"

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

I think that other software stacks pull rugs out from under people too
frequently sometimes, but I believe that this is the right approach, and
I'm glad that you all agree.


On Fri, Dec 28, 2018 at 5:02 AM Hugh S. Myers <[email protected]> wrote:

> Frank,
> If Coffeescript can get away with an extension of .coffee. Then it follow=
s
> that you've got a free hand in the situation. From your description of th=
e
> 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. T=
he
>> 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 th=
e
>>> 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 denominato=
r
>>> 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 en=
d in
>>> ".ufo". The least disruptive change would be to keep ".ufo" for UFO 2 a=
nd
>>> 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 difficul=
t
>>> 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
>
> _______________________________________________
> fontforge-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fontforge-users
> http://fontforge.10959.n7.nabble.com/User-f8781.html

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

<div dir=3D"ltr">I think that other software stacks pull rugs out from unde=
r people too frequently sometimes, but I believe that this is the right app=
roach, and I&#39;m glad that you all agree.<div><br></div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr">On Fri, Dec 28, 2018 at 5:02 AM Hugh S=
. Myers &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr">Frank,<div>If Coffeescript=C2=A0can get away with an extension of =
.coffee. Then it follows that you&#39;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</div></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr">On Thu, Dec 27, 2018 at 10:31 PM Frank Trampe &lt;<a href=3D"mailto:fra=
[email protected]" target=3D"_blank">[email protected]</a>&gt; 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"lt=
r">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_2018110=
3_1" target=3D"_blank">The code</a> and <a href=3D"http://fontforge.github.=
io/en-US/bulletins/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, 2=
018 at 7:58 PM Frank Trampe &lt;<a href=3D"mailto:[email protected]" t=
arget=3D"_blank">[email protected]</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hello.<div><br></di=
v><div>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 fe=
edback and general approval from the user community.</div><div><br></div><d=
iv>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 extensio=
ns, which marks a big change from the jumbled common denominator output tha=
t we have been using up to this point. Because of the way the scripting int=
erfaces work, the only way to differentiate UFO 2 from UFO 3 on output is v=
ia the directory name extension. One of the two cannot end in &quot;.ufo&qu=
ot;. 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 ado=
ption of UFO 3 and the limitations of UFO 2, there would be a lot of upside=
s to taking the reverse approach, using &quot;.ufo&quot; for UFO 3 and &quo=
t;.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.</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>
_______________________________________________<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>

--000000000000251546057e1b3231--


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


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

--===============6694075290882235353==--