Hi all,
I'm banging my head against the docs building problem and now I'm
getting this:
http://docbook.sourceforge.net/release/xsl/current/html/inline.xsl:1:
parser error : Start tag expected, '<' not found
HTTP/1.0 504 Gateway Time-out
^
compilation error: file http://docbook.sourceforge.net/release/xsl/
current/html/docbook.xsl line 50
element include
xsl:include : unable to load http://docbook.sourceforge.net/release/
xsl/current/html/inline.xsl
which I hadn't seen previously.
Any clues? Is this just a transient problem with sourceforge?
Cheers,
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"OS X is great that way. I put a copy of OS X on my coffee table,
and it hasn't been hacked yet. Yes, I am using it as a server. I
serve several meals on it every week." -- Anthony Minkoff
Erik de Castro Lopo wrote:> Is this just a transient problem with sourceforge?Yes, a transitory problem. Erik -- ----------------------------------------------------------------- Erik de Castro Lopo ----------------------------------------------------------------- "These are the finest moments in (post)modern life, when satire is completly indistinguishable from reality... I usually have to rely on the presidential elections for such dada." -- frenomulax on Jesux a christian Linux distro.
On Sat, Feb 7, 2009 at 4:57 PM, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote:> I'm banging my head against the docs building problem and now I'm > getting this: > > http://docbook.sourceforge.net/release/xsl/current/html/inline.xsl:1: > parser error : Start tag expected, '<' not found > HTTP/1.0 504 Gateway Time-outNote that this is another way docbook toolsets are often broken. If you edit your catalog file, you should be able tell it to use an installed copy of the stylesheets instead, which is often at least an order of magnitude faster. -r
> http://docbook.sourceforge.net/release/xsl/current/html/inline.xsl:1: > parser error : Start tag expected, '<' not found > HTTP/1.0 504 Gateway Time-out > ^This is just... SO wrong... Is it not possible to configure this to *not* attempt to connect to a distant site when building *local* data ? Surely this should be seen as a privacy hole (and possibly a security one if the pulled xsl can be crafted to exploit the tool that then parses it).
On Sun, Feb 8, 2009 at 1:12 AM, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote:> Presumably, if it wants some other file which you don't happen > to have, it would still try to find it on its distant site ? What I'd like > is a way (well, I'd like it to be a default, but hey) to be sure that > none of these tools will attempt to connect away unless I specifically > allow it toThe --nonet option should ALWAYS be given to xsltproc for example. I don't know what, if any, options would prevent net access for the other tools. Mike -- Michael David Crawford mdcrawford at gmail dot com I'm looking for a job in Silicon Valley: http://www.goingware.com/resume/cover-letter.html