• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Handling of Japanese file names

Zoo3

Regular Pleskian
I'm having trouble opening a file with a Japanese file name in Collabora Online(CODE). I can change that file to English and open the file.
I use Collabora Online on Nextcloud and Mattermost. Users cannot open files with Japanese file names in either application. Users will not be able to open the file if they change the file name from English to Japanese on Nextcloud.

I verified this on Collabora's demo site and it was fine there. In other words, the cause is my environment.
If it's an English file, there's no problem, but if it's a Japanese file name, there's a problem. How do I find the cause of the problem?

I started facing this problem in Collabora 6.2-16. But on Collabora's demo site, it's not a problem.
I have glibc-common installed and I think most of the language locales are installed.

---
CentOS 7.8 PHP 7.3.19, nginx 1.16.1, Plesk Obsidian 18.0.27
 
Last edited:
Back
Top