Hi,

On Wed, 2006-11-29 at 15:24 +0100, Roman Joost wrote:

I'm not able to compile the HTML files anymore with the autoindex-ng stylesheet.

Why has the change to autoindex-ng been made in the first place?

Sven

Hi,

On Wed, 2006-11-29 at 15:24 +0100, Roman Joost wrote:

I'm not able to compile the HTML files anymore with the autoindex-ng stylesheet.

Why has the change to autoindex-ng been made in the first place?

Sven

Sorry for this kind of troubles. Without autoidx-ng docbook-xsl stylesheets generate rather bad index for non-english languages. For example it doesn't recognize some iso8859-1 letters for french, puts everything into single Symbols category for Russian and Korean.

Autoidx-ng is supposed to solve this problem. Unfortunately, it doesn't work well with xsltproc. It takes too much memory for English and with new docbook-xsl it even denies xsltproc as xslt processor.

I see several options here:

1. Return back to autoidx. Will work but our index will be not perfect.

2. Copy-paste autoidx-ng in our stylesheets and correct it to take less memory and accept xsltproc. Not so good solution I suppose.

3. Fix xsltproc. That will require some time but I can try to do this work. Although I can say how soon this changes will be applied.

Hi,

On Wed, 2006-11-29 at 18:59 +0300, Nickolay V. Shmyrev wrote:

Autoidx-ng is supposed to solve this problem. Unfortunately, it doesn't work well with xsltproc. It takes too much memory for English and with new docbook-xsl it even denies xsltproc as xslt processor.

Until this is fixed, autoindex-ng shouldn't be used by default. Instead it should be made an option at configure time so that people like you can play with it but the rest of the team can continue their work.

Sven

Hi,

On Wed, 2006-11-29 at 18:59 +0300, Nickolay V. Shmyrev wrote:

Autoidx-ng is supposed to solve this problem. Unfortunately, it doesn't work well with xsltproc. It takes too much memory for English and with new docbook-xsl it even denies xsltproc as xslt processor.

Until this is fixed, autoindex-ng shouldn't be used by default. Instead it should be made an option at configure time so that people like you can play with it but the rest of the team can continue their work.

Sven

I see. Is it ok to apply the attached patch then? -------------- next part -------------- A non-text attachment was scrubbed... Name: patch.diff
Type: application/octet-stream
Size: 896 bytes
Desc: not available
Url : /lists/gimp-docs/attachments/20061129/42a72c4e/attachment.obj

Hi Nickolay,

On Wed, Nov 29, 2006 at 07:50:38PM +0300, Nickolay V. Shmyrev wrote:

Autoidx-ng is supposed to solve this problem. Unfortunately, it doesn't work well with xsltproc. It takes too much memory for English and with new docbook-xsl it even denies xsltproc as xslt processor.

Until this is fixed, autoindex-ng shouldn't be used by default. Instead it should be made an option at configure time so that people like you can play with it but the rest of the team can continue their work.

I see. Is it ok to apply the attached patch then?

Can you checkin your patch
for yourself? I'm just curious :)

Greetings,

I'm just pasting to let you know :) Patch is committed, sorry for troubles.

I'll try to look at xsltproc issue if there will be more time. Hopefully with new libxslt we'll be able to move to autoidx-ng.