After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 325592 - document() doesn't handle non-ASCII paths
document() doesn't handle non-ASCII paths
Status: RESOLVED OBSOLETE
Product: libxslt
Classification: Platform
Component: general
1.1.11
Other Mac OS
: Normal normal
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-03 09:28 UTC by Alexey Proskuryakov
Modified: 2021-07-05 11:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test case (4.45 KB, application/zip)
2006-01-03 09:29 UTC, Alexey Proskuryakov
Details

Description Alexey Proskuryakov 2006-01-03 09:28:19 UTC
In the attached test case, only an ASCII filename works.

Works in Firefox as expected, but doesn't work in command-line xsltproc (version installed with Mac OS X 10.4). For easier testing, I have also made the test available via http:

xsltproc http://nypop.com/~ap/webkit/xslt-%D0%BF%D1%83%D1%82%D0%B8/xslt-%D0%BF%D1%83%D1%82%D0%B8.xml

Should have the string "Hello, WebKit!" in all lines (except for the first one in http-based test, of course).
Comment 1 Alexey Proskuryakov 2006-01-03 09:29:02 UTC
Created attachment 56700 [details]
test case
Comment 2 Daniel Veillard 2006-01-05 09:58:32 UTC
"only an ASCII filename works"
-> what is a filename ?

  http://www.w3.org/TR/xslt#function-document
  "This string is treated as a URI reference; the resource identified by
   the URI is retrieved."

Check the definition of document(), the string is to be interpreted
as an URI-Reference ! XSLT has no idea of what a filename is. On the 
other hand it references RFC 2396 (and later) for URI and URI-References.
Your strings are not %escaped as an URI Reference should be, hence the failure,
I don't think it is a bug.

Daniel
Comment 3 Alexey Proskuryakov 2006-01-05 13:03:33 UTC
Sorry about the confused terminology. The language of standards is often pretty confusing when it comes to non-ASCII characters, but in most implementation that I have seen, non-ASCII characters are permitted, and are percent-escaped only for transmission. This is also the most safe appoach, because otherwise the encoding of escaped characters (UTF-8, Latin-1 etc.) could easily get out of sync with the encoding of the document itself.

I have additionally verified that the attached test case works not only in Firefox, but also in Saxon 6.5.5.
Comment 4 GNOME Infrastructure Team 2021-07-05 11:00:49 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/libxslt/-/issues/

Thank you for your understanding and your help.