Project

Profile

Help

Bug #5561

open

misleading error message on failure to find external DTD

Added by Lou Burnard 2 months ago. Updated 27 days ago.

Status:
New
Priority:
Low
Category:
-
Start date:
2022-06-11
Due date:
% Done:

0%

Estimated time:
Found in version:
Fixed in version:
Platforms:

Description

If the source file being transformed by a stylesheet contains a DOCTYPE statement which references a non-existent file, an I/O error is raised. That's fine, but the diagnostic message suggests that it's the source file which doesn't exist, rather than a file it references.

SaxonC-HE 11.3 from Saxonica
source in transformFiletoString=/home/lou/Desktop/LacyWork/outgoing/0101Time/temp.xml 
stylsheet=/home/lou/Public/pdf2tei/pt0.xsl
Error 
   I/O error reported by XML parser processing
  /home/lou/Desktop/LacyWork/outgoing/0101Time/temp.xml: No such file or directory. Caused
  by java.io.FileNotFoundException: No such file or directory

Simply doing touch [dtdFilename] makes this error go away.

Here for comparison is the message provided if the source file really doesn't exist

SaxonC-HE 11.3 from Saxonica
source in transformFiletoString=/home/lou/Desktop/LacyWork/outgoing/0101Time/tump.xml 
stylsheet=/home/lou/Public/pdf2tei/pt0.xsl
Error 
   I/O error reported by XML parser processing
  /home/lou/Desktop/LacyWork/outgoing/0101Time/tump.xml: No such file or directory. Caused
  by java.io.FileNotFoundException: No such file or directory

Can you see any difference? Me neither.


Related issues

Related to Saxon - Bug #5606: Duplicate source error message in exception (Saxon 11)ClosedMichael Kay2022-07-15

Actions

Please register to edit this issue

Also available in: Atom PDF