[MGNLWEBDAV-18] Unicode support Created: 09/Nov/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: WebDAV (closed)
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.2

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-2929 Enhance unicode support Closed
supersession
supersedes MGNLWEBDAV-15 Node names aren't validated before cr... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We currently can't support non-ascii node names.

See http://confluence.magnolia-cms.com/display/DEV/Unicode+support+status



 Comments   
Comment by Magnolia International [ 19/Mar/10 ]

This might be fixed with MAGNOLIA-2929, to be verified.

Comment by Christian Balaguer [ 28/Oct/13 ]

Hi Grégory

I'd like to ask what the current progress on this matter is? We're evaluating an integration of the WebDAV module for a client and they're having german umlauts in their filenames of the dms. At the moment it's not even possible to list the content of the directories containing files with umlauts in their name.

Chris

Comment by Magnolia International [ 13/Nov/13 ]

Hey Christian,

MAGNOLIA-2929 is very low priority, but again, if we consider unicode support for webdav, it might be easier/simpler to fix it there; or.. there might be an easy fix in the webdav module itself. Would need to investigate.

Sorry I didn't see this earlier - there are no plans that I know of, but that could be considered. As always, patches or simply help with testing would definitely help getting things on track faster.

Cheers,

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 11:10:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.