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

[Aur] Traditional Chinese support in OnlyOffice DesktopEditors #135

Closed
kennethso168 opened this issue Aug 10, 2018 · 11 comments
Closed

[Aur] Traditional Chinese support in OnlyOffice DesktopEditors #135

kennethso168 opened this issue Aug 10, 2018 · 11 comments

Comments

@kennethso168
Copy link

I know Chinese display problems have been reported here, such as #82 . However, the behaviour on my system is different and I believe it has a different cause. Therefore I opened a new issue here.

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Chinese characters are shown as invisible characters, even when changed to a font with Chinese characters. Often, opening a document with Chinese characters makes OnlyOffice DesktopEditors hang at the loading screen.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

I have two test documents here to demonstrate the issue.

Document 1
test.docx

This document was created by Microsoft Office 2016 with a single line of "這是一段測試文字。". However, under OnlyOffice, the characters are displayed as invisible characters, not even boxes are shown.
screenshot_20180810_153413

I also tried to change the font from "Calibri" to some installed Chinese fonts such as Noto Sans CJK TC Regular. But the characters are still invisible. Unlike #82, in which the user can show the characters by changing to a Chinese font.
screenshot_20180810_153622

Document 2
何謂二十四節氣.docx

This document was created a long time ago, possibly by Microsoft Office 2007. It contains large paragraphs of Chinese text.

When opening the document from OnlyOffice DesktopEditors, OnlyOffice becomes stuck in the loading screen for over a minute:
screenshot_20180810_154137

While LibreOffice opens the document successfully:
screenshot_20180810_154526

In fact, many of my Chinese documents failed to open under DesktopEditors

What is the expected behavior?

OnlyOffice DesktopEditors can open the documents successfully with Chinese characters visible.

Which versions of DesktopEditors, and which OS are affected by this issue? Did this work in previous versions of DesktopEditors?

OnlyOffice DesktopEditors 5.1.29.350

Manjaro KDE (System Info)

I haven't tried previous versions.

Thank you.

@ShockwaveNN
Copy link
Contributor

Seems this have something to do with your OS, we just tried both of your issues (this and #134)
And everything working fine on our Ubuntu-Kubuntu systems, I downloading manjaro now to try it, but I'm not sure it OS dependent, more like something in configs of your system.
Could you try to reproduce your issues on other PC's?

@ShockwaveNN
Copy link
Contributor

ShockwaveNN commented Aug 10, 2018

@kennethso168 just notice that Manjaro is arch linux, and we have no Arch-specific package of editors. Did you use snap of AppImage version of DesktopEditors?

@kennethso168
Copy link
Author

Oh I'm using the AUR version from here (https://aur.archlinux.org/packages/onlyoffice-bin)
I know this isn't supported. But any guidance for debugging the problem would be greatly appreciated (e.g. are there any logs? I only get the following output when running from the command line)

./DesktopEditors: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/libascdocumentscore.so)
/opt/onlyoffice/desktopeditors/DesktopEditors: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/libascdocumentscore.so)
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
/opt/onlyoffice/desktopeditors/converter/x2t: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/converter/x2t)
/opt/onlyoffice/desktopeditors/converter/x2t: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/converter/libdoctrenderer.so)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/onlyoffice/desktopeditors/libascdocumentscore.so)

Off-topic:
By the way, after you've mentioned AppImage, I also tried running the AppImage version but I run into this issue

@ShockwaveNN
Copy link
Contributor

@kennethso168 Did you try this solution from https://aur.archlinux.org/packages/onlyoffice-bin

jamar commented on 2017-12-21 15:49
The problem with opening or creating documents is caused by wrong symlink to libcurl in /opt/onlyoffice/desktopeditors/converter/. So, just run command:

sudo ln -s -f /usr/lib/libcurl-compat.so.4.5.0 /opt/onlyoffice/desktopeditors/converter/libcurl.so.4

which will overwrite it with correct one and then opening and creating documents will work again.

@kennethso168
Copy link
Author

I tried this, but the same error still occurs and the problem isn't solved

@ShockwaveNN ShockwaveNN changed the title Traditional Chinese support in OnlyOffice DesktopEditors [Aur] Traditional Chinese support in OnlyOffice DesktopEditors Aug 10, 2018
@kennethso168
Copy link
Author

kennethso168 commented Aug 10, 2018

I also tried the snap version and the same problems (including #134 and this one) still exist. Should I also open an issue in the snap repo?

I may also test in a clean VM or ask other Manjaro users on the Manjaro forum to test this to see if this is a distro-specific problem, but this will take some time.

@ShockwaveNN
Copy link
Contributor

ShockwaveNN commented Aug 10, 2018

@kennethso168 I just tried aur on Archlinux image from Osboxes.Org and it just gave me segmentation failt. I'm installing Manjaro by now and take a look at snap.

@ShockwaveNN
Copy link
Contributor

@kennethso168 Ok, clean Manjaro install with https://aur.archlinux.org/packages/onlyoffice-bin opened your file without any troubles
image

@ShockwaveNN
Copy link
Contributor

@kennethso168 same with snap - a lot of warnings in console but file opened
image

@kennethso168
Copy link
Author

Thank you very much for testing that in a VM. It should be a problem of my system then.
Closing the issue.

@ShockwaveNN
Copy link
Contributor

@kennethso168 if you will able detect what is the reason of such behaviour - it will be good.
I'm not sure - but probably some of fonts installed on your system

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

2 participants