Inspiring

Question

Why does EDD to DTD truncate some Element Names?

Forum|Forum|11 years ago
May 15, 2015
1 reply
389 views

Running FMv12/Structured in Win7. StructApps is established for this project.

Task at hand: Finagle XML out of FMv12 structured documents while EDD is not properly written. That is, Element Names are apparently too long for SGML, and Attribute Values contain spaces!

Trying to use DTD to draft new R/W Rules, but saving EDD as DTD squawks that R/W Rules are not found.

Since the DTD still comes out, I press, hoping to get somewhere anyway.

However, in the resultant DTD, long Element Names have been truncated to 8 chars. But not all of them. Some are left long.

What to do?

Am I on the wrong track to begin with? That is, XML might not be available at all due to spaces in Attribute Values(?).

Thanks,

Dave

Structured

This topic has been closed for replies.

ScottPrentice

Inspiring

Hi Dave...

I think you'll need to be a bit more specific in your question. I'm not sure what you're asking. There are a lot of pieces involved here, I think you'll need to focus on one issue at a time. Are you dealing with XML or SGML? Seems like XML, but you mention SGML as well.

One thing I can address .. there's no reason that attribute values (not attribute names) can't have spaces in them. Happens all of the time.

...scott

DrDaveJAuthor

Inspiring

Sorry for confusion. Working toward XML.

SGML came up because. . . . well it's a longer answer and likely stays confusing!

So, I am trying to develop the StructApps to get XML. I think our EDD is not compatible with XML, but am trying anyway to make it happen.

For one thing, NameLen might be an issue. Yes, that comes from the SGML side, so may not be an issue here at all.

For another thing, we use a ton of Inclusions and Exclusions; which I know were at issue long ago. Am hoping, with current specs and software, etc. these days, and since our tagged content is well formed, maybe tagged XML output is actually available.

To restate my original post.

In EDD, I Save As to get DTD. Process squawks about missing R/W Rules, but DTD comes out. With some element names truncated.

In EDD, I go to Struc Tools > New R/W Rules, and then Launch Rule File Maker with above DTD selected.

The process generates an Err Log that includes the following examples:

Line 26, Char 40, Msg: Expected '|' enumeration separator or closing parens. >> Eliminating space in attribute values moves error location to next instance of same issue. I can repair many values in EDD, reprocess, and err location moves on down the file.
Line 48, Char 22, Msg: Expected content specification expression for Element 'Acronym'. I dont know what this means.
In DTD, that element looks like this:
<!ELEMENT Acronym - - (#PCDATA)>
<!ATTLIST Acronym Definition CDATA #REQUIRED
ConditionCode CDATA #REQUIRED >
There are other errors, but these are the only two I've looked at so far.

Is this any better? Can you help?

Dave

ScottPrentice

Inspiring

It's hard to say what to do without seeing the EDD (and, no .. I'm not saying that I'll look at it .. that's more than I can do right now .. sorry).

What I'd suggest is looking at a working XML EDD and comparing the element definitions to those in your file. The DITA EDDs all work, but may be more complex than you want to deal with. Maybe look at xdobook or xhtml.

Make a rules file (just copy an existing one and fix it up). If you don't know how to fix it up, read the docs ..

http://www.adobe.com/support/documentation/en/framemaker/

Those are not the most current guides for streetcar development, but that's what comes up when I search .. (geez Adobe, can't you make it easier for people to find the right docs?) .. it doesn't matter though, the fundamental functionality of this stuff hasn't changed for a long time. The Structure Application Developer Guide and Reference are the books you want to read. It's all in there.

It does sound like your EDD isn't really compatible with XML output .. you'll need to fix it before you'll get a useful DTD.

Sorry I can't be of more help. Maybe someone else will chime in with more useful info!

Good luck!

...scott

<!ELEMENT Acronym	- - (#PCDATA)>
<!ATTLIST Acronym	Definition CDATA	#REQUIRED
	ConditionCode CDATA	#REQUIRED >

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded