... Hi Eliot, thanks for this information. I found discussion and wrote to TC list as well. ... I see, but I think that I could live with fixed prefixes here.

I believe this belongs in the actual topicref that wraps its child topicrefs, not in the relationship table. The reltable only creates the relationship table

Hi, I might be misunderstanding something. I have the following reltable row:

There is no legal mechanism to do this. The TC did recently discuss the ITS vocabulary and whether or not it was useful to allow it to be included in DITA--I

Hi, How are you processing this in the second case? If you're going to PDF, then what you've specified won't work. You're probably better off using flagging in

We are in the process of implementing a RelaxNG-to-DITA-DTD transform and it's pretty close. The project is here: http://code.google.com/p/dita-ng/ and people

Hi, I have to integrate ITS 2.0 (http://www.w3.org/TR/its20/) into DITA. ITS consist of several attributes and elements in ITS namespace which can be used on

... I think that you can easily disable any DITA element if you will use DITA-NG (http://code.google.com/p/dita-ng/) -- RELAX NG based definition of DITA. You

Hi Nuesel, When you edited commonltr.css, you only made formatting changes to for online outputs. It sounds like you want to make these same changes in

Thanks. I have broken my OT and will have to figure out what has gone wrong first. thanks for the information. /Kevin

Hello, I added the following line .prog_example {color:green; font-family:"Courier New";} to the file "DITA-OT/resource/commonltr.css". In a related DITA topic

... First, you should setup fonts in XEP. If sample xep.xml was not enough for you, can read XEP documentation:

Hi, Yes, I signed up for Gittip in case someone was interested donating. Note that if you're interested in donating via Gittip, it's a *weekly gift*, not a

That's definitely an option. This came up as part of a general discussion about removing some elements that people aren't using or for which we currently don't

There is no easy way to remove a base element type without replacing it with something else. That is, it's legal to do: Which

Is there an official way to globally remove a given base DITA element from a topic type without redefining each and every ____.content entity for whichever

I'd imagine that you'd want the encoding to be UTF-8, as that is required by DITA, and not iso-8859-2.

Sorry it took a while to get back, but other tasks had me occupied. I did as you instructed and added

Thanks for posting this, Michael. I assumed (wrongly) that he was being compensated for most of his work. I'm sure I wasn't the only one who made this

That's very cool. I've signed up. Would be nice if we, as a community, could find a way to support Jarno to an even greater degree, but this is a good start.