I/o Error Reported By Xml Parser Processing
Have I got the correct DTD? You can merge this pull request into a Git repository by running: $ git pull https://github.com/hutchkintoot/camel CAMEL-8287 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1118.patch To Making a very large form user friendly One syllable antonym for "care"? Following error is thrown: > > Error > I/O error reported by XML parser processing file:/F:/tést/test.xml: Path contains invalid character > > I'll illustrate this with following minimal test case (attached): http://upintheaether.com/i-o-error/i-o-error-reported-by-xml-parser-processing-no-protocol.php
F:/tést/test.xml) in the path, the transformation fails with following error: > > Error > I/O error reported by XML parser processing file:/F:/tést/test.xml: Path contains invalid character: é > > The culprit DITA Open Toolkit member eerohele commented Feb 26, 2016 @jelovirt: Nope, still getting the same error after applying that patch. When you switch manually to the Author visual editing mode do you receive an error message dialog? Error Error reported by XML parser processing file:/home/ond1/work/test/nicolas/xml/5.xml: The markup declarations contained or pointed to by the document type declaration must be well-formed.
DITA Open Toolkit member raducoravu commented Feb 29, 2016 I think I used the Java code from the 2.2.2 branch. Not the answer you're looking for? Would it be possible to have more permission on Camel Jira component. if so, would you be able to create a pull request for this?
xsl:import could probably be made to work when there is no base URI provided there is a URIResolver, but only with difficulty, because of the rule that says if you have Fix now applied to master. I actually also thought that DITA-OT already converted Windows separators to Unix separators. Please don't fill out this field.
That seems to return values which contain "\" instead of "/". We'll look into this, maybe we can somehow make the parsing of the XML when switching to the visual Author editing mode more relaxed to such problems. DITA Open Toolkit member jelovirt commented Feb 26, 2016 @raducoravu Yep, clearly a regression bug then. https://sourceforge.net/p/saxon/mailman/message/32977588/ Unfortunately, I don't have control over my input file format: I'm stuck with files referencing DTDs and entities using relative paths, and the paths may contain special characters.
Now I get this: Error I/O error reported by XML parser processing file:/C:/Users/z003a5bp/Desktop/Workspace/FOP/file:C:/Users/z003a5bp/Desktop/3-Leiter-Steuerung,%20Methode%202.xml: C:\Users\z003a5bp\Desktop\Workspace\FOP\file:C:\Users\z003a5bp\Desktop\3-Leiter-Steuerung, Methode 2.xml (the filename, directory name or volume label syntax is incorrect) net.sf.saxon.trans.XPathException: I/O error reported by Where are sudo's insults stored? "prohibiting" instead of "prohibit"? DITA Open Toolkit member raducoravu commented Feb 29, 2016 I'll test and get back. DITA Open Toolkit member eerohele commented Feb 26, 2016 @jelovirt: I can do that.
DITA Open Toolkit member raducoravu commented Feb 26, 2016 I think the entire DITA OT Java code should be combed for places where the Windows file separator is explicitly used or http://saxon-xslt-and-xquery-processor.13853.n7.nabble.com/I-O-error-reported-by-XML-parser-processing-td12695.html DITA Open Toolkit member raducoravu commented Feb 26, 2016 Yes, the problem is deeper embedded in the DITA OT. jelovirt added this to the 2.2.3 milestone Feb 26, 2016 DITA Open Toolkit member eerohele commented Feb 26, 2016 @raducoravu Ah, I see — I didn't look at the input files See the NOTICE file distributed with * this work for additional information regarding copyright ownership. * The ASF licenses this file to You under the Apache License, Version 2.0 * (the
Regards, Thomas. Hide Permalink ASF GitHub Bot added a comment - 15/Aug/16 13:18 GitHub user hutchkintoot opened a pull request: https://github.com/apache/camel/pull/1123 Fix for CAMEL-8287 Allows a user to supply a custom URIResolver to I will now investigate further what is happening. Laws characterizing the trivial group Crossing the border from Switzerland to France and back Plausibility of the Japanese Nekomimi How can I properly Handle this awkward situation?(job interview) Are non-english speakers
The failure is plausible, because it's not a valid absolute URI. Show ayache khettar added a comment - 20/Jan/16 07:04 Thanks Johan, I see what you mean I will look into this hopefully today. Join them; it only takes a minute: Sign up XSLT-Transformation with Saxon9he throws java.net.URISyntaxException: Illegal character in path at index up vote 1 down vote favorite I'm trying an xsl transformation Show Thomas Walzer added a comment - 28/Jan/15 15:57 The patch (I hope it works the way I created it) contains a test case to reproduce the issue.
Cannot parse document: C:\...\legalnotices.xml (The system cannot find the file specified)Pascale Radu Posts: 4235 Re: How to enable Author mode if parsing errors Quote Tue Sep 30, 2014 2:15 pm Hi Still odd however that the URIResolver was not even triggered. –Ayyoudy Aug 30 '11 at 14:19 add a comment| Your Answer draft saved draft discarded Sign up or log in Regards Show Johan Mörén added a comment - 19/Jan/16 20:16 Hi Ayache!
You signed out in another tab or window.
I use document() to load a bunch of files that i want to merge, which worked fine until the url in their doctype declaration ceased to work.As i can't change the But we would really need to have this back ported to the 2.16.x and 2.17.x branches if possible. I've been refactoring that code to use URI for all path processing, replacing File and String usage. Automated exception search integrated into your IDE Test Samebug Integration for IntelliJ IDEA Root Cause Analysis net.sf.saxon.s9api.SaxonApiException I/O error reported by XML parser processing C:\Program Files\DAISY Pipeline 2\daisy-pipeline\bin\../etc/config-calabash.xml: Unknown protocol: c
Maybe a simple fix could be made for this situation but ideally we could avoid using the Windows separator in the entire DITA OT code. I tried XsltCompiler, etc and same thing... Hide Permalink Johan Mörén added a comment - 09/Aug/16 14:28 - edited I'v been trying some things out and found that a possible way to fix this issue is to allow The code is in StandardCollectionURIResolver.java, so I would suggest you try running with a "user-written" collection URI resolver that contains this change, and let us know if it works for you.
I'm running version 2.15.3. Reload to refresh your session. When an XSLT stylesheet tries to load these files using the collection() function, this fails when the folder containing the XML files contains a special character. RE: Problem with EntityResolver and document() - Added by Nicolas Houillon over 3 years ago A more appropriate (and closer to what is really happening in my program) doctype line for
I am sorry I cannot think of a work-around without changing the xml files themselves, which I know you do not have control over. I've tried to specify the collection path in a number of varieties: as absolute path, as (encoded) URL, but this makes no difference. Hide Permalink ASF GitHub Bot added a comment - 15/Aug/16 13:20 Github user hutchkintoot closed the pull request at: https://github.com/apache/camel/pull/1118 Show ASF GitHub Bot added a comment - 15/Aug/16 13:20 Github You can merge this pull request into a Git repository by running: $ git pull https://github.com/hutchkintoot/camel CAMEL-8287-master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1123.patch To
Show Johan Mörén added a comment - 09/Aug/16 14:28 - edited I'v been trying some things out and found that a possible way to fix this issue is to allow the RE: Problem with EntityResolver and document() - Added by O'Neil Delpratt over 3 years ago Hi, I have finally managed to track done why we are getting this intermitted behaviour. share|improve this answer answered Jan 29 '14 at 12:24 Michael Kay 78.9k44080 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google When does bugfixing become overkill, if ever?
What would be the best way to handle that? Breaking an equation How can I Avoid Being Frightened by the Horror Story I am Writing? Automated exception search integrated into your IDE Test Samebug Integration for IntelliJ IDEA 0 mark BabelProcessor#process causes java.lang.CloneNotSupportedException GitHub | 10 months ago | yuki-takei java.lang.IllegalStateException: Calling Context.exit without previous Context.enter