Package Details: wps-office 11.1.0.11723-1

Git Clone URL: https://aur.archlinux.org/wps-office.git (read-only, click to copy)
Package Base: wps-office
Description: Kingsoft Office (WPS Office) - an office productivity suite
Upstream URL: http://wps-community.org
Licenses: LicenseRef-WPS-EULA
Conflicts: kingsoft-office
Submitter: felixonmars
Maintainer: Universebenzene
Last Packager: Universebenzene
Votes: 491
Popularity: 1.01
First Submitted: 2014-08-17 11:57 (UTC)
Last Updated: 2024-07-29 18:49 (UTC)

Dependencies (25)

Sources (2)

Pinned Comments

Universebenzene commented on 2023-01-20 10:34 (UTC)

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

Universebenzene commented on 2020-10-22 02:25 (UTC)

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

Universebenzene commented on 2020-01-10 04:48 (UTC) (edited on 2020-06-09 15:38 (UTC) by Universebenzene)

[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

Universebenzene commented on 2019-10-26 05:46 (UTC) (edited on 2019-10-26 07:10 (UTC) by Universebenzene)

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.

Universebenzene commented on 2019-07-05 17:08 (UTC)

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.

Universebenzene commented on 2019-04-16 13:34 (UTC)

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.

oowl commented on 2017-11-29 14:16 (UTC)

About the software issues, you can go to the official feedback problem. I'm just a packager, I can not solve the software problem.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 70 Next › Last »

theriddick commented on 2021-02-16 10:53 (UTC)

@Universebenzene yes I see that, but is for the Chinese version. Unfortunately I was looking for the multi language english version. I found instructions elsewhere on howto do it however. UNFORTUNATELY there is a bug with WPS Office where it will not spell check words, so much for that.. lmao

Universebenzene commented on 2021-02-16 09:55 (UTC)

@theriddick It's already mentioned in pinned message.

tinywrkb commented on 2021-01-17 12:18 (UTC)

fcitx5-wps make it possible to have an updated Fcitx5 module in WPS.
See here how it is built for Flatpak without the need to install or build QT 4.7.4. Further information is available in this blog post (use Google Translate if needed).

Except for updating the Fcitx module it also solves the problem of having to set QT_IM_MODULE=fcitx5 instead of fcitx.

With the latest Fcitx5 5.0.4 we actually don't need this if the fcitx4frontend addon is enabled, and it is by default, but I thought it worth posting here.

lewis2e commented on 2020-12-01 20:25 (UTC)

Does anyone know how to install different dictionaries? In my case I need en_GB but I don't know where to get it and nor can I see any way to install it

chain commented on 2020-11-22 12:24 (UTC)

Still problems with mime. Every time after writing microsoft type of document, WPS rewrite Override.xml in @HOME/.local/share/mime/application. So I had to patch \usr\lib\office6\libkso.so from to change this. That's real problem with mime types, not only google drive don't recognize documents, any software that need to check mime type, for example, in my CRM internal viewer can't show file contents.

ttc0419 commented on 2020-11-21 16:24 (UTC) (edited on 2020-11-22 03:41 (UTC) by ttc0419)

Hi @Universebenzene,

Thanks for the package, but there are several things can be improved:

  1. depends of PKGBUILD are outdated, missing a lot of libraries and some of the libraries are redundant. Use ldd to find the correct libraries.
  2. Package like this should be installed under /opt instead of /usr, see this wiki for more info
  3. What's the point of spliting into two packages? I know that you also made a mine package for cn version and they cannot be installed together, but can two versions of wps office installed side by side?
  4. What's the point of leaving outdated source and code in PKGBUILD?
  5. Please remove the post_install message, it's outdated and I don't understand why do we need that.
  6. Use rpm as source would be better as you do not need extra step to extract data.tar.xz.

I'm happy to be the maintainer if you do not have the time.

Cheers

chain commented on 2020-10-26 18:41 (UTC) (edited on 2020-10-29 15:03 (UTC) by chain)

google drive don't recognize docx, xlsx and all the office files from linux because of wps mime type - "mimeType": "application/wps-office.docx" for example instead of "application/vnd.openxmlformats-officedocument.wordprocessingml.document" can you change this behavior? Or may be tell how to repair it? Thanx. I've found decision: sudo rm -rf /usr/share/mime/packages/wps-office* rm -rf $HOME/.local/share/mime/packages/Override.xml sudo update-mime-database /usr/share/mime update-mime-database $HOME/.local/share/mime

Universebenzene commented on 2020-10-22 02:25 (UTC)

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

JoZ3 commented on 2020-10-21 20:47 (UTC) (edited on 2020-10-21 20:47 (UTC) by JoZ3)

Validating source files with sha1sums ... wps-office_11.1.0.9711.XA_amd64.deb ... HAS FAILED ==> ERROR: One or more files did not pass the validation check! Error: Failed to build wps-office

I download the file wps-office_11.1.0.9711.XA_amd64.deb and I usded sha1sum to checking the file integrity, and the checksums is the same that appears in the file PKGBUILD and the error keeps appearing