jp2masa
jp2masa
We want to ship compatible versions, and it's also easier for users if we ship these tools with the build tools package.
It uses native code.
There's already a PR for this.
It annoys me too. I'll try to do this.
Point 3 on [v11 porting guide - updating the project](https://github.com/AvaloniaUI/Avalonia/wiki/Avalonia-11-Porting-Guide#updating-the-project): > Remove the package reference to XamlNameReferenceGenerator - Avalonia now includes an inbuilt generator by default
This is a problem specifically on Linux, and it's not that easy to fix. For more info: - https://github.com/AvaloniaUI/Avalonia/issues/9002 - https://github.com/AvaloniaUI/Avalonia/issues/9390 - https://github.com/AvaloniaUI/Avalonia/wiki/Configuring-X11-per-monitor-DPI
Option B could allow reusing the route with `Raise` vs `RaiseAndComplete` or `Raise(..., bool complete = true)`, for example. As this is a lower-level API, the increased complexity is acceptable,...
> the only unusual part is that the sTypoDescent (from OS/2) and the ascent field in the hhea table were massive (in the order of 60,000 for a lot of...
I see, the problem seems to be that you're reading uint16 instead of int16, i.e. you should use `ReadInt16BigEndian` instead of `ReadUInt16BigEndian`.
Looking at the naming, there is a mismatch: `lineGap`/`lineSpacing`. I think you need to adapt the gdi code, although the `else` logic isn't very straightforward: probably doing `lineGap = Math.Max(hhea_linespacing,...