non-ascii collection names over WebDAV?
Friday, 21 August 2015 · 7 messages · last reply 25 Aug 2015
AJ
Andreas Jung21 Aug 2015 09:32 #
Hi there,
does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters?
In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. File names and directory names must be preserved. BaseX seems to normalize names to ascii. Any way to change this?
Andreas
CG
Christian Grün21 Aug 2015 12:34 #
Quoted text · Andreas Jung · 5 lines
> does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? > > In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. > File names and directory names must be preserved. BaseX seems to normalize names to ascii. > Any way to change this?
How do you exactly proceed to import ZIP files via WebDAV? Do you encounter similar problems when import your ZIP file via the GUI or other APIs?
Christian
AJ
Andreas Jung21 Aug 2015 13:30 #
I could reproduce this using cadaver
dav:/webdav/> ls
Listing collection `/webdav/': collection is empty.
dav:/webdav/> mkcol üöäß
Creating `üöäß': succeeded.
dav:/webdav/> ls
Listing collection `/webdav/': succeeded.
Coll: uoas
and using Python 2.7 (using pyfilesystem API).
Andreas
Quoted text · Christian Grün · 12 lines
On 21 Aug 2015, at 12:34, Christian Grün wrote: >> does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? >> >> In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. >> File names and directory names must be preserved. BaseX seems to normalize names to ascii. >> Any way to change this? > > How do you exactly proceed to import ZIP files via WebDAV? Do you > encounter similar problems when import your ZIP file via the GUI or > other APIs? > > Christian
CG
Christian Grün21 Aug 2015 23:31 #
Thanks; I could create similar behavior. Now listed as bug on GitHub [1]. Christian
[1] https://github.com/BaseXdb/basex/issues/1184
Quoted text · Andreas Jung · 31 lines
On Fri, Aug 21, 2015 at 1:30 PM, Andreas Jung <lists at zopyx.com> wrote: > I could reproduce this using cadaver > > dav:/webdav/> ls > Listing collection `/webdav/': collection is empty. > > dav:/webdav/> mkcol üöäß > Creating `üöäß': succeeded. > > dav:/webdav/> ls > Listing collection `/webdav/': succeeded. > Coll: uoas > > and using Python 2.7 (using pyfilesystem API). > > Andreas > > > On 21 Aug 2015, at 12:34, Christian Grün wrote: > >>> does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? >>> >>> In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. >>> File names and directory names must be preserved. BaseX seems to normalize names to ascii. >>> Any way to change this? >> >> How do you exactly proceed to import ZIP files via WebDAV? Do you >> encounter similar problems when import your ZIP file via the GUI or >> other APIs? >> >> Christian
CG
It seems that the name decoding is done within the Milton library. As far as I know, eXist-db uses the same WebDAV library; did you encountered the same encoding issues with eXist-db?
Quoted text · Andreas Jung · 10 lines
On Fri, Aug 21, 2015 at 9:32 AM, Andreas Jung <lists at zopyx.com> wrote: > Hi there, > > does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? > > In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. > File names and directory names must be preserved. BaseX seems to normalize names to ascii. > Any way to change this? > > Andreas
AJ
Andreas Jung25 Aug 2015 06:04 #
No, I don't. Exist works happily with non-ascii chars. I can across the issue while running my XML Director test suite which has explicit tests with non-ascii collection names against Exist and BaseX.
Andreas
Quoted text · Christian Grün · 16 lines
On 24 Aug 2015, at 17:55, Christian Grün wrote: > It seems that the name decoding is done within the Milton library. As > far as I know, eXist-db uses the same WebDAV library; did you > encountered the same encoding issues with eXist-db? > > > On Fri, Aug 21, 2015 at 9:32 AM, Andreas Jung <lists at zopyx.com> wrote: >> Hi there, >> >> does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? >> >> In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. >> File names and directory names must be preserved. BaseX seems to normalize names to ascii. >> Any way to change this? >> >> Andreas
CG
Christian Grün25 Aug 2015 08:25 #
Thanks. I think I've found a solution for some of the mentioned issues. However, some of the WebDAV operations like rename still need to be looked at.
Your feedback on the latest snapshot is welcome [1].
Christian
PS: I'll be abroad for a while, so my next replies will take a while.
[1] http://files.basex.org/releases/latest/
Quoted text · Andreas Jung · 25 lines
On Tue, Aug 25, 2015 at 6:04 AM, Andreas Jung <lists at zopyx.com> wrote: > > No, I don't. Exist works happily with non-ascii chars. I can across the issue > while running my XML Director test suite which has explicit tests with non-ascii > collection names against Exist and BaseX. > > Andreas > > On 24 Aug 2015, at 17:55, Christian Grün wrote: > >> It seems that the name decoding is done within the Milton library. As >> far as I know, eXist-db uses the same WebDAV library; did you >> encountered the same encoding issues with eXist-db? >> >> >> On Fri, Aug 21, 2015 at 9:32 AM, Andreas Jung <lists at zopyx.com> wrote: >>> Hi there, >>> >>> does BaseX support the creation of collections containing non-ascii (uft8-encoded) characters? >>> >>> In my case we have a functionality to import a ZIP file into BaseX or Exist-DB over WebDAV. >>> File names and directory names must be preserved. BaseX seems to normalize names to ascii. >>> Any way to change this? >>> >>> Andreas
Written for BaseX 8.2. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery