Arch Linux User Repository

Anyone who meet the problem of launching wpspdf, please install the optional dependency libtiff5

If you have the "ERROR: One or more files failed the validity check!" problem, try cleaning your AUR cache first, and try again.

[ATTENTION] The new international version (11.1.0.9080) removed zh_CN support, login, and some other functions. If you still want full functions, or you want aarch64 support, you may need the Chinese version from https://linux.wps.cn here: https://aur.archlinux.org/pkgbase/wps-office-cn

I split the /usr/share/mime/packages/wps-office-*.xml files to the wps-office-mime package to avoid mime issues. If you still want the mime files provided by wps-office itself, you can install the new mime package.

There is no official 32-bit package for version 11.1.0.8722, so I drop the support for i686 arch. For archlinux32 users you can create another wps-office package for 32-bit system yourself.

When you shut down wps-office, the wpsoffice process may still exist. You can do sudo chmod -x /usr/lib/office6/wpsoffice to fix it. But this might bring you problem with signing in.

"qt5-base" is necessary, please add it as dependency.

After updating from 10161 to 10702, the annotation functionality of the WPS PDF is gone. Does anyone know how to bring this functionality back? Thanks!

@CalzzOne that's very helpful thanks, looking good!

@matt17br: In et.kuip The style responsible for the autofilter is named "AutoFilter". Starting from the version of this particular style I found in the skin named "2018white_dark", I tweaked the colors until I found something I can use. I settled on changing the color named "content-background" to something dark ("#232323") and "filterthis-selectall-text" to something very visible ("#ff0000").

<style class="AutoFilter" base="common"><color name="background" value="#28292B"/><color name="title-background" value="#353638"/><color name="filteritem-split" value="#666666"/><color name="filterthis-normal" value="#5c9b32"/><color name="filterthis-hover" value="#7ab950"/><color name="filterthis-text" value="#ffffff"/><color name="tab-bottom-hover" value="#42b386"/><color name="tab-bottom-normal" value="#c8c8c8"/><color name="content-border" value="#b6c1cc"/><color name="content-background" value="#232323"/><color name="content-background-xa" value="#28292B"/><color name="treeheader-background" value="#eaeaea"/><color name="btn-text" value="#FFFFFFB8"/><color name="tab-text-normal" value="#FFFFFFB8"/><color name="common-text" value="#FFFFFFCC"/><color name="filterthis-selectall-text" value="#ff0000"/><linearGradient name="filterthis-normal" spread="pad" start="0,0" end="0,1"><color position="0" value="#5c9b32"/><color position="1" value="#5c9b32"/></linearGradient><linearGradient name="filterthis-hover" spread="pad" start="0,0" end="0,1"><color position="0" value="#7ab950"/><color position="1" value="#7ab950"/></linearGradient></style>

Hi @ppc52776: Thanks! It's good solution!

Good, @tornado99. Perfect solution, works prerfectly!

@curlywei, For who can't see fcitx5 input during typing, try to disable show preedit in application option in Fcitx 5 > Global Options.

Just to add that the true dark theme, which you can download from here: https://github.com/Prayag2/wps-skin-installer/tree/main/.skins, is now no longer buggy on WPS, and works well. You can also edit /home/[user]/.local/share/Kingsoft/office6/skinsv2/default/histroy.ini to add paths to extra skin folders, then change lastSkin= to the one you want. WPS Office does try to overwrite this file when it quits, so you will have to change permissions to read only.

@CalzzOne, thanks a lot for the insight. Your second solution doesn't seem to make a difference on my end, whereas your first solution works in that the menu bar on wps now has an actual dark theme, however the issue I still encounter is the following: https://i.imgur.com/15XsARx.png

As @flavio92ux pointed out the other day, the only fix that seems to work for me is running et as root, but your fix seems to work for him and I have no idea what I'm doing wrong. Just a minor annoyance but still pretty weird.

Thanks, @CalzzOne. The second solution worked for me. Thanks very much a lot!