Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing fonts #114

Open
christianrauch opened this issue Dec 23, 2021 · 9 comments
Open

missing fonts #114

christianrauch opened this issue Dec 23, 2021 · 9 comments

Comments

@christianrauch
Copy link

On start, WPS reports that are missing from the installation:
Bildschirmfoto von 2021-12-23 13-08-07

@ImBearChild
Copy link

Those fonts are not shipped with WPS. Actually, they are from MS Windows.

@christianrauch
Copy link
Author

Actually, they are from MS Windows.

Are those proprietary fonts? Can they be included with the flatpak?

@qoheniac
Copy link

qoheniac commented Sep 2, 2022

You can create an Arch container (if you don't already run Arch), and use makepkg -i PKGBUILD to download the fonts from the Windows 11 Enterprise 90-day evaluation edition. It will move the fonts to /usr/share/fonts/TTF and you can move them from there to the host system (if you were using a container).

@tinywrkb
Copy link
Contributor

tinywrkb commented Sep 2, 2022

You can create an Arch container

Why going through this trouble? Just throw the fonts in ~/.local/share/fonts and add the override --filesystem=xdg-data/fonts to the app, and this should be enough.

@qoheniac
Copy link

qoheniac commented Sep 2, 2022

That's what I meant when I wrote move them from there to the host system and you don't actually need the override. But you need to get the fonts from somewhere first and I just thought it's best to get them directly from the source. And why reinvent the wheel when someone already wrote a maintained script to do just that.

@tinywrkb
Copy link
Contributor

tinywrkb commented Sep 2, 2022

That's a pretty terrible package to recommend, and one of the worst packaging I've seen. Setting up a loop device and accessing system service (UDisks2), that's falls under bad packaging practices. A packaging recipe should not f*** with my system.

I suggest extracting the fonts manually from the ISO. fuseiso should work, probably 7z, which means also PeaZip.

@tinywrkb
Copy link
Contributor

tinywrkb commented Sep 2, 2022

Oh! And I find it hard to believe that packaging will work in a container, considering UDisks2.

@qoheniac
Copy link

qoheniac commented Sep 2, 2022

It messes with the container image you burn anyways after you're done but sure you can do it manually. I just wanted to point out a way to get those fonts.

@christianrauch
Copy link
Author

If those fonts are proprietary and it's not allowed to distribute them, then it does not matter how you extract them for the flatpak. You simply cannot distribute the flatpak with these fonts inside. But if there were a script that could download them directly from Microsoft, you could include that in the flatpak and let a user run it to extract scripts in a local font dir (after the user accepts whatever EULA).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants