🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: adobe.framemaker.sgml
6 messages
6 total messages Started by Karen Millard Tue, 08 Jul 2008 18:07
XML read errors--failure to open dtd (DITA)
#992
Author: Karen Millard
Date: Tue, 08 Jul 2008 18:07
25 lines
2904 bytes
Hi all,
I've run out of ideas and places to look on this one, I hope someone can help.

The specs: WinXP Pro, Frame 8.0p277. Built-in DITA. Not using DITA Open Toolkit. No major issues except for previously discussed conref problems which, many thanks to Scott, seem to be under control.

The context: I'm a freelancer, on contract to a financial institution. I work part-time in my own office (up-to-date, preferred set-up) and part-time onsite. I can't go into detail, but the set-up is less than ideal. I have to do much back-and-forth portaging of project and template files, and they are often corrupted when I reopen them.

Specs onsite I'm not sure about, but it's definitely Frame 8 with the first patch. I'm pretty sure they haven't installed any others, so the 8.03 patch shouldn't be an issue. (I'll check and report back, if that info is needed.)

The error: Came out of the blue last week, my first day back in my office after three days onsite. Now, every time I open or create any xml file, using any template, I get an XML Read Report Log error that reports a failure to open the DTD, and a parse error in the document prolog. I don't know where it's coming from, and I don't know why it started happening. I modified structapps once, many months ago, but hadn't touched it since, and I've never touched the r/w rules files in either location.

(I realize I should test this scenario onsite, but I daren't risk importing trouble, if it started here.)

Specifically, the error reads: Could not open DTD file: C:\Documents and Settings\path-to-project-files-folder\ditabase.dtd Parse error at line 9, char 1: Error procssing external entity reference.

I don't understand why it's looking for the dtd file in the same folder as the project files when I've never stored it there, and I have the following in the structapps, and r/w rules files.

DTD: $STRUCTDIR\xml\dita\default-app\dtd\ditabase.dtd
Read/write rules: $STRUCTDIR\xml\dita\default-app\DITA-Topic-FM\topic.rules.txt

The R/W Rules statement reads: writer external dtd is public "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd";

I can go completely cross-eyed after a few hours trying to parse these docs myself. The answer may well be right in front of me, but for the life of me I can't see it. I hope someone else can.

Karen
Re: XML read errors--failure to open dtd (DITA)
#975
Author: Scott_Prentice
Date: Tue, 08 Jul 2008 18:50
20 lines
1502 bytes
Hi Karen...

The only thing that jumps out at me are the structapp paths .. if you haven't changed from the defaults they should point to ..

$STRUCTDIR\xml\dita\app

not this ..

$STRUCTDIR\xml\dita\default-app

That is, unless you created your own app called "default-app".

The other thing to check is the doctype declaration in the DITA files themselves. Have the DITA files been edited in another editor that is changing the doctype declaration in some way? The first two lines should look like this ..

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd" [

Lemme know.

...scott
Re: XML read errors--failure to open dtd (DITA)
#985
Author: Lynne_A._Price
Date: Sat, 12 Jul 2008 21:32
9 lines
1200 bytes
Karen,

You write that:

But the xml fails validation tests outside of Frame. The result reads: Line: 9; Line Position 3; File Position: 212; Error: The system cannot locate the object specified. Error processing resource 'ditabase.dtd'.

You'll either need to replace the relative pathname produced by FrameMaker or provide an appropriate search path to your other XML tools so that they can find the DTD.

--Lynne
Re: XML read errors--failure to open dtd (DITA)
#993
Author: Karen Millard
Date: Sun, 13 Jul 2008 06:37
10 lines
2203 bytes
Hi Lynne, Hi Scott,
My brain is a bit fried these days, so forgive me if what I say makes no sense. Regarding the relative path: I understand the concepts but not well enough to risk fooling around with entity references of any kind, dtd folders, or r/w rules files. Until I began troubleshooting, I hadn't touched structapps for months. I'd set up the project directory onsite so that it matched mine, and then tested the whole setup till I was sure it worked on both systems. Which it had done since last September. It was also working there just fine yesterday (Friday.) It's only on my system that I'm having trouble, and I haven't changed anything here, either.

(With regard to your follow-up, yes, I understand, but I opened them in other editors _after_ this started happening (to try and find out what was going on), not before.)

Having said all that: say I give up trying to figure out how it happened, what component of the structured application do I need to fix so that my files will open properly in Framemaker? So far, I believe, I've checked them all, but they all seem to be correct. (I'm assuming there's a template, edd, r/w rules or structapps issue because I've created and tested a dozen brand new files and they all have the same Read error on file creation, save and open. (ie. it's not just affecting existing project files.)

Anyway, if it goes away, I'll let you know. Meantime, I very much appreciate your feedback. I think I'll spend a lazy Sunday curled up with the SADG...again ;-)

Karen
Re: XML read errors--failure to open dtd (DITA)
#991
Author: Lynne_A._Price
Date: Mon, 14 Jul 2008 16:53
5 lines
973 bytes
Karen,

Do you have a backup of a configuration that worked? If so, you might compare it, one file at a time, to the current system. Have you updated FrameMaker itself in the meantime?

--Lynne
Re: XML read errors--failure to open dtd (DITA)
#982
Author: Karen Millard
Date: Tue, 15 Jul 2008 03:26
11 lines
2363 bytes
Hi Lynne,
Since this saga began, I haven't updated my own copy of Frame. I don't know what's been done to the onsite copy but I'll be able to check tomorrow.

I spent last night doing a line-by-line comparison of the original structapps, templates and EDD files, those from my system, and copies of those I use onsite. There were some element definition and formattting errors in my own templates which were likely introduced by my RSI-afflicted mouse-hand (it's not so steady sometimes--I can click things I don't mean to click). With luck (?) these are what caused the original problem. (I haven't had a chance to test my fixes.) There was an incorrect variable in my structapps, too, but I'm certain this was a recent error introduced the same way during troubleshooting. (I did the same thing when I was fixing it, but caught it before I hit Replace.)

However...

I was puzzled to discover that the ConditionalText/ OutputTextProcessingInstructions in one of the active structapps files were transposed, at least in comparison to the originals. ie where the originals were set to WithPIs, the active versions were set to Without, and vice versa. This was for the topic, map and book apps. There doesn't seem to be a variable associated with that element, so I don't see what I could have done. (I'm a freelancer, and what I break, I fix, generally. I learned enough about structured application development to figure out what I needed to tweak, then I got out and stayed out.) If you have an idea (or you actually know ;-), please enlighten me!

Best wishes,
Karen
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads