I build my book using skynet build 1 The book is Zanata_Quickstart. I open the Preface.xml and see the following id: <preface id="pref-Messaging_Installation_and_Deployment_Guide-Preface"> Not sure where this is coming from.
This is what was described in the emailed notes that describes how to create a book. -- begin Preface.xml -- <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "<<contentSpec.escapedTitle>>.ent"> %BOOK_ENTITIES; ]> <preface id="pref-<<contentSpec.escapedTitle>>-Preface"> <title>Preface</title> <xi:include href="Common_Content/Conventions.xml" xmlnsi="http://www.w3.org/2001/XInclude" /> <xi:include href="Feedback.xml" xmlnsi="http://www.w3.org/2001/XInclude"><xi:fallback xmlnsi="http://www.w3.org/2001/XInclude"> <xi:include href="Common_Content/Feedback.xml" xmlnsi="http://www.w3.org/2001/XInclude" /> </xi:fallback> </xi:include> </preface> -- end Preface.xml -- So what would you like done instead of this?
With build 11 of the web service, and a Content Spec with the title "Writing with Topics", I get: ?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "Writing_with_Topics.ent"> %BOOK_ENTITIES; ]> <preface id="pref-Messaging_Installation_and_Deployment_Guide-Preface"> <title>Preface</title> You can see that it does not follow the pattern: <!ENTITY % BOOK_ENTITIES SYSTEM "<<contentSpec.escapedTitle>>.ent"> %BOOK_ENTITIES; ]> <preface id="pref-<<contentSpec.escapedTitle>>-Preface"> The BOOK_ENTITIES has been correctly written following that pattern with the name of the Content Spec, but for some reason the preface id is hardcoded to "pref-Messaging_Installation_and_Deployment_Guide-Preface"
Oh okay it's setting the wrong title will have a look straight away. Completely missed that sorry.
The issue was caused by the regex missing in the resource file. Therefore it was never getting replaced and was that static field. We have now put the regex in there so that it will get replaced.