Re: [ft-devel] what old/new FontVal says about these fonts

2017-01-02 Thread Werner LEMBERG
>> You say `make', and a TTF compiler and decompiler together with an >> annotated documentation (in HTML format) gets built. You need Java >> and its development package (for `javac') for building and running >> the compiler stuff; it should work out of the box. > > Aehm, but I'm currently not

Re: [ft-devel] what old/new FontVal says about these fonts

2017-01-02 Thread Hin-Tak Leung
Happy New Year to you all too. The full-ish reports (notes below) of the 29 fonts, plus the 1.0-backend part are in: http://htl10.users.sourceforge.net/tmp/2017-Jan-broken-29-reports.tar.xz It is under 2MB but will expand to about 180MB, btw. The xml's are the original, but the derived html's

Re: [ft-devel] what old/new FontVal says about these fonts

2017-01-02 Thread Jan Bruns
Werner LEMBERG: >> Hm, I didn't get how aots is meant to be used, > You say `make', and a TTF compiler and decompiler together with an > annotated documentation (in HTML format) gets built. You need Java > and its development package (for `javac') for building and running the > compiler stuff; it

Re: [ft-devel] what old/new FontVal says about these fonts

2017-01-02 Thread Werner LEMBERG
> Hm, I didn't get how aots is meant to be used, You say `make', and a TTF compiler and decompiler together with an annotated documentation (in HTML format) gets built. You need Java and its development package (for `javac') for building and running the compiler stuff; it should work out of the b

Re: [ft-devel] what old/new FontVal says about these fonts

2017-01-02 Thread Jan Bruns
Werner LEMBERG: > Two remarks regarding inconsistencies with the OpenType specification. > > . There exists an annotated OpenType specification at > > https://github.com/adobe-type-tools/aots > >which discusses implementation problems. > > . If you find problems in the specification, pl

Re: [ft-devel] Announcing FreeType 2.7.1

2017-01-02 Thread Werner LEMBERG
>> No. Appending an element to a public structure that is accessed >> via a pointer only is ABI compatible for C. At least this is how I >> understand the issue. > > Yes, this is not a problem when it is accessed via pointer but it > still can be accessed directly (although it is unlikely). Als

Re: [ft-devel] Announcing FreeType 2.7.1

2017-01-02 Thread Marek Kasik
On 01/02/2017 05:06 PM, Werner LEMBERG wrote: > >> thank you for the new release. I've come over changes between 2.7 >> and 2.7.1 and I see that the structure "FT_Var_Named_Style" has new >> member "psid" but soname is still "6". Do you plan to bump the >> soname? > > No. Appending an element

Re: [ft-devel] Announcing FreeType 2.7.1

2017-01-02 Thread Werner LEMBERG
> thank you for the new release. I've come over changes between 2.7 > and 2.7.1 and I see that the structure "FT_Var_Named_Style" has new > member "psid" but soname is still "6". Do you plan to bump the > soname? No. Appending an element to a public structure that is accessed via a pointer onl

Re: [ft-devel] Announcing FreeType 2.7.1

2017-01-02 Thread Marek Kasik
Hi, thank you for the new release. I've come over changes between 2.7 and 2.7.1 and I see that the structure "FT_Var_Named_Style" has new member "psid" but soname is still "6". Do you plan to bump the soname? Regards Marek On 12/30/2016 10:39 PM, Werner LEMBERG wrote: > > FreeType 2.7.1 has b