It is really hard to advise without seeing what the XML is structured like and what the presentation of that XML inside of InDesign is desired to be.
For what your needs are as I understand them, and again depending on what the XML looks like and how consitent it is in one document type (book, article), you may be able to skip any transforms and simply import it with mapped styles and have all or the majority of the document(s) formatted. But it really depends on the XML itself and what it should look like in ID once formatted.
Being new to ID and going into XML import straight away is like jumping into the deep end of the pool to learn to swim. It can be done, but there is a learning curve. If you would like to privately share a couple XML files of each type (book and article) I would be happy to review them for any issues that may require XSLT work or not, as well as advise you as to how I would approach your needs.
If this is something you can do, ZIP up the XML and a sample ID file or two of how you desire the work to look in ID and upload it to dropbox.com or the like and send me a private message with the download link and over the next day or two after receiving it I would do so.
Thanks a lot for your answer. I’ll try to explain how are things.
By now, we publish our content doing auto assembly. It means, we have written a collection of XSLT scripts that transform an XML document to XSL-FO format – one script for each series of publication (each layout). Then a commercial XSL-FO processor is used to generate resultant PDF document. Depending upon the series we use AH XSL Formatter or RenderX XEP Assistant. It works quite well, but, naturally, has some inconveniencies – generally, almost no possibilities to do minor changes to the resultant PDF document. On the other hand, the XSL-FO code updating is not a nice occupation and needs some qualifications, which our editors haven’t got. That’s why the idea was born: using XSLT experiences in transforming our XML structures to XSL-FO (and also XHTML), attempt to transform our content to such XML (maybe IDML) format, which can be imported to ID. Next, mentioned minor changes could be done in ID, before final PDF generation.
Mike, it would be great if you wanted to share your opinion on these things.
Exemplary files that contain a source XML document and a resultant PDF document (generated automatically via XSL-FO) are available here:
Interesting job. The XML seems very consistent, and can be compared to the current PDF almost page by page.
I noticed there seem to be no ligatures used anywhere in the PDF -- not only for Minion Pro's typical "Th", but also not for the practically mandatory "fi" and "fl". (Of course, this could have been a design choice as well.)
A direct XML-to-IDML trajectory is very, very hard. IDML is not the most user friendly format! By way of intermediate, and looking at the target design, I think INX would serve much better!
Other than IDML, an INX file is one single file, and you don't have to provide specific values for every single item. At its very basic form, just plain text plus an indication of which paragraph style to use is enough! But everything else I see in the PDF, including the footnotes, should be possible as well.