#104 XSL 1.42 breaks FO generation...

closed-works-for-me
nobody
None
5
2001-09-23
2001-08-13
Dan York
No

Norm,

Just downloaded the 1.42 stylesheets today and it
appears that the
localization stuff does not work quite right when
generating FO. Here is what I get:

With the 1.41 stylesheets:

$ xsltproc -o sample.fo
/usr/share/sgml/docbook/docbook-xsl-1.41/fo/docbook.xsl
sample.xml
Making portrait pages on USletter paper
(8.5inx11in)
$

With the 1.42 stylesheets:

$ xsltproc -o sample.fo
/usr/share/sgml/docbook/docbook-xsl-1.42/fo/docbook.xsl
sample.xml
Making portrait pages on USletter paper
(8.5inx11in)
No localization exists for "en" or "". Using
default "en".
No localization exists for "en" or "". Using
default "en".
No "en" localization exists.
No context named "title" exists in the "en"
localization.
No template named "article" exists in the context
named "title" in the "en" localization.
No localization exists for "en" or "". Using
default "en".
No "en" localization of "Copyright" exists; using
"en".
No localization exists for "en" or "". Using
default "en".
No "en" localization exists.
No context named "section-title" exists in the "en"
localization.
No template named "sect1" exists in the context
named "section-title" in the "en" localization.
No localization exists for "en" or "". Using
default "en".
No "en" localization exists.
No context named "section-title" exists in the "en"
localization.
No template named "sect1" exists in the context
named "section-title" in the "en" localization.
No localization exists for "en" or "". Using
default "en".
No "en" localization exists.
No context named "section-title" exists in the "en"
localization.
No template named "sect2" exists in the context
named "section-title" in the "en" localization.
No localization exists for "en" or "". Using
default "en".
No "en" localization exists.
No context named "section-title" exists in the "en"
localization.
No template named "sect2" exists in the context
named "section-title" in the "en" localization.
$

My LANG environment variable is set to "en_US". I am on
Linux and, as
you can see, using xsltproc (v1.0). The sample.xml was
just a trivial XML
file (an <article> with a couple of sections). What
happens is that I get
a PDF file that does not have a title or section
headings.

Discussion

  • Charles Gagnon

    Charles Gagnon - 2001-08-19

    Logged In: YES
    user_id=26887

    I have seen the same behavior on Solaris using Cocoon 1.8 (and an upgraded Xerces), processing a simple article. It was working in 1.41 and it has been broken in 1.42,43 and 44. I get an error message like:
    XSL Warning: Can not load requested doc: http://home.unixrealm.com/~charlesg/docs/xsl/common/l10n.xml

    Any ideas?

     
  • Norman Walsh

    Norman Walsh - 2001-09-22

    Logged In: YES
    user_id=81663

    I can't reproduce this with xsltproc. Have you tried a more
    recent version? Are you sure you installed the whole
    stylesheet distribution?

    Wrt Cocoon, I wonder if the base URI is getting hosed by a
    bug in Xerces or Cocoon?

    The stylesheets load localization info from l10n.xml in the
    common subdirectory under where the stylesheets are installed.

     
  • Norman Walsh

    Norman Walsh - 2001-09-22
    • status: open --> open-works-for-me
     
  • Dan York

    Dan York - 2001-09-22

    Logged In: YES
    user_id=12191

    Norm,

    Everything works fine with 1.44. As I recall, I think the
    issue may have been an xsltrpoc issue - I believe DV told me
    I had to grab a newer
    version, which I did. All is working well. My apologies
    for not coming back to close out the bug earlier.

    I would consider this closed - although if you want to keep
    it open for the Cocoon issue from charlesg, that is fine by
    me. *My* issue is set, though.

    Thanks,
    Dan

     
  • Norman Walsh

    Norman Walsh - 2001-09-23
    • status: open-works-for-me --> closed-works-for-me
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks