I'm moving this discussion over from the derby-user list, as it
looks like a problem that originated during the documentation build
for the 10.3 docs.
If you look at the generated 10.3 HTML pages, such as:
http://db.apache.org/derby/docs/10.3/tuning/ttundepth34375.html
and look in the page source, you'll see:
<link href="/export/home/rh161140/derby/docs/10.3/out/tuningtemp/commonltr.css"
type="text/css" rel="stylesheet" />
That CSS reference is to a file system path name, when it should be to
some sort of relative URL that resolves to a CSS file on
http://db.apache.org
Is this already a known, logged problem? Or should I log a new JIRA?
Note that the 10.2 docs are similar; they contain:
<link href="/export/home/rh161140/derby/docs/10.2/out/tuningtemp/commonltr.css"
type="text/css" rel="stylesheet" />
The 10.1 docs, however, contain:
<link href="commonltr.css" type="text/css" rel="stylesheet" />
But even though that resolves to a more reasonable CSS link:
http://db.apache.org/derby/docs/10.1/tuning/commonltr.css
That CSS URL still does not seem to reference an actual stylesheet.
thanks,
bryan
--- Begin Message ---
caston first, 30.09.2007 14:40:
I am reading the HTML PAGES dev guide, and every time
there is a reference to an actual code item in-line
with text (in Courier font), it is an obfuscated
(meaningless) word, viz.:
This base text (as a result of a copy operation):
The standard way to obtain a Connection object is to
call the method DriverManager.getConnection, which
takes a String
appears in Safari (Mac OS X, 10.4.10) as in the
attached image. In fact, I didn't know the text would
paste correctly when I started this note! Hmmm...
The HTML coce seems to be correct:
<p>The standard way to obtain a <samp
class="codeph"><em>Connection</em></samp> object
is to call the method <samp
class="codeph"><em>DriverManager.getConnection</em></samp>
But I have noticed that the reference to the css in the header is incorrect:
<link
href="/export/home/rh161140/derby/docs/10.3/out/devguidetemp/commonltr.css"
type="text/css" rel="stylesheet" />
this is taken from the 10.3 distribution archive.
As no css files are part of the distribution, the reference does not
make sense (a relative path would make sense if the css files were
included in the archive).
But maybe on your computere the referenced .css file does indeed exist
and defines a font which causes the garbled output.
Thomas
--- End Message ---
