FOP does not implement FO index processing, so it is incapable of removing duplicated page numbers on its own. Antenna House and XEP RenderX can both render indexes. If FOP is a requirement it can be done by implementing a two-pass process using the FOP area tree—basically post-process the rendered index to generate a literal markup representation of the correct page number references then rerender the XML to produce the final PDF. Cheers, Eliot -- Eliot Kimber http://contrext.com From: oXygen-user <oxygen-user-bounces@oxygenxml.com> on behalf of Bernhard Kleine <bernhard.kleine@gmx.net> Date: Monday, May 21, 2018 at 10:01 AM To: <oxygen-user@oxygenxml.com> Subject: [oXygen-user] repeated indexentries with the same text from the same page During the indexing process I noticed that an repeated indexentry is not automatically removed. An example: I agree that the example is not very intelligent. I substituted the entity <!ENTITY T3 "T₃ "> with <!ENTITY T3 "T₃ <indexterm>&primTthree;</indexterm>"> <!ENTITY primTthree "<primary>TH (Schilddrüsenhormon)</primary><secondary sortas='Tdrei'>T₃, (Trijodothyronin)</secondary>" > and the page 521 is about thyroid hormones, but it shows that FOP does not check for doubled page numbers of the same entry. Kind regards Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kleine@gmx.net www.b-kleine.com, www.urseetal.net - thunderbird mit enigmail GPG schlüssel: D5257409 fingerprint: 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09 _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
