Re: Imported graphics not exporting to XML: update

2006-11-28 Thread Lynne A. Price

At 06:41 AM 11/28/2006, Steve Rickaby wrote:
After half a day of documentation thrashing and cerebral overload, I think 
I now know part of the reason for this: I should have included a filepath 
attribute in the EDD for imported graphics. Adding one at least gets a 
file id into the XML... even though I still get the error. Grrr.


Steve,
  No need for a FrameMaker attribute. When moving data between FrameMaker 
and XML representations, the typical XML attribute does correspond to a 
FrameMaker attribute. Some XML attributes, however, correspond to a 
FrameMaker formatting property such as the number of columns in a table or 
the filename of an imported image.
  As to why you cannot export the graphics, it could be because you do not 
have an output filter that handles that format, because you don't have 
write permission in the directory where graphics would be written, 
or  other causes.

--Lynne


Lynne A. Price
Text Structure Consulting, Inc.
Specializing in structured FrameMaker consulting, application development, 
and training

[EMAIL PROTECTED]   http://www.txstruct.com
voice/fax: (510) 583-1505 cell phone: (510) 421-2284  



___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]

or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.


Re: Imported graphics not exporting to XML: update

2006-11-28 Thread Steve Rickaby
At 19:22 + 27/11/06, someone called Steve Rickaby wrote:

>What can cause the message:
>
>'Cannot export graphics or equation contents. Check the element mapping and 
>description'
>
>and failure to export graphics with XML export?
>
>I am exporting to XML without a structured application in place, as this is 
>one-way only. (Maybe not a great idea?) The documents are all valid, and the 
>exported XML looks ok, but as far as I can see none of the imported graphics 
>files are exported. The majority of imported graphics are EPS format.

After half a day of documentation thrashing and cerebral overload, I think I 
now know part of the reason for this: I should have included a filepath 
attribute in the EDD for imported graphics. Adding one at least gets a file id 
into the XML... even though I still get the error. Grrr.

Another possible problem is that the Structured Developer's Guide lists 'EPSB', 
'EPSD', 'EPSF' and 'EPSI' as exportable, but not plain old 'EPS'. We are 
working with EPSs from Adobe Illustrator.

I've also encountered an issue with element naming: we used the bullet 
character to distinguish top-level elements, as in 'Chapter*', and FrameMaker 
doesn't seem to like this, and appears to be reading the element name only to 
the character immediately preceding the bullet. Maybe it's because bullet isn't 
allowed in XML?

Onwards and upwards...

-- 
Steve
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.