Thread View: adobe.framemaker.sgml
5 messages
5 total messages
Started by NF82
Tue, 14 Oct 2008 07:26
FM8+DITA
Author: NF82
Date: Tue, 14 Oct 2008 07:26
Date: Tue, 14 Oct 2008 07:26
11 lines
791 bytes
791 bytes
Hello, the DITA Architectural Specification v1.0 says on page 18... "Some of the attributes and metadata in a map can be inherited based on the structures in the map." Is this implement for attributes in FM 8? Are there any effects?/Can I see any effects? Thanks, Nina
Re: FM8+DITA
Author: Scott_Prentice
Date: Tue, 14 Oct 2008 16:47
Date: Tue, 14 Oct 2008 16:47
5 lines
953 bytes
953 bytes
Hi Nina... Are you asking if you can enter attribute values in the map and have them passed down to the topics? I don't believe that the FM8 map to book transform is set up to do that, but you could probably modify the XSLT import script to support this to some degree. What is it that you're trying to do? ...scott
Re: FM8+DITA
Author: NF82
Date: Wed, 15 Oct 2008 14:58
Date: Wed, 15 Oct 2008 14:58
7 lines
1075 bytes
1075 bytes
Hello Scott, * Are you asking if you can enter attribute values in the map and have them passed down to the topics? --- Yes * What is it that you're trying to do? --- I create a concept for my metadata and attributes. If the attributes and metadata passed down from the map to the topic or from a "parent" topic to a "child" topic I don�t need to give the "child" topics attributes and metadata, they get them automatically and that save time. But if it isn�t possible, it�s okay. Nina
Re: FM8+DITA
Author: Scott_Prentice
Date: Wed, 15 Oct 2008 17:28
Date: Wed, 15 Oct 2008 17:28
5 lines
777 bytes
777 bytes
Hi Nina... It should be possible to do this, but would require modification to the XSLT import script. This may be something that we try to support in the 1.1 update for DITA-FMx. ...scott
Re: FM8+DITA
Author: systecgmbhnuremberg
Date: Fri, 16 Jan 2009 11:30
Date: Fri, 16 Jan 2009 11:30
28 lines
2058 bytes
2058 bytes
Hello Nina and Scott, this sounds good, but: it should only be so, if the "child" does not have its own values defined. If a attribute setting of a parent would override the child, this coud be an error: the child might rightly have its own set of values and on purpose. Also, in respect to use the metadata (of the prolog) for getting/setting CMS metadata, a topic must either have metadata or must not have metadata. If child topics would inherit metadata, this would imply that the children have the same metadata in the CMS, and this is also very improbable. I would argue that maintaining the prologue is something that has to be done on a per-topic basis.Also: Why would you like the metadata to be inheritable? For the sake of using attribute-based filtering? Just my 2 cents. With kind regards, Franz. [SYSTEC - the document processing company.] <http://www.systec-gmbh.com/sites/toolbox.php> <http://www.systec-gmbh.com/sites/ditapack.php> <http://www.systec-gmbh.com/sites/3dpack.php> ____________ |Schreiberhauer Str. 5 |D-90475 Nuernberg - Germany |Phone +49 911 998955-625 |Fax +49 911 998955-663 |e-Mail info@systec-gmbh.com |Internet: www.systec-gmbh.com |Redaction, Translation: www.systec-td.de |ePublishing, Solutions: www.systec-it.de ____________ |CEO: Dipl.-Ing. (FH) Georg Eck, Dipl.-Btw. (FH) Manfred Papp |Amtsgericht N�rnberg HRB 9369 |Umsatzsteuer-Identifikationsnummer DE 133560519 ______________ |"We innovate things that work better."
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