Re: [Oorexx-devel] (Solved) docbook and ooDialog documentation problems
David,
Thanks, that's a good solution. We all live and learn.
As you'll see in a later post I made, my biggest problem was finding
*which* link was the problem one. I finally figured out how to do
that.
Your solution is a good one to know about. That should help me in the future.
--
Mark Miesfeld
On Wed, Mar 3, 2010 at 9:53 AM, David Ashley wrote:
> There is a way to fix this problem. Unfortunately it would require a LOT
> OF WORK to fix it for everything abd every possibility. And I will take
> the blame for this one. I did not realize when I first started to
> convert the dosuments to sgml/xml that this problem was possible, but
> live an learn I guess.
>
> In any case here is the solution.
>
> First, change the target of a link from its current form. here is an
> example.
>
> This is the original version.
>
> AdvancedControls Class
>
> Here is the modified version.
>
> id="clsAdvancedControls.title">AdvancedControls Class
>
> The label is the text you want to use to refer to the chapter/section.
>
> Now change the link.
>
> Here is an original example.
>
> See the chapter Advanced
> Controls for more information.
>
> Here is the corrected example.
>
> See the chapter endterm="clsAdvancedControls.title" /> for more information.
>
> Note that the endterm causes the text of the title to be substituted at
> the link's location. Thus there is no text that will cross a page
> boundary. This technique can be used on any tag and has the added
> benefits in the output pdf. This should have been the methodology used
> from the very beginning, but I didn't know enough at the time to add
> this little magic. In any case, feel free to fix things using this
> methodology as they come up.
>
> David Ashley
>
> On 03/03/2010 11:08 AM, Mark Miesfeld wrote:
>> On Wed, Mar 3, 2010 at 8:24 AM, Mark Miesfeld wrote:
>>
>>> On Wed, Mar 3, 2010 at 8:00 AM, Mark Miesfeld wrote:
>>>
>>>
Looking back at the last time I posted about this, I see that there is
this solution:
This happens when hyperref is used under pdftex and a citation splits
across a page boundary. To fix it, note the page number of the error
>> Okay, I got this fixed. Here's the solution in case any one else runs
>> into this.
>>
>> When the build finishes with this error there will be an *.out file.
>> oodialog.out in this case, I'm assuming it would be rexxref.out or
>> rexxpg.out, etc..
>>
>> I catted oodialog.out and the last lines look like this:
>>
>> \BOOKMARK [3][-]{10.68.422.19.3}{7.9.1.2. addButton}{10.68.422.2}
>> \BOOKMARK [3][-]{10.68.422.20.3}{7.9.1.3. addBitmapButton}{10.68.422.2}
>>
>> I then went to the *.sgml file for the addBitmapButton section. For
>> the links in that section, I changed any that were more than 1 word,
>> to just be 1 word. On the premise that a 1 word link would not cross
>> a page boundry. Like this:
>>
>> image list
>>
>> changed to:
>>
>> image list
>>
>> That worked.
>>
>> Of course, I'd really like the link above to use the two words. And I
>> changed about 4 links in the section when it was probably only 1 link
>> that needed to be changed. But, at least this is a pretty quick way
>> to go forward.
>>
>> In general, I guess only using 1 word in any link would probably
>> prevent this error.
>>
>> --
>> Mark Miesfeld
>>
>> --
>> 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
>
--
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
Re: [Oorexx-devel] (Solved) docbook and ooDialog documentation problems
There is a way to fix this problem. Unfortunately it would require a LOT
OF WORK to fix it for everything abd every possibility. And I will take
the blame for this one. I did not realize when I first started to
convert the dosuments to sgml/xml that this problem was possible, but
live an learn I guess.
In any case here is the solution.
First, change the target of a link from its current form. here is an
example.
This is the original version.
AdvancedControls Class
Here is the modified version.
AdvancedControls Class
The label is the text you want to use to refer to the chapter/section.
Now change the link.
Here is an original example.
See the chapter Advanced
Controls for more information.
Here is the corrected example.
See the chapter for more information.
Note that the endterm causes the text of the title to be substituted at
the link's location. Thus there is no text that will cross a page
boundary. This technique can be used on any tag and has the added
benefits in the output pdf. This should have been the methodology used
from the very beginning, but I didn't know enough at the time to add
this little magic. In any case, feel free to fix things using this
methodology as they come up.
David Ashley
On 03/03/2010 11:08 AM, Mark Miesfeld wrote:
> On Wed, Mar 3, 2010 at 8:24 AM, Mark Miesfeld wrote:
>
>> On Wed, Mar 3, 2010 at 8:00 AM, Mark Miesfeld wrote:
>>
>>
>>> Looking back at the last time I posted about this, I see that there is
>>> this solution:
>>>
>>> This happens when hyperref is used under pdftex and a citation splits
>>> across a page boundary. To fix it, note the page number of the error
>>>
> Okay, I got this fixed. Here's the solution in case any one else runs
> into this.
>
> When the build finishes with this error there will be an *.out file.
> oodialog.out in this case, I'm assuming it would be rexxref.out or
> rexxpg.out, etc..
>
> I catted oodialog.out and the last lines look like this:
>
> \BOOKMARK [3][-]{10.68.422.19.3}{7.9.1.2. addButton}{10.68.422.2}
> \BOOKMARK [3][-]{10.68.422.20.3}{7.9.1.3. addBitmapButton}{10.68.422.2}
>
> I then went to the *.sgml file for the addBitmapButton section. For
> the links in that section, I changed any that were more than 1 word,
> to just be 1 word. On the premise that a 1 word link would not cross
> a page boundry. Like this:
>
> image list
>
> changed to:
>
> image list
>
> That worked.
>
> Of course, I'd really like the link above to use the two words. And I
> changed about 4 links in the section when it was probably only 1 link
> that needed to be changed. But, at least this is a pretty quick way
> to go forward.
>
> In general, I guess only using 1 word in any link would probably
> prevent this error.
>
> --
> Mark Miesfeld
>
> --
> 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
Re: [Oorexx-devel] (Solved) docbook and ooDialog documentation problems
On Wed, Mar 3, 2010 at 8:24 AM, Mark Miesfeld wrote:
> On Wed, Mar 3, 2010 at 8:00 AM, Mark Miesfeld wrote:
>
>> Looking back at the last time I posted about this, I see that there is
>> this solution:
>>
>> This happens when hyperref is used under pdftex and a citation splits
>> across a page boundary. To fix it, note the page number of the error
Okay, I got this fixed. Here's the solution in case any one else runs
into this.
When the build finishes with this error there will be an *.out file.
oodialog.out in this case, I'm assuming it would be rexxref.out or
rexxpg.out, etc..
I catted oodialog.out and the last lines look like this:
\BOOKMARK [3][-]{10.68.422.19.3}{7.9.1.2. addButton}{10.68.422.2}
\BOOKMARK [3][-]{10.68.422.20.3}{7.9.1.3. addBitmapButton}{10.68.422.2}
I then went to the *.sgml file for the addBitmapButton section. For
the links in that section, I changed any that were more than 1 word,
to just be 1 word. On the premise that a 1 word link would not cross
a page boundry. Like this:
image list
changed to:
image list
That worked.
Of course, I'd really like the link above to use the two words. And I
changed about 4 links in the section when it was probably only 1 link
that needed to be changed. But, at least this is a pretty quick way
to go forward.
In general, I guess only using 1 word in any link would probably
prevent this error.
--
Mark Miesfeld
--
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
