The only problem I see with this is that in the ooDialog documentation the text I use in the link is very often either not a title, or not the text of the title. At least in the documentation I'm writing myself.
For example: This class is <link linkend="ovvDeprecated">deprecated</link>. The ooDialog framework <link linkend="sctHistory">no longer</link> makes a distinction between some types of dialog controls Neither of those links would work for that type of transformation. We'd get a sentence like: The ooDialog framework History makes a distinction between some types of dialog controls. I rarely write: See xxx We could see how it works though. Yesterday I would have jumped at this. <grin> But now that I know how to locate the offending hyperref, my frustration has eased considerably. -- Mark Miesfeld On Wed, Mar 3, 2010 at 2:22 PM, Jean-Louis Faucher <jfaucher...@gmail.com> wrote: > The number of links to update seems high (I found more than 2000 linkend in > oodialog, assuming all are candidate for update). Proposition : I can > modify the script transformdir in DocMusings to apply these transformations > for endterm. > > By default, this script creates a clone of the directory passed as argument > (zero diff). I can add the option -endterm, and apply theses > transformations, described by David : > > Give an id "parentid.title" to each title (parent can be a chapter, a > section, ...). Ex : > > <chapter id="clsAdvancedControls"><title>AdvancedControls Class</title> > becomes : > <chapter id="clsAdvancedControls"><title > id="clsAdvancedControls.title">AdvancedControls Class</title> > > Add an attribute endterm to each link and remove the child text. Ex : > > <para>See the chapter <link linkend="clsAdvancedControls">Advanced > Controls</link> for more information.</para> > becomes : > <para>See the chapter <link linkend="clsAdvancedControls" > endterm="clsAdvancedControls.title" /> for more information.</para> > > That works only if the target of a linkend is always a title. If this is not > the case, then the doc build will complain and we can adapt the script to > support the other cases. > > Let me know if you are interested. > > Jean-Louis > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
