Hi Julio, ... Yes it's sure. company_logo ...

Hi Matt, Fortunately my user uses CMS and CMS publication manager check-outs the image files to the same folder with maps and topics. So the image/@href

How do you access that xpath from your stylesheet? I was trying to do this a while back but gave up. I'm currently using paths like this:

Hi Kris, ... Thank you for your suggestion. As logo and cover images are document level object I prefer to define them in bookmeta element. Currently I am

... I tend to agree with you, and with Kris. That's a reasonable distinction. Only trouble is, it's not what the spec *says*. There is a weak implication

... Is this a typo. It should be ant -f integrator.xml lax Jarno

Thank to all who replied to my question. So I'll choose . Perhaps a future DITA version will have an element of its own for

Hi Toshihiko, Did you have a keydef (or topicref with @processing-role='resource-only') in your map? If not that's why you didn't get the image to resolve. You

... Odd. That's not the way the other ditaval actions work, like exclusion. That doesn't exclude the TOC entry, it excludes the whole topic. Why wouldn't

OT 1.7.3. In a topic I have . When I generate a PDF (using FOP or XEP), I get the following error message (the PDF

Although the OT supports adding flagging attributes to a topicref, the flag is rendered (if at all) in links to the topic and not in the topic itself, which is

I think there is a semantic difference between text that a user enters () and a keypress (). In the latter case, the user is not

First Thanks to Peter, Mica, and all the others who helped me get DITA-OT up and running in Terminal on the Mac. I moved to DITA-OIT 1.7.2. I created a PDF

As I mentioned, I don't think either element is a perfect fit. However, I'd argue that pressing Enter on the keyboard or tapping Enter on a touchscreen is

On Mon, 08 Apr 2013 17:29:52 -0400, Kristen James Eberlein ... Really? The 1.2 spec says: The user input () element represents the text a user

I'd agree with Shane about preferring over for keyboard items. It *would* be useful for the core DITA standard to have elements to

We use and set our processing to display keyboard shortcuts in all caps, not bolded. Compare the descriptions of

... You want . -- Jeremy H. Griffith DITA2Go site: http://www.dita2go.com/

One approach might be to flag content in the short description rather than the title. As the short description applies to the entire topic, the flag

Hi group Yes, the ditaval syntax Kris suggested also works in oXygen 14.2 with the DITA-OT 1.6. This is what I'm using now: