[MPEG-OTSPEC] Updates to specification

[Behdad Esfahbod]

On Fri, Aug 14, 2020 at 7:40 AM Eric Muller <eric.muller at efele.net> wrote:

> At the same time, the names of structures in OpenType tables end up in
> code, documentation, tools' UI, discussions on this list, our heads, etc..
> Changing them every two months is not going to help. I would prefer such
> changes to occur infrequently, may be accumulating them in a backlog in the
> mean time.
>

Not just that: Peter's unilateral renaming was a disservice to the
specification: he replaced the obscure-looking "SHORT", "USHORT", "LONG",
"ULONG", with common words "int16", "uint16", "int32", "uint32", even
though those do not match the similarly-named types in computers and
languages, because the OpenType ones are always big-endian.  If he had
consulted others, we could have reached a universally-unambiguous and clear
names.

b



>
> Eric.
>
> On 8/13/2020 12:12 PM, Levantovsky, Vladimir wrote:
>
> I’d argue that naming convention / name changes that do not affect data
> structures and have no effect on future and existing implementations can
> and should be considered purely editorial in nature. They are within the
> editor’s responsibilities of things to do to maintain the clarity of the
> spec itself.
>
>
>
> Vlad
>
>
>
>
>
>
> _______________________________________________
> mpeg-otspec mailing list
> mpeg-otspec at lists.aau.at
> https://lists.aau.at/mailman/listinfo/mpeg-otspec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200814/263dd206/attachment.html>