Hi Laurent, I had the same problem, except for the "5-7". I only had to remove multiple entries with identical page numbers. A search for buzzword index in the archives should unearth that thread ("Index and Pagenumbers").
Important parts: ------------ by Jeremias Maerki ------------- * XSL 1.1 contains support for building indices but that hasn't been implemented in FOP, yet. ------------ by Jeremias Maerki ------------- At the moment, the resolution of page-number-citations can happen in two places at the moment: 1. In PageNumberCitationLayoutManager where the page number is directly entered as a TextArea if the target page is already known. 2. In area.inline.UnresolvedPageNumber if the target page is only known at a later stage. In this case the page number is squeezed into some pre-reserved space. This avoids a two-pass layout approach that other implementations use but it has its limitations. The problem for you: In case 2, the layout engine is no longer operating and you cannot adjust properly for larger amounts of text (multiple p-n-cs that are suddenly gone). However, since word indices are normally at the end of a document, this might be something you can avoid. ------------- by Andreas Delmelle ------------ I once started gathering some thoughts on the topic, but didn't get very far... See: http://wiki.apache.org/xmlgraphics-fop/FormattingObjectsForIndexing By itself, the implementation of the 'index-key' property is not that difficult. It is its treatment further on during layout/rendering that will be a challenge. If you're interested, I'll be glad to co-operate on this one. ----------------------------------------------- My personal solution was actually: I generated the fo-file to area tree, read the page numbers, deleted entries from the original fo file and generated the resulting fo-file to pdf. Regards, Georg Datterl ------ Kontakt ------ Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH: www.irs-nbg.de Willmy PrintMedia GmbH: www.willmy.de Willmy Consult & Content GmbH: www.willmycc.de -----Ursprüngliche Nachricht----- Von: Laurent Caillette [mailto:laurent.caille...@ullink.com] Gesendet: Mittwoch, 19. August 2009 11:39 An: firstname.lastname@example.org Betreff: Referencing multiple pages for index entries Hi all, First, I'd like to thank all FOP developers for creating such a great tool that tackles really, really hard problems. I'm developing an OSS tool for generating PDF (and other formats) from a wiki-like syntax and it uses FOP instensively. Now I met some people that could be interested by Novelang (the OSS tool of mine) but they need index entries. XSL 1.1 specification supports this, but in the short term FOP doesn't seem to be implementing it. FO markers are great for single pages, but they come short when referencing several pages, as we don't want duplicate entries like "3, 3, 5, 6, 6, 7" ("3, 5-7" wanted instead). A solution for a reasonable amount of work seems to be a FOP extension acting like a marker but supporting multiple entries, calculating page ranges and removing duplicates. I've looked at extension samples (MathML, Barcode4J). They all work as rectangular graphical areas. I could find none working as a text flow. - Is it possible to implement an extension generating text flow? - If yes, where can I find such an example? - If no, any other idea? Regards, Laurent Caillette http://novelang.sourceforge.net __________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 4347 (20090819) __________ Le message a ?t? v?rifi? par ESET NOD32 Antivirus. http://www.eset.com