How to report issues How to escalate issues
  • please check whether this issue is already known
  • provide a link to an article that is affected by the issue
  • report only one issue per section
  • select a descriptive title
  • consider to prefix the title with Bug, Proposal, Question, Comment, Task ...

There is a central page at (English) gathering all major issues with this extension. Issues that can't be solved and are not yet covered on the page at meta should be translated and added there.

For obvious bugs the issue tracker (English) is the preferred place to directly issue and check tickets.

At IRC #booktool (English) some immediate support might be available.

Question: How to organize issuesEdit

This is the template in action. Not too much magic here.

A template like this helped us in past deployments to organize and annotate issues.

Comment: Following some dummy commentsEdit

These don't need any translation ....

Question: Principal AuthorsEdit

How is the list of principal authors computed? It looks as if any contributor is listed. He!ko 16:08, 11 February 2009 (UTC)

Proposal: Add a table of contentsEdit

There is a ticket for this issue.

Did you consider to add a table of contents at the first page of the PDF? I think this might improve usability of larger PDFs. --he!ko 15:57, 11 February 2009 (UTC)

Bug: <poem/>-tag not supportedEdit

There is a ticket for this issue.

It looks like the <poem/>-tag is not supported (example). He!ko 16:08, 11 February 2009 (UTC)