DITA/FM8 topic misbehavior

Article View: adobe.framemaker.sgml

Article #283

Back to adobe.framemaker.sgml Previous Next

#283

From: Toby_P_Green
Date: Thu, 22 Jan 2009 14:45

5 lines
1311 bytes

I've noticed some funny business with our implementation of DITA that I was hoping someone could shed some light on.

When we work with topic topics, tasks, or concepts, fm-xref elements don't save. When the document is reopened, they are replaced with xref elements, and nonfunctional ones at that. Similarly, image element href attributes do not populate at import in theses topics. The funny part is that in references, fm-xref elements work and save correctly, and image href values are automatically populated. HOWEVER, they populate with windows filepaths (Drive\Parent Dir\Dir\Filename) instead of the web relative urls that I was under the impression DITA used (../Sub Dir/filename).

If anyone can explain any of this, I'd be supergrateful.

Technical Details

Message-ID: <59b79573.-1@webcrossing.la2eafNXanI>

Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2.glorb.com!newshub.sdsu.edu!webcrossing

Show Full Headers

Complete Article Headers

X-Google-Thread: fcc08,b0251328f01e897f,start
X-Google-Attributes: gidfcc08,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
From: Toby_P_Green@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2.glorb.com!newshub.sdsu.edu!webcrossing
Newsgroups: adobe.framemaker.sgml
Subject: DITA/FM8 topic misbehavior
Message-ID: <59b79573.-1@webcrossing.la2eafNXanI>
Date: Thu, 22 Jan 2009 06:45:37 -0800
Lines: 13
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit