https://bugs.documentfoundation.org/show_bug.cgi?id=114758

            Bug ID: 114758
           Summary: Can't open files when name contains german umlauts
           Product: LibreOffice Online
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 138739
  --> https://bugs.documentfoundation.org/attachment.cgi?id=138739&action=edit
Original error message (german)

LOOL seems to have issues opening files which contain germany umlauts (ÄäÖöÜü).

Setup: CODE (compiled from source) integrated with nextcloud


Versions:

Nextcloud: 12.0.4 (stable)
Libreoffice: cp-5.3-36 bb5e55d
LOOL: CODE-3.0.0 81c8935

Steps to reproduce:

1. Create a new docuemnt in nextcloud with the name "täst.odt"
2. Click to open it in LOOL

Expexted behaviour: Document is opened and can be edited,

Actual behaviour: LOOL opens and shows an error-message (something along the
lines of "loading failed, please check if the document type is supported and
the file isn't broken" - see screenshot for the original german errormessage).

I found this in the server-logs: "Failed to load:
file:///user/docs/HgJF7HWvuf5pJ8t1/t%C3%A4st.odt, error: Unsupported URL
<file:///user/docs/HgJF7HWvuf5pJ8t1/t%C3%A4st.odt>: "type detection failed"|
kit/Kit.cpp:1484"

Note that as a workaround it is possible to rename the file, than edit it, and
rename it back to it's original name afterwards.

I think this issue might be related to one of the following:

Bug 101581 - Files with names containing diacritics can't be opened in LOOL
Bug 107051 - WOPI Error if german umlaute in domain

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to