A Chapter with the same name is not uniquely identified. If I have a content spec with two chapters: Chapter: Sample Chapter Some Content [100] Chapter: Sample Chapter Different Content [110] It looks like the second chapter overwrites the first. However, the problem doesn't end there.. I end up with: Book.xml <xi:include href="chap-Sample-Chapter.xml"> <xi:include href="chap-Sample-Chapter.xml"> Sample-Chapter.xml <xi:include href="topics/TopicID110.xml"> Which gives me an error of "ID TopicID110 is already defined", because Topic 110 is included twice in the book. So two issues: 1. Uniquely identify chapters even when their names are the same. 2. Investigate if we can get duplicate IDs through inclusion like this through some other mechanism, and how we can detect and deal with that.
We discovered this because someone accidentally pasted the same Chapter into a Content Spec twice.
Fixed the Duplicate chapter naming issue. The processor never checked that chapter names were unique when processing or building. So now the builder will add the line number of the chapter to the file name. This in turn makes each chapter entity unique and allows for the book to be built by publican. The builder also takes care of the duplicate topic id because the chapters are then declared different since they have different names and therefore the topics inside are duplicated and given a unique id and filename. As for issue number two I don't quite get what you mean by that Josh, so if you could please elaborate that'd be great.
Don't worry about the second issue. It's basically investigating to see if other inclusion mechanisms can lead to duplicate ID errors. If we run into it we can deal with it then.
Moving it onto QA then. Fixed in 0.20.0 of the csprocessor.