RE: Need Help!!Getting Different glyph_locations in freetype 2.0.9 and 2.10.0

[Jain, Ankit]

Thank you mpsuzuki .Yes, these are types that changed over the time but I tried 
simply changing to FT_Byte* to  FT_Long* to newer version but that doesn't help.
Can somebody help me in getting those old values with new freetype or some 
other suggestion.

Thanks,
Ankit Jain

-----Original Message-----
From: suzuki toshiya <mpsuzuki@hiroshima-u.ac.jp>
Sent: Wednesday, April 26, 2023 7:51 PM
To: freetype@nongnu.org
Cc: Jain, Ankit <Ankit.Jain3@fisglobal.com>
Subject: Re: Need Help!!Getting Different glyph_locations in freetype 2.0.9 and 
2.10.0

The difference might be FT_Long* versus FT_Byte*.

Regards,
mpsuzuki

On 2023/04/26 22:15, Jain, Ankit wrote:
> Hi,
>
> I need help in knowing how we are getting different glyph_locations in 
> freetype version 2.0.9 and 2.10.0.
> I understand both are very different version initially we were using
> 2.0.9 version and creating the font data for post script(.ps file) we are 
> using these location to write the data in post script file as post script has 
> limitation in writing the number of bytes and after a certain threshold(65519 
> characters) it adds a new line.
> The threshold was getting in hit in older version and output was fine but 
> after upgrades the locations are not what we were getting in 2.0.9.
>
> Please find attached source code and glyph_location from both the versions. I 
> am using arial font for testing.
>
> Appreciate help any other pointers to move further from here.
>
> Thanks,
> Ankit Jain
>
> The information contained in this message is proprietary and/or confidential. 
> If you are not the intended recipient, please: (i) delete the message and all 
> copies; (ii) do not disclose, distribute or use the message in any manner; 
> and (iii) notify the sender immediately. In addition, please be aware that 
> any message addressed to our domain is subject to archiving and review by 
> persons other than the intended recipient. Thank you.
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.