dita-users Yahoo! Group
Re: DITA 1.2 Spec production data
... Why? It seems to take a long time to process some very small files with very simple relationships? If it FOP or DITA that is causing the problem? I know
Re: DITA 1.2 Spec production data
Having worked at one time on the FOP code base, I know that layout is inherently cpu intensive. ... This seems to defeat the purpose of SSD drives. Peter West
Re: <keydef> in submap not included in root maps key-space? Is this
On Wed, 29 May 2013 10:59:41 +0300, Jarno Elovirta ... I agree... if you are talking about a *silent* fix. Nobody in their right mind would dispute that. But
Re: nested elements in keydefs
You would have to integrate the UI domain into your map shell, but having done so, it should be possible to put any specialization of (including
Re: specialize attribute for <entry>?
Hi Leigh, You should be able to use @base for the same purpose. Best, Sev ________________________________ From: Leigh White To:
specialize attribute for <entry>?
I had grand plans for specializing an attribute specifically for rotating text in elements. I had it working with @outputclass but wanted something
nested elements in keydefs
Hi all...I have a writer who's trying to stretch the boundaries of keydef to avoid using ditaval filtering. Long story short, he wants to create keydefs that
Re: Index problem - Who has texts translated into Japanese?
Hi Joe, Just to make sure that I understand you correctly: Do you mean that the + elements should look as follows in the XML before
Re: DITA 1.2 Spec production data
I feel that the initial parsing phase really benefits but some of the later steps (FOP) still seem to be slow. It appears that some of this processing is CPU
Re: <keydef> in submap not included in root maps key-space? Is this
I agree with George here. It's nice to have lax parsers and it's convenient to use them when your source material is broken. But, the old "crap in, crap out"
Re: DITA 1.2 Spec production data
My small tests indicate that a RAM drive on an OS X is not that much faster than an SSD. However, because writing on an SSD will wear the drive, using a RAM
Re: group of elements under one id for conref?
HI, You can also use the conref and conrefend attributes to conref a sequence of elements see http://ditaspec.suite-sol.com/common/theconrefendattribute.html
Re: <keydef> in submap not included in root maps key-space? Is this
Thanks for the reference Alan! And Jeremy, there is the Lightweight DITA project of course: http://www.slideshare.net/mpriestley/lw-dita20130424 Mark
Re: <keydef> in submap not included in root maps key-space? Is this
I doubt anyone would like to have automatic fatal error recovery when they publish their airplane manual... Best Regards, George -- George Cristian Bina
Re: DITA 1.2 Spec production data
Caching of data by hard drives is a very well established practice and when you are purchasing a disk, one of the specifications that determines the price is
Re: DITA 1.2 Spec production data
I don't expect that caching would make any difference. It would be dangerous to cache a hard disc with volatile memory, so I assume something like flash is
Re: DITA 1.2 Spec production data
Another good acceleration idea! I would expect that an SSD would be faster since it would have some internal caching and a higher speed of data transfer but
Re: <keydef> in submap not included in root maps key-space? Is this
... LOL! Go for it! ;-) ... Yes, that's right. And note that in the 5th edition, the Status section at the start says: As a consequence, many possible
Re: group of elements under one id for conref?
On Tue, 28 May 2013 14:21:56 -0700, Alex Escott ... Not only that, looking at the content model more closely, the itself needs to be inside a
Re: DITA 1.2 Spec production data
What about mounting a 32Gb usb3 stick as your working drive (assuming a machine with usb3.) That should give an idea of the improvement possible with an SSD