Hi Jean,

I found the thread in my archive. I enclose it here.

Thanks,
Dag


--- Begin Message ---
--- Begin Message ---
Topics:
   Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)
   Re: Derby HTML book manuals - invalid anchors in TOC? (DERBY-753)

--- End Message ---
--- Begin Message ---
Hello,

Some time ago I created DERBY-753 
(http://issues.apache.org/jira/browse/DERBY-753), but there has not been 
any activity on it since then. It says that the links in the table of 
contents of the HTML book manuals do not work.

Can anyone confirm that the problem (still) exists?




thanks,
--
Kristian



--- End Message ---
--- Begin Message ---
Kristian Waagan wrote:
> Hello,
> 
> Some time ago I created DERBY-753 
> (http://issues.apache.org/jira/browse/DERBY-753), but there has not been 
> any activity on it since then. It says that the links in the table of 
> contents of the HTML book manuals do not work.
> 
> Can anyone confirm that the problem (still) exists?

I can confirm that the problem still exists with the 10.2 reference manual. I 
have not tried the others.

I also tried the link (from the Jira issue) that was supposed to work, but it 
did not work either. I.e.:

http://db.apache.org/derby/docs/dev/ref/ref-single.html#crefsqlj95081

does not work;

http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1223F

does not work; but

http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1227F

works.


-- 
John



--- End Message ---
--- Begin Message ---
John Embretsen wrote:
> Kristian Waagan wrote:
>> Hello,
>>
>> Some time ago I created DERBY-753 
>> (http://issues.apache.org/jira/browse/DERBY-753), but there has not 
>> been any activity on it since then. It says that the links in the 
>> table of contents of the HTML book manuals do not work.
>>
>> Can anyone confirm that the problem (still) exists?
> 
> I can confirm that the problem still exists with the 10.2 reference 
> manual. I have not tried the others.
> 
> I also tried the link (from the Jira issue) that was supposed to work, 
> but it did not work either. I.e.:
> 
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#crefsqlj95081
> 
> does not work;
> 
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1223F
> 
> does not work; but
> 
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1227F
> 
> works.
> 
> 

Okay, thanks for confirming the problem.
For the links, the point was to illustrate that there are anchors in the 
files, but they are not used. To me, it looks like there has been some 
kind of mapping error or something during the build process.

I do not know how the anchors are defined and how the documentation 
build process works. Can anyone with more Derby documentation building 
experience see the reason for this problem?


Since I believe we don't exactly score "Top rated" on our documentation, 
I would say this problem should be fixed pretty quickly! It hinders 
navigation severely.



--
Kristian



--- End Message ---
--- Begin Message ---
I can tell you that this is a problem that could be
hard to fix.  The single-html books are not a normal
result of the DITA transform.  However, some time ago
Andrew found an xsl file on the web that we were able
to use to transform the half-processed PDF transforms
from the DITA process and convert them to html. 
Unfortunately, since that XSL file came from outside
of DITA, it is not supported by their project.  If
someone has time they can try to modify that xsl file
to fix this problem, but I think the single-html files
were put in place as sort of a bonus when Andrew found
that xsl file, so I wouldnt expect to see as much
progress on the quality of those books as the other
two types of output, unless someone else knows what
they are doing and can fix this (I dont!) :)

Also, Andrew, do you know if the xsl file is legally
modifiable?


--- Kristian Waagan <[email protected]> wrote:

> John Embretsen wrote:
> > Kristian Waagan wrote:
> >> Hello,
> >>
> >> Some time ago I created DERBY-753 
> >> (http://issues.apache.org/jira/browse/DERBY-753),
> but there has not 
> >> been any activity on it since then. It says that
> the links in the 
> >> table of contents of the HTML book manuals do not
> work.
> >>
> >> Can anyone confirm that the problem (still)
> exists?
> > 
> > I can confirm that the problem still exists with
> the 10.2 reference 
> > manual. I have not tried the others.
> > 
> > I also tried the link (from the Jira issue) that
> was supposed to work, 
> > but it did not work either. I.e.:
> > 
> >
>
http://db.apache.org/derby/docs/dev/ref/ref-single.html#crefsqlj95081
> > 
> > does not work;
> > 
> >
>
http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1223F
> > 
> > does not work; but
> > 
> >
>
http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1227F
> > 
> > works.
> > 
> > 
> 
> Okay, thanks for confirming the problem.
> For the links, the point was to illustrate that
> there are anchors in the 
> files, but they are not used. To me, it looks like
> there has been some 
> kind of mapping error or something during the build
> process.
> 
> I do not know how the anchors are defined and how
> the documentation 
> build process works. Can anyone with more Derby
> documentation building 
> experience see the reason for this problem?
> 
> 
> Since I believe we don't exactly score "Top rated"
> on our documentation, 
> I would say this problem should be fixed pretty
> quickly! It hinders 
> navigation severely.
> 
> 
> 
> --
> Kristian
> 



--- End Message ---
--- Begin Message ---
Jeff Levitt wrote:
> I can tell you that this is a problem that could be
> hard to fix.  The single-html books are not a normal
> result of the DITA transform.  However, some time ago
> Andrew found an xsl file on the web that we were able
> to use to transform the half-processed PDF transforms
> from the DITA process and convert them to html. 
> Unfortunately, since that XSL file came from outside
> of DITA, it is not supported by their project.  If
> someone has time they can try to modify that xsl file
> to fix this problem, but I think the single-html files
> were put in place as sort of a bonus when Andrew found
> that xsl file, so I wouldnt expect to see as much
> progress on the quality of those books as the other
> two types of output, unless someone else knows what
> they are doing and can fix this (I dont!) :)
> 
> Also, Andrew, do you know if the xsl file is legally
> modifiable?
> 


I had a look at this. The XSL file "fo2html.xsl" comes from 
www.renderx.com. I downloaded a copy (it is free) and compared it to the 
one in our repos. They are identical, so nothing has been updated. 
Although I had to obtain a license to download the XSL file, the 
following is stated in the XSL file itself:

<!-- =============================================================== -->
<!--                                                                 -->
<!-- Convert XSL FO (as in REC 2001-10-15) to HTML                   -->
<!--                                                                 -->
<!-- © RenderX 2000-2001                                             -->
<!-- Permission to copy and modify is granted, provided this notice  -->
<!-- is included in all copies and/or derived work.                  -->
<!--                                                                 -->
<!-- Author: Nikolai Grigoriev, [email protected]                     -->
<!--                                                                 -->
<!-- =============================================================== -->


Just for completeness, my (modified) 'license.xml' looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<license issuer="RenderX" issued="2006-02-28">
    <licensee>
       <person>My Name</person>
       <organization/>
    </licensee>
    <product name="Fo2Html">
       <limit name="full">1</limit>
    </product>
<signature>[snipped]</signature></license>

Don't know if you need to have this around, or if it is only a mean to 
trace/control downloads.


I'm thinking about updating the Jira issue (DERBY-753) with some 
information and maybe resolve/close it, but I will wait a little longer 
to see if anyone else has something to add to this topic.



--
Kristian


> 
> --- Kristian Waagan <[email protected]> wrote:
> 
>> John Embretsen wrote:
>>> Kristian Waagan wrote:
>>>> Hello,
>>>>
>>>> Some time ago I created DERBY-753 
>>>> (http://issues.apache.org/jira/browse/DERBY-753),
>> but there has not 
>>>> been any activity on it since then. It says that
>> the links in the 
>>>> table of contents of the HTML book manuals do not
>> work.
>>>> Can anyone confirm that the problem (still)
>> exists?
>>> I can confirm that the problem still exists with
>> the 10.2 reference 
>>> manual. I have not tried the others.
>>>
>>> I also tried the link (from the Jira issue) that
>> was supposed to work, 
>>> but it did not work either. I.e.:
>>>
>>>
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#crefsqlj95081
>>> does not work;
>>>
>>>
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1223F
>>> does not work; but
>>>
>>>
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1227F
>>> works.
>>>
>>>
>> Okay, thanks for confirming the problem.
>> For the links, the point was to illustrate that
>> there are anchors in the 
>> files, but they are not used. To me, it looks like
>> there has been some 
>> kind of mapping error or something during the build
>> process.
>>
>> I do not know how the anchors are defined and how
>> the documentation 
>> build process works. Can anyone with more Derby
>> documentation building 
>> experience see the reason for this problem?
>>
>>
>> Since I believe we don't exactly score "Top rated"
>> on our documentation, 
>> I would say this problem should be fixed pretty
>> quickly! It hinders 
>> navigation severely.
>>
>>
>>
>> --
>> Kristian
>>
> 



--- End Message ---
--- Begin Message ---
Kristian Waagan wrote:
> Jeff Levitt wrote:
> 
>> I can tell you that this is a problem that could be
>> hard to fix.  The single-html books are not a normal
>> result of the DITA transform.  However, some time ago
>> Andrew found an xsl file on the web that we were able
>> to use to transform the half-processed PDF transforms
>> from the DITA process and convert them to html. Unfortunately, since
>> that XSL file came from outside
>> of DITA, it is not supported by their project.  If
>> someone has time they can try to modify that xsl file
>> to fix this problem, but I think the single-html files
>> were put in place as sort of a bonus when Andrew found
>> that xsl file, so I wouldnt expect to see as much
>> progress on the quality of those books as the other
>> two types of output, unless someone else knows what
>> they are doing and can fix this (I dont!) :)
>>
>> Also, Andrew, do you know if the xsl file is legally
>> modifiable?
>>
> 
> 
> I had a look at this. The XSL file "fo2html.xsl" comes from
> www.renderx.com. I downloaded a copy (it is free) and compared it to the
> one in our repos. They are identical, so nothing has been updated.
> Although I had to obtain a license to download the XSL file, the
> following is stated in the XSL file itself:
> 
> <!-- =============================================================== -->
> <!--                                                                 -->
> <!-- Convert XSL FO (as in REC 2001-10-15) to HTML                   -->
> <!--                                                                 -->
> <!-- © RenderX 2000-2001                                             -->
> <!-- Permission to copy and modify is granted, provided this notice  -->
> <!-- is included in all copies and/or derived work.                  -->
> <!--                                                                 -->
> <!-- Author: Nikolai Grigoriev, [email protected]                     -->
> <!--                                                                 -->
> <!-- =============================================================== -->
> 
> 
> Just for completeness, my (modified) 'license.xml' looks like this:
> <?xml version="1.0" encoding="UTF-8"?>
> <license issuer="RenderX" issued="2006-02-28">
>    <licensee>
>       <person>My Name</person>
>       <organization/>
>    </licensee>
>    <product name="Fo2Html">
>       <limit name="full">1</limit>
>    </product>
> <signature>[snipped]</signature></license>
> 
> Don't know if you need to have this around, or if it is only a mean to
> trace/control downloads.
> 
> 
> I'm thinking about updating the Jira issue (DERBY-753) with some
> information and maybe resolve/close it, but I will wait a little longer
> to see if anyone else has something to add to this topic.
> 
> 

Info needs to be added to the derby/docs/trunk documenting where files
came from outside the ASF.

What's the history behind fo2html.xsl getting committed to the Derby
repo? I keep thinking I should know that, but I'm drawing a blank. Also,
lib/dita2fo-shell.xsl is from the DITA toolkit, which is under the ASL
license, but that isn't readily apparent from looking at that file in
the Derby repo.

I'm not suggesting anything is wrong, but it's important to track where
files came from and the licenses in effect for them.

-jean



--- End Message ---
--- Begin Message ---
On 2/28/06, Jean T. Anderson <[email protected]> wrote:
>
> Info needs to be added to the derby/docs/trunk documenting where files
> came from outside the ASF.
>
> What's the history behind fo2html.xsl getting committed to the Derby
> repo? I keep thinking I should know that, but I'm drawing a blank. Also,
> lib/dita2fo-shell.xsl is from the DITA toolkit, which is under the ASL
> license, but that isn't readily apparent from looking at that file in
> the Derby repo.
>
> I'm not suggesting anything is wrong, but it's important to track where
> files came from and the licenses in effect for them.

Sorry it's taken me so long to follow up on this, it took me a while
to find the original post to fop-user from which I found this. The
file itself was linked from a site posted to the FOP users lists
asking about how to turn XML-FO into html:

http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200503.mbox/%3c422ECBC1.15336.7498F0@localhost%3e

I never agreed to a license to get the file, and in the file itself,
which I got from the site linked in the original mail to fop-user, it
is clearly marked "Permission to copy and modify is granted, provided
this notice is included" and then attributes authorship. Essentially
an ultra-brief BSD license, this statement appears in 4 different
identical copies of the file that I've found online, so it appears to
be the original document. Certainly "permission to copy and modify" is
sufficient to be allowed to put it in the repo?

The file is also freely available from a half dozen other sites
related to FOP, and in a half dozen other open source repositories,
including at least three CVS trees at sourceforge alone. If you're
still concerned, though, despite the fact that the file is clearly
marked "Permission to copy and modify, etc." then do please remove it.
I'll subsequently disable the "HTML Book" builds for the docs.

thanks,
andrew



--- End Message ---
--- Begin Message ---
Andrew McIntyre wrote:
> On 2/28/06, Jean T. Anderson <[email protected]> wrote:
> 
>>Info needs to be added to the derby/docs/trunk documenting where files
>>came from outside the ASF.
>>
>>What's the history behind fo2html.xsl getting committed to the Derby
>>repo? I keep thinking I should know that, but I'm drawing a blank. Also,
>>lib/dita2fo-shell.xsl is from the DITA toolkit, which is under the ASL
>>license, but that isn't readily apparent from looking at that file in
>>the Derby repo.
>>
>>I'm not suggesting anything is wrong, but it's important to track where
>>files came from and the licenses in effect for them.
> 
> 
> Sorry it's taken me so long to follow up on this, it took me a while
> to find the original post to fop-user from which I found this. The
> file itself was linked from a site posted to the FOP users lists
> asking about how to turn XML-FO into html:
> 
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200503.mbox/%3c422ECBC1.15336.7498F0@localhost%3e
> 
> I never agreed to a license to get the file, and in the file itself,
> which I got from the site linked in the original mail to fop-user, it
> is clearly marked "Permission to copy and modify is granted, provided
> this notice is included" and then attributes authorship. Essentially
> an ultra-brief BSD license, this statement appears in 4 different
> identical copies of the file that I've found online, so it appears to
> be the original document. Certainly "permission to copy and modify" is
> sufficient to be allowed to put it in the repo?
> 
> The file is also freely available from a half dozen other sites
> related to FOP, and in a half dozen other open source repositories,
> including at least three CVS trees at sourceforge alone. If you're
> still concerned, though, despite the fact that the file is clearly
> marked "Permission to copy and modify, etc." then do please remove it.
> I'll subsequently disable the "HTML Book" builds for the docs.


Did fop commit this file to their asf repo? or do they just provide
instructions on where to obtain it? If FOP includes it, no problem, we
just get it from FOP and cite that in a NOTICES file that we add to the
doc trunk. If FOP doesn't include it, it would be interesting to
understand why.

 -jean



--- End Message ---
--- Begin Message ---
I haven't looked at that file, but looking at the fop output, in the 
getstarted file, bookmarks exist, which are not supported (from what I 
saw) in the fo2xhtml.xsl file.

<fo:block margin-left="9pc" text-align-last="justify">
<fo:basic-link internal-destination="tgsrunningij">Running ij<fo:leader 
leader-pattern="dots"/>
<fo:page-number-citation ref-id="N105D5"/>
</fo:basic-link>
</fo:block>

You will find that the basic-link doesn't have any internal-destination, 
although it does have the page-number-citation ref-id.

<fox:bookmark internal-destination="N105D6">
<fox:label>Running ij</fox:label>
</fox:bookmark>

<fo:inline id="N105D6"/>Running ij</fo:block>

Although I think it has a off-by-one error in the fo:block with the 
basic-link and the page-number-citation ref-id, which I am fairly 
certain at one time or another, some of the dita transforms were off by 
1.  So it looks like if we used the bookmarks (implemented them in 
fo2html.xsl) then the links would work.  Sound reasonable?

This is just a quick fix, and I haven't looked at it enough to make sure 
it works, it just looks like it would.  More than likely, some other 
items need fixed in the transform to fop, which should be fixed first.

scott



John Embretsen wrote:
> Kristian Waagan wrote:
>> Hello,
>>
>> Some time ago I created DERBY-753 
>> (http://issues.apache.org/jira/browse/DERBY-753), but there has not 
>> been any activity on it since then. It says that the links in the 
>> table of contents of the HTML book manuals do not work.
>>
>> Can anyone confirm that the problem (still) exists?
>
> I can confirm that the problem still exists with the 10.2 reference 
> manual. I have not tried the others.
>
> I also tried the link (from the Jira issue) that was supposed to work, 
> but it did not work either. I.e.:
>
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#crefsqlj95081
>
> does not work;
>
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1223F
>
> does not work; but
>
> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1227F
>
> works.
>
>



--- End Message ---
--- Begin Message ---
BTW, I think from what I have looked at, that it's best to fix the 
original problem rather than hack in fox (fop extensions), put titles in 
the fop output etc...

scott

scott hutinger wrote:
> I haven't looked at that file, but looking at the fop output, in the 
> getstarted file, bookmarks exist, which are not supported (from what I 
> saw) in the fo2xhtml.xsl file.
>
> <fo:block margin-left="9pc" text-align-last="justify">
> <fo:basic-link internal-destination="tgsrunningij">Running 
> ij<fo:leader leader-pattern="dots"/>
> <fo:page-number-citation ref-id="N105D5"/>
> </fo:basic-link>
> </fo:block>
>
> You will find that the basic-link doesn't have any 
> internal-destination, although it does have the page-number-citation 
> ref-id.
>
> <fox:bookmark internal-destination="N105D6">
> <fox:label>Running ij</fox:label>
> </fox:bookmark>
>
> <fo:inline id="N105D6"/>Running ij</fo:block>
>
> Although I think it has a off-by-one error in the fo:block with the 
> basic-link and the page-number-citation ref-id, which I am fairly 
> certain at one time or another, some of the dita transforms were off 
> by 1.  So it looks like if we used the bookmarks (implemented them in 
> fo2html.xsl) then the links would work.  Sound reasonable?
>
> This is just a quick fix, and I haven't looked at it enough to make 
> sure it works, it just looks like it would.  More than likely, some 
> other items need fixed in the transform to fop, which should be fixed 
> first.
>
> scott
>
>
>
> John Embretsen wrote:
>> Kristian Waagan wrote:
>>> Hello,
>>>
>>> Some time ago I created DERBY-753 
>>> (http://issues.apache.org/jira/browse/DERBY-753), but there has not 
>>> been any activity on it since then. It says that the links in the 
>>> table of contents of the HTML book manuals do not work.
>>>
>>> Can anyone confirm that the problem (still) exists?
>>
>> I can confirm that the problem still exists with the 10.2 reference 
>> manual. I have not tried the others.
>>
>> I also tried the link (from the Jira issue) that was supposed to 
>> work, but it did not work either. I.e.:
>>
>> http://db.apache.org/derby/docs/dev/ref/ref-single.html#crefsqlj95081
>>
>> does not work;
>>
>> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1223F
>>
>> does not work; but
>>
>> http://db.apache.org/derby/docs/dev/ref/ref-single.html#N1227F
>>
>> works.
>>
>>
>



--- End Message ---
-- 

--- End Message ---

Reply via email to