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 deprecated. The
ooDialog framework no longer makes a dist
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 passe
On Wed, Mar 3, 2010 at 11:15 AM, Rick McGuire wrote:
> On Wed, Mar 3, 2010 at 2:13 PM, David Ashley
> wrote:
>>
>> There are some mass updates I want to perform to the ooRexx
>> Documentation. None of them are critical but they will make thing a
>> little easier and more obvious to the uninitiat
On Wed, Mar 3, 2010 at 2:13 PM, David Ashley wrote:
> All -
>
> There are some mass updates I want to perform to the ooRexx
> Documentation. None of them are critical but they will make thing a
> little easier and more obvious to the uninitiated.
>
> 1. Rename all files to have an .xml suffix inst
All -
There are some mass updates I want to perform to the ooRexx
Documentation. None of them are critical but they will make thing a
little easier and more obvious to the uninitiated.
1. Rename all files to have an .xml suffix instead of an .sgml suffix.
2. Add an id to all title tags.
3. Fix
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 M
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
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 bo
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
> and spe
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
and specify the draft option to hyperref so you get an output PDF.
Then y
Once again I'm having lots of problems with updating the ooDialog
documentation. It's that stupid end link ended up at a different
nesting level than the start link.
The last time this happened, it took me days to fix it.
David, is there any way to figure out where in the text this is
happening
11 matches
Mail list logo
