Dear Joerg,

Thank you for the pointer. 

On the archlinux, I modified the /usr/bin/dblatex python script 
to point the SGML_CATALOG_FILES variable to /etc/xml/docbook-xml instead of 
/etc/xml/docbook

        cat = os.environ.get("SGML_CATALOG_FILES") 

>         if cat: 
>                 cat += ":/opt/local/etc/xml/docbook-xml" 
>         else: 
>                 cat = "/opt/local/etc/xml/docbook-xml" 
>         os.environ["SGML_CATALOG_FILES"] = cat 

It is now working under  6 seconds.


Thank you

On Saturday, March 31, 2012 1:44:22 PM UTC+2, jvdh wrote:
>
>
>
> On Mar 30, 11:23 am, Christian Kyony <[email protected]> wrote: 
> > I am using dblatex version 0.3.2. 
> > 
> > How can configure dblatex to stop query the network because of the 
> > --catalogs options? 
>
>
> when I had this problem some time ago I made this memo: 
>
> 8<-------------------------------- 
> +dblatex+ uses +xsltproc+ for preprocessing xml-files prior to tex 
> generation.  The main +dblatex+ python-script contains definition of 
> the 
> default location for finding the required catalog files: 
>
>         cat = os.environ.get("SGML_CATALOG_FILES") 
>         if cat: 
>                 cat += ":/opt/local/etc/xml/catalog" 
>         else: 
>                 cat = "/opt/local/etc/xml/catalog" 
>         os.environ["SGML_CATALOG_FILES"] = cat 
>
> If this is not set up correctly +xsltproc+ fetches the catalogs from 
> the 
> net which takes massive time.  _Solution_: if necessary, manually set 
> that variable in your shell resource file.  This prevents the annoying 
> network access. 
> 8<-------------------------------- 
>
> the path mentioned in the note is specific to MacOS, but that's 
> essentially the problem: dblatex does not find the `catalog' file 
> where it expects it locally and then tries to get it from the net. 
>
> hth 
> joerg 
>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Fri, Mar 30, 2012 at 12:12 PM, Lex Trotman <[email protected]> wrote: 
> > > On 30 March 2012 20:19, Christian Kyony <[email protected]> 
> wrote: 
> > 
> > > > Find attached the output of a2x --verbose agenda.txt 
> > 
> > > > I noticed that the bottleneck is when running dblatex. 
> > 
> > > > Is the error messages give you any clue? 
> > 
> > > Hi, 
> > 
> > > None of this output is error messages. 
> > 
> > > The only difference I can see compared with my system which takes 3 
> > > sec on a *much* lower spec machine is that on yours the third xsltproc 
> > > command run by dblatex has --catalogs on it.  That might make it look 
> > > for something on the network and cause your system to wait around for 
> > > 30 secs for the failure timeout. (Note that even on your system it is 
> > > only actually using 5 seconds cpu of the 45 seconds it takes so it is 
> > > waiting for something) 
> > 
> > > These commands are internal to dblatex. 
> > 
> > > I have dblatex 0.3.2-1, what version are you using? 
> > 
> > > Cheers 
> > > Lex 
> > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups 
> > > "asciidoc" group. 
> > > To post to this group, send email to [email protected]. 
> > > To unsubscribe from this group, send email to 
> > > [email protected]. 
> > > For more options, visit this group at 
> > >http://groups.google.com/group/asciidoc?hl=en.


On Saturday, March 31, 2012 1:44:22 PM UTC+2, jvdh wrote:
>
>
>
> On Mar 30, 11:23 am, Christian Kyony <[email protected]> wrote: 
> > I am using dblatex version 0.3.2. 
> > 
> > How can configure dblatex to stop query the network because of the 
> > --catalogs options? 
>
>
> when I had this problem some time ago I made this memo: 
>
> 8<-------------------------------- 
> +dblatex+ uses +xsltproc+ for preprocessing xml-files prior to tex 
> generation.  The main +dblatex+ python-script contains definition of 
> the 
> default location for finding the required catalog files: 
>
>         cat = os.environ.get("SGML_CATALOG_FILES") 
>         if cat: 
>                 cat += ":/opt/local/etc/xml/catalog" 
>         else: 
>                 cat = "/opt/local/etc/xml/catalog" 
>         os.environ["SGML_CATALOG_FILES"] = cat 
>
> If this is not set up correctly +xsltproc+ fetches the catalogs from 
> the 
> net which takes massive time.  _Solution_: if necessary, manually set 
> that variable in your shell resource file.  This prevents the annoying 
> network access. 
> 8<-------------------------------- 
>
> the path mentioned in the note is specific to MacOS, but that's 
> essentially the problem: dblatex does not find the `catalog' file 
> where it expects it locally and then tries to get it from the net. 
>
> hth 
> joerg 
>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Fri, Mar 30, 2012 at 12:12 PM, Lex Trotman <[email protected]> wrote: 
> > > On 30 March 2012 20:19, Christian Kyony <[email protected]> 
> wrote: 
> > 
> > > > Find attached the output of a2x --verbose agenda.txt 
> > 
> > > > I noticed that the bottleneck is when running dblatex. 
> > 
> > > > Is the error messages give you any clue? 
> > 
> > > Hi, 
> > 
> > > None of this output is error messages. 
> > 
> > > The only difference I can see compared with my system which takes 3 
> > > sec on a *much* lower spec machine is that on yours the third xsltproc 
> > > command run by dblatex has --catalogs on it.  That might make it look 
> > > for something on the network and cause your system to wait around for 
> > > 30 secs for the failure timeout. (Note that even on your system it is 
> > > only actually using 5 seconds cpu of the 45 seconds it takes so it is 
> > > waiting for something) 
> > 
> > > These commands are internal to dblatex. 
> > 
> > > I have dblatex 0.3.2-1, what version are you using? 
> > 
> > > Cheers 
> > > Lex 
> > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups 
> > > "asciidoc" group. 
> > > To post to this group, send email to [email protected]. 
> > > To unsubscribe from this group, send email to 
> > > [email protected]. 
> > > For more options, visit this group at 
> > >http://groups.google.com/group/asciidoc?hl=en.


On Saturday, March 31, 2012 1:44:22 PM UTC+2, jvdh wrote:
>
>
>
> On Mar 30, 11:23 am, Christian Kyony <[email protected]> wrote: 
> > I am using dblatex version 0.3.2. 
> > 
> > How can configure dblatex to stop query the network because of the 
> > --catalogs options? 
>
>
> when I had this problem some time ago I made this memo: 
>
> 8<-------------------------------- 
> +dblatex+ uses +xsltproc+ for preprocessing xml-files prior to tex 
> generation.  The main +dblatex+ python-script contains definition of 
> the 
> default location for finding the required catalog files: 
>
>         cat = os.environ.get("SGML_CATALOG_FILES") 
>         if cat: 
>                 cat += ":/opt/local/etc/xml/catalog" 
>         else: 
>                 cat = "/opt/local/etc/xml/catalog" 
>         os.environ["SGML_CATALOG_FILES"] = cat 
>
> If this is not set up correctly +xsltproc+ fetches the catalogs from 
> the 
> net which takes massive time.  _Solution_: if necessary, manually set 
> that variable in your shell resource file.  This prevents the annoying 
> network access. 
> 8<-------------------------------- 
>
> the path mentioned in the note is specific to MacOS, but that's 
> essentially the problem: dblatex does not find the `catalog' file 
> where it expects it locally and then tries to get it from the net. 
>
> hth 
> joerg 
>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Fri, Mar 30, 2012 at 12:12 PM, Lex Trotman <[email protected]> wrote: 
> > > On 30 March 2012 20:19, Christian Kyony <[email protected]> 
> wrote: 
> > 
> > > > Find attached the output of a2x --verbose agenda.txt 
> > 
> > > > I noticed that the bottleneck is when running dblatex. 
> > 
> > > > Is the error messages give you any clue? 
> > 
> > > Hi, 
> > 
> > > None of this output is error messages. 
> > 
> > > The only difference I can see compared with my system which takes 3 
> > > sec on a *much* lower spec machine is that on yours the third xsltproc 
> > > command run by dblatex has --catalogs on it.  That might make it look 
> > > for something on the network and cause your system to wait around for 
> > > 30 secs for the failure timeout. (Note that even on your system it is 
> > > only actually using 5 seconds cpu of the 45 seconds it takes so it is 
> > > waiting for something) 
> > 
> > > These commands are internal to dblatex. 
> > 
> > > I have dblatex 0.3.2-1, what version are you using? 
> > 
> > > Cheers 
> > > Lex 
> > 
> > > -- 
> > > You received this message because you are subscribed to the Google 
> Groups 
> > > "asciidoc" group. 
> > > To post to this group, send email to [email protected]. 
> > > To unsubscribe from this group, send email to 
> > > [email protected]. 
> > > For more options, visit this group at 
> > >http://groups.google.com/group/asciidoc?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/asciidoc/-/YSg5CCwHQX8J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to