Re: [docbook-apps] Eclipse Help generation - anchor IDs
On 5.3.2015 8:19, Shikareva, Ekaterina wrote: I generate Eclipse HTML Help from my DocBook files with xsltproc, and every generation leads to attribute (ID) changes in anchor tags. Because of this we get a lot of warnings during code reviews. Our current solution is to mark such changes as unimportant in Beyond compare, but is there a way to minimize anchor ID changes during HTML files generation? Apart from what Bob suggested you can put xml:id attribute on all structural elements that produce anchors -- like chapters, sections, ... Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML and Web consulting and training services DocBook/DITA customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Eclipse Help generation - anchor IDs
Try setting the stylesheet param generate.consistent.ids to 1. See: http://docbook.sourceforge.net/release/xsl/current/doc/html/generate.consistent.ids.html Bob Stayton Sagehill Enterprises b...@sagehill.net On 3/4/2015 11:19 PM, Shikareva, Ekaterina wrote: Hello! I generate Eclipse HTML Help from my DocBook files with xsltproc, and every generation leads to attribute (ID) changes in anchor tags. Because of this we get a lot of warnings during code reviews. Our current solution is to mark such changes as unimportant in Beyond compare, but is there a way to minimize anchor ID changes during HTML files generation? -- *Kind regards,* *Ekaterina Shikareva* Senior Technical Writer Luxoft Russia *Skype: maymakayu* *www.luxoft.com* http://www.luxoft.com/ *www.facebook.com/Luxoft* http://www.facebook.com/Luxoft This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Eclipse Help generation - anchor IDs
Thank you very much, it helped! -- Ekaterina Shikareva -Original Message- From: Bob Stayton [mailto:b...@sagehill.net] Sent: Thursday, March 05, 2015 11:30 AM To: Shikareva, Ekaterina; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Eclipse Help generation - anchor IDs Try setting the stylesheet param generate.consistent.ids to 1. See: http://docbook.sourceforge.net/release/xsl/current/doc/html/generate.consistent.ids.html Bob Stayton Sagehill Enterprises b...@sagehill.net On 3/4/2015 11:19 PM, Shikareva, Ekaterina wrote: Hello! I generate Eclipse HTML Help from my DocBook files with xsltproc, and every generation leads to attribute (ID) changes in anchor tags. Because of this we get a lot of warnings during code reviews. Our current solution is to mark such changes as unimportant in Beyond compare, but is there a way to minimize anchor ID changes during HTML files generation? -- *Kind regards,* *Ekaterina Shikareva* Senior Technical Writer Luxoft Russia *Skype: maymakayu* *www.luxoft.com* http://www.luxoft.com/ *www.facebook.com/Luxoft* http://www.facebook.com/Luxoft -- -- This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you. This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Eclipse Help generation - anchor IDs
Hello! I generate Eclipse HTML Help from my DocBook files with xsltproc, and every generation leads to attribute (ID) changes in anchor tags. Because of this we get a lot of warnings during code reviews. Our current solution is to mark such changes as unimportant in Beyond compare, but is there a way to minimize anchor ID changes during HTML files generation? -- Kind regards, Ekaterina Shikareva Senior Technical Writer Luxoft Russia Skype: maymakayu www.luxoft.comhttp://www.luxoft.com/ www.facebook.com/Luxofthttp://www.facebook.com/Luxoft This e-mail and any attachment(s) are intended only for the recipient(s) named above and others who have been specifically authorized to receive them. They may contain confidential information. If you are not the intended recipient, please do not read this email or its attachment(s). Furthermore, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and then delete this e-mail and any attachment(s) or copies thereof from your system. Thank you.
