Forums Let Customers, Partners and Internal Services Team Share Tips and Best Practices for XMetaL Deployments
Archive - Nov 2008
Brushing your teeth with DITA: Leveraging relationships to improve usability
Presentation at the 28 May 2008 meeting of the RTP DITA Users' Group by Shane Taylor, Computer Task Group. Originally presented at DITA 2006 by Shane Taylor and Karen Mobley (IBM).
JustSystems Unveils XMetaL Community Forums
Michael Priestley
DITA visual editing in Eclipse with Vex
Just wanted to draw folks' attention to a new Eclipse project: Vex, a visual XML editor.
While they mention DITA as one of the goals for the project, I'm not sure that they have DITA skills currently on the contributing team, so I know they could use help.
If you're using Eclipse currently for DITA, or just like the idea of an open-source visual editor for DITA, I encourage you to go over and contribute your support in whatever way you can: encouragement, ideas, and most importantly the skills and time to help develop and document the new project.
inclusion path
I'm wondering if it is simple to ask a processing engine to search for included resources through several paths rather than just the base path of the document being processed. E.g., suppose a processor encounters
<synph conref="../foo/bar.xml#here">xxx</synph>
Why the acronym tags?
One thing keeps bugging me about DITA... Why are a lot of tags acronyms and not natural language? Language is a code for people to learn (as we all know). So why put another code (the acronyms) on top of that? It only serves to complicate the accessibility of DITA. It doesn't seem very DITAish to overcomplicate things like that.
The corporate world suffers from the Acronym Disease, but I would think that professional communicators like us tech writers, would be clever enough to avoid this kind of exclusion and inaccessibility.