{"id":1705,"date":"2016-02-19T17:33:51","date_gmt":"2016-02-19T15:33:51","guid":{"rendered":"http:\/\/www.ozalto.com\/en\/?p=1705"},"modified":"2016-02-19T17:33:42","modified_gmt":"2016-02-19T15:33:42","slug":"5-errors-you-will-do-with-indesign-xml","status":"publish","type":"post","link":"https:\/\/www.ozalto.com\/en\/5-errors-you-will-do-with-indesign-xml\/","title":{"rendered":"5 errors you will do with InDesign XML"},"content":{"rendered":"

XML Import within Adobe InDesign is tricky\u00a0for rookies.<\/strong> It’s likely you will fall into one of its\u00a0many pitfalls. You have to follow some rules if you want to get your catalog, directory or book project perfectly populated<\/strong>!<\/p>\n

Here are 5 errors you will probably do<\/strong> unless you read carefully\u00a0this article.<\/p>\n

1)\u00a0Ignore the true nature of XML<\/h3>\n

Importing a XML file within InDesign is a piece of cake. But once loaded, you may think you have a nice and layout free database.<\/strong> So eventually InDesign will pick whatever data it needs<\/strong> within that structure.<\/p>\n

Well\u2026not really.<\/strong><\/p>\n

InDesign XML is nothing but tagged text !<\/p><\/blockquote>\n

\"En<\/p>\n

In above figure, dropping a XML Element within the document will place all the nodes as a continuous tagged texts article.<\/p>\n

Once you got that,\u00a0next points will be easier to understand.<\/p>\n

2) Import different structures<\/h3>\n

One of the hardest rule is that incoming structure MUST match the existing structure.<\/strong>
\nNot something you care on the original importation. However once a layout is set with all tags needed, it becomes dramatically important.<\/p>\n

If you do import mismatching structures and think InDesign will dela with it\u2026<\/p>\n

You may\u00a0suffer,\u00a0a lot!<\/p><\/blockquote>\n

Imagine that basic\u00a0structure:<\/strong><\/p>\n

\"Structure<\/p>\n

And this existing structure.<\/strong><\/p>\n

<Root>\r\n <a>A<\/a>\r\n <c>C<\/c>\r\n <b>B<\/b>\r\n<\/Root>\r\n<\/pre>\n
And you think InDesign will deal with\u00a0your\u00a0mess\u2026?<\/strong><\/p>\n
Here is what you will get eventually:<\/p>\n
\"Problemes<\/p>\n
When\u00a0the incoming <a> tag found an appropriate <a> tag within InDesign (same index) and the content was placed within that node. Then a <c> comes in and found\u00a0a <b> at its index. <c> says : “Hey, I am not a <b>, looking forward\u2026”. Then <c> found\u00a0a <c> and the content was\u00a0placed.Then entered <b> after <c> but <b> couldn’t find any following <b> tag, so it\u00a0was\u00a0added as it.<\/p>\n
Nothing close to what we could expect, right ?<\/strong><\/p>\n
At no point, InDesign is going to look backwards to deal with the incoming tags!<\/p>\n
3) Overuse frames<\/h3>\n
Quite logically, rookies tend to\u00a0use and abuse of frames.<\/strong> Once for the price, one for the description, etc. Eventually a “nature morte” of frames. Charming yet inefficient.<\/strong><\/p>\n
\"module_frame\"<\/p>\n
Remember that your structure is text made. So keep in mind your fundamental brick is a story within a text frame.<\/strong> Whatever the nature of your project, it will starts with an unique text frame.<\/p>\n
use boxes as few as possible<\/p><\/blockquote>\n
\"textRules\"<\/p>\n
So try to mimick frames, position and spacings with texts attributes.<\/strong> A paragraph rule can simulate a frame. Leading, spaces after\/before, indents and tabs can dispatch items like you would it would be isolated frames.<\/p>\n
You tried that but you really need a floating frame for the pictures ?<\/strong> Well use anchored frames<\/strong>\u00a0in combination of\u00a0objet styles<\/strong> to layout control.<\/p>\n
4) Forget\u00a0styles<\/h3>\n
A few of you may already know that you can map tags to styles. It’s always good practice to use\u00a0styles<\/strong> so any tags you try to add will be linked to the appropriate style.<\/strong><\/p>\n
\"association_styles\"<\/p>\n
\"tarif_prix\"<\/p>\n
\"style_applique\"<\/p>\n
The “price” styles is automatically applied to the associated tag.<\/p>\n
However one hiccup<\/strong> is that you can’t apply different styles to tags regarding to their\u00a0location.<\/strong> For ex. you would like p tags to be in arial in text\/p but in Times in headline\/p. No way with mapping.\u00a0You would have to set styles<\/strong> within the xml file thanks to aid namespaces<\/strong> and aid:pstyle and aid:cstyle to call styles more smoothely. An alternative is to use scripting.<\/strong><\/p>\n
5) Lack of abstraction<\/h3>\n
Catalog or directories projects tend to offer a repetitive pattern.<\/strong>\u00a0A bad approach would be to set a really descriptive structure like below\u00a0:<\/p>\n
\"What<\/p>\n
That could work somehow. However\u00a0that would lead to a lot tagging within InDesign and would definitively lack of scalability.<\/strong> If you have two or three players, well why not but what if you have to work with hundreds ?<\/p>\n
There is so much better to do !<\/p><\/blockquote>\n
Thanks to abstraction<\/strong> and some options, InDesign is going to work for us.<\/strong> Let’s consider that structure:<\/p>\n
\"goodXMLLayout\"<\/p>\n
We only have one player module.<\/strong>\u00a0Thanks to the “Clone the repeated text elements” you will find in the XML Import Options, InDesign is going to duplicate our module as many times as needed:<\/p>\n
\"xmlImportOptions\"<\/p>\n
\"xmlResult\"<\/p>\n
Et voil\u00e0 !<\/strong><\/p>\n
I hope this article will help you avoiding common mistakes<\/strong> and get faster results. If you want to share other typical errors, feel free to do so into the comments.<\/p>\n
If you want a XML Import training or consulting services for your publishing projects, contact us !<\/a><\/strong><\/p>\n
See you soon !<\/p>\n","protected":false},"excerpt":{"rendered":"
XML Import within Adobe InDesign is tricky\u00a0for rookies. It’s likely you will fall into one of its\u00a0many pitfalls. You have to follow some rules if you want to get your catalog, directory or book project perfectly populated! Here are 5 errors you will probably do unless you read carefully\u00a0this article. 1)\u00a0Ignore the true nature of […]<\/p>\n","protected":false},"author":2,"featured_media":1719,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[43,5,15],"tags":[82,76,81,75],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/posts\/1705\/"}],"collection":[{"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/posts\/"}],"about":[{"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/types\/post\/"}],"author":[{"embeddable":true,"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/users\/2\/"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/comments\/?post=1705"}],"version-history":[{"count":0,"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/posts\/1705\/revisions\/"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/media\/1719\/"}],"wp:attachment":[{"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/media\/?parent=1705"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/categories\/?post=1705"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ozalto.com\/en\/wp-json\/wp\/v2\/tags\/?post=1705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}