Hi Carrie, Thanks for the information about Container and CrossReference element types. I hadn't picked that up from the Structured Developers Guide -- good...
Hi Mark. It appears that in Frame 7.2, Adobe fixed the problem of the xref not closing by changing the xref element definition in the .mod files. Try ...
Hi... I'm working on getting FrameMaker to handle both a DITA-based xref (one with content) as well as a FrameMaker-based xref (where the content is defined by...
Modifying my .mod file worked, Carrie. Amazing! How'd you get to be such a smart cookie? I adjusted my EDD and read/write rules half a dozen times each, and...
Hmm .. OK, I see that setting 'format' to anything other than the approved values, results in a bogus link (at least in the CHM build). However, using the...
How do authors use topics? I have to convert a traditional A4 reference manual with chapters and sections into DITA without rewriting it. Would you map each...
How do authoring groups get DITA off the ground from a standing start? An eventual DITA project might consist of 5000 topics written by 20 authors, with...
... When we are migrating books to topics, I tell our authors to make a judgement call on "leaf" headings (i.e., those without children). If the heading plus...
... Two words: Content Management System. It's quite possible to use a filesystem to manage that many topics (we are), but it does increase the risk of losing...
... Just tried it, and it seems to work when I run a command-line transformation. I'm using Java 1.5.0_06 on Mac OS X, DITA-OT 1.2.2 source compiled with "ant...
Hello! DITA uses the Exchange Table Model, which is very close to CALS-tables. I assume it would be no problem, to specialize also table elements or to create...
DITA has two table models, Exchange and Simple Table. Simple table is the type more appropriate for specialization. In fact DITA itself contains several...
... Yep, sure. As Paul mentioned, there's already a few specializations of <simpletable>, but those happen to be structural specializations rather than domain...
Darn, hit "send" too quickly. ... I forgot about the ~= selector, which matches one of a set of space-separated strings, and would probably suffice for class ...
Actually, I am not aware of any JDK 1.4 dependency for the FO plugin nor XEP specifically. RenderX only states that they require JDK 1.2 and newer. I just...
... made ... therefore, ... When we started working on the DITA OT User Guide, we ran into some of these problems of scale. We did several things that helped a...
XMetaL does support the ~= selector (for more than a year now) and future versions of XMetaL will make very targeted specialization as easy as possible. In the...
Hi Chris, That's correct...there is an incompatibility with the IBM SDK because it ships Xerces instead of Crimson. Some code in xep.jar calls the Crimson...
Dear dita developers, We are a group of professionals and researchers (Montpellier Business School, France) specialized in Open source software (OSS) and we...
I have a concern about Adobe's 7.2 approach, which amounts to "changing the standard to fit a particular tool functionality." This is potentially problematic...
... This ought to work, though I haven't tried it: Wrap dita2fo-shell.xsl in another shell. Create your own override.xsl file, and put in it something like: ...
In addition to Deborah's suggestion, if you always use the same options, you could pass those options in directly with your ANT build. Instead of relying on...
Thanks for the suggestions, Robert and Deborah. I know I can override these params by altering the build routine to either load a different xsl or to pass my...
After letting the comments settle down, it seemed that the concensus is that using the Sun JDK 1.5 would not break my OT 1.2.2 install, so I installed the...
Hi David - Typically we use the required-cleanup element for such items (and do not consider it abuse...) The required cleanup contains information that needs...
Hope this makes sense but suppose you have a topic that you only want to make avialable to a specific audience, you could apply the audience metadata element...
