Thanks,
The approach I was planning does not include any binaries, only scripts and manifest to build the actual flatpak yourself. I find the included Tahoe font from WineHQ does not exhibit proper kerning so the build script removes it (the file system is R/O at runtime). I spent time going through traces and WinBox seems to exclusively select Tahoe with 2 specific geometries.
After you build the flatpak the first execution downloads and installs WinBox, checks the available replacement fonts and provides a dialog box to choose one. The build script allows you to add your own fonts e.g. a GitHub repo where the Segoe font has been uploaded etc..
Not sure if this fits in with the established policy.
The approach I was planning does not include any binaries, only scripts and manifest to build the actual flatpak yourself. I find the included Tahoe font from WineHQ does not exhibit proper kerning so the build script removes it (the file system is R/O at runtime). I spent time going through traces and WinBox seems to exclusively select Tahoe with 2 specific geometries.
After you build the flatpak the first execution downloads and installs WinBox, checks the available replacement fonts and provides a dialog box to choose one. The build script allows you to add your own fonts e.g. a GitHub repo where the Segoe font has been uploaded etc..
Not sure if this fits in with the established policy.
Statistics: Posted by hfxdanc — Fri Feb 23, 2024 3:42 pm