Using code view adds an invalid attribute to fm-xref element


i've upgraded structured fm9 using dita structured fm11 using dita1.1 based on composite structured application. project includes number of xml files , seemed validating correctly. until opened file had saved , found invalid outputclass attribute in fm-xref element. in fact, of fm-xref elements had invalid attribute. trying discover came from, opened backup files , checked element, no outputclass attribute.  switch code view , wsywig view , there value in outputclass attribute.

 

it seems attribute value added cross reference format (fm:title_and_page) rather 1 of accepted attributes (topictitle, see figure, , on). 

 

i've seen there have been other issues code view. has else encountered 1 or know of fix it?

 

thanks,

sharon

hi sharon...

 

fm9 used @type attribute store cross-ref format name .. technically not quite apporpriate, in fm11 switched using @outputclass attribute data, makes more sense since styling information xref. isn't problem code view, , happen when open , save file (which happens when switch code view). problem there's no easy migration path fm9 fm11 in regard. if open files in text editor (or other xml editor) , change of xref/@type attributes xref/@outputclass (as long @type attribute values start woth "fm:") it'll groovy in fm11. you'll need 1 way ot since "right" attribute used purpose. it's unfortunate fm11 isn't more friendly migration.

 

however .. i'm thinking isn't problem you're talking about. asking actual value used in attribute, not matching expect? "valid" values set in edd. if you're not seeing values expect, you'll need modify edd uses values in template.

 

does or have confused many issues?

 

...scott



More discussions in FrameMaker Structured


adobe

Comments

Popular posts from this blog

How to set the order of FAQs instead of alphabetical

Thread: Get UK Keyboard working

how do I change the e-mail address for my merchant account