An Open Source Project

An example: Assume, we want to publish our Newspaper or periodicals on the Internet.

What material do we have to start:

 

What do we need on the Internet:

 

«BatchXSLT for InDesign» transforms InDesign documents into understandable structured XML. It creates groups of text and image boxes and merges them to article objects.

The automatically generated external style sheet (a CSS) may be modified to match the visual needs in browser views.

 

The resulting XML and HTML output files contain information on:

 

The exported data is suitable for any further electronic processing.

«BatchXSLT for InDesign» creates a flip book based on XML, HTML5 and Javascript.

 

Such eBooks may be textually searched, may be read by search engines and are suitable for any further data processing!

No matter what you want to do with the exported data, XML is first choice!

 

All source code is available at github - license is GPL3

 

 

If you have no such rights, ask your System Administrator

 

Make the two copy operations as mentioned on the install disk image.

Double click the downloaded installer to start it. You will be asked to enter the adminstrator’s login credentials to start the installation.

«BatchXSLT for InDesign» runs with Windows 10 - 64 Bit, OSX 10.9 and newer and with InDesign CC back to CS6. At least 8GB of main memory, for huge documents the double or more.

 

The script

„ExportCurrentDocument.jsx“

exports the content of the current document, creates all page previews as PDFs and JPEGs, copies the original images and starts «BatchXSLT» to transform the prepared material to (e-paper) XML and HTML.

 

The script

„ftpToWebArchive.jsx“

is the starter for «BatchXSLT» to transfer exported data to a web server using the FTP protocol.

 

The script

„pushToWebDatabase.jsx“

is the starter for «BatchXSLT» to load exported text data into the full-text search database.

To enable you to immediately export a document, the software package contains an example document.

The previously installed package folder „BatchXSLT4InDesign“ contains the sub-folders „BatchXSLT/_TestData“. Therein find the folder „in“ with several files:

 

Open the file “DB_20080628_CS5.indd” in InDesign.

At the InDesign Script Panel double click the script “ExportCurrentDocument.jsx”.

The following dialog is shown:

You may fill in the fields „Company Name“, „Object Name“ etc. Sub-folders with the given information are created below the „Export Base Path“ (shown at the top of this window).

Click the OK-Button to start the export.

 

After a minute the message appears, that the base export has been completed and that the exported data, which is now transformed by «BatchXSLT for InDesign», may be expected in the output folder.

Depending on the exported document’s complexity, the export process lasts between seconds or some minutes.

 

The export script has compiled an IDML file, has produced page PDFs and -JPEGs and has copied all images into the folder “Export/in” in your Home folder. After this, it has called «BatchXSLT» to produce the XML output.

 

That’s it! The XML and the eBook is ready!

The exported data may be found within your Home folder: Export/out/... and some folders deeper. The HTML file is named like the exported InDesign Document.

For the above shown example, the path is:

Open this file in your browser.

On this page, the blue background shows, that each article has enough distance to his neighbor.

No box of one article should touch or even cover an other element of an article next to it.

The article below, titled “Too Large Title Box”, touching the right article, shows the importance of such article gaps.

In browser view, when moving the mouse over the article, the shadow overlay shows, that both articles were merged into the same article unity. Click on the article and you will see the text of both articles as a single article.

 

Advertisement

Don’t expect your readers to see and to read adds running in multiple columns over an arbitrary number of pages!

Separate the text boxes for example at each category boundary.

It is comfortable for a reader while browsing through adds to be able to see the category head too.

So: Anchor the Heads into the running text!

Anchor

at the proper position in a read flow!

Do not simply position them over the text. Otherwise, such floating elements will be placed anywhere in the exported text – for example at the text end. In any case, they will not appear in the desired read flow

You even can add a caption to the image, group both and then anchor the whole group.

Using the Anchored Objects Options palette, you may position the image anywhere on the page – even outside the parent text box.

This actually should be an independent article! The overlap with the left title box means for the exporter to export and merge both articles into one single article unity!

The far too wide title box of this single column article does not have a negative effect in the printed document and just looks fine. Touching the article on the right hand side causes, that both articles are merged into one article. This might be correct if you intentionally enlarge the box but definitely is wrong in this case.

To find components belonging to the same article, this “BatchXSLT for InDesign” pays attention to:

Text and image boxes are attentive to other boxes within a given catch radius. The standard catch radius is 0 (touching).

Box catching is the most important part to present readers an article as an entity including title, lead, text and image, just like they would read it on the Newspaper page.

The blue background box on this page does NOT try to combine all articles into a single large article. The reason is simple: The blue colored box is defined to have content type “Unassigned” (is not a text and not an image box.

There are several box types which are always exported as a standalone object:

A page with a background image, also can be achieved by a dedicated special master page.

 

Advertisement

The

is not only very important for your readers, but especially for full-text search engines.

In order to be able to deliver relevant results, it is most important, that a textual section covers one theme only like “cars to sell”.

If you don’t split sections, you run the risk that a

will return an article actually talking about “cars to sell” but also about “higgledy-piggledy”.

The optical

of sections in a printed product is done automatically by our eyes and brain.

In an eBook, where a computer is responsible for an adequate display, the physical separation (box splitting) must be done manually when a document is created!

The three boxes of this article:

are chained with each other.

Chained text boxes assure that the correct read flow of an article is preserved even when it is built from a more complex box structure.

Articles running over multiple pages are NEVER separated and are exported as single text flow (except you request story box splitting).

The box chain also guaranties, that the box on the right side having a lot of space to the title, is attached to the correct article.

Chains are not useful in all cases! Often enough, especially in automated ads production, text is filled into chained boxes in one piece.

In these cases it is of importance to physically split sections. Your readers will be happy not to read thousands of lines with any number of sub-sections as a single article.

It is up to you to decide when and where text boxes should be split.

The “Images” tab at the main export window lets you choose several options to define how images contained in an InDesign document should be converted:

 

 

From the drop down menu, you may choose to export images as JPEG or PNG.

At the “at width:” field enter the size of exported images as a scale factor. 1.0 means: same size as shown in the InDesign document.

If you need 2 image sizes enter something like 1.0//2.0

This will export the primary image at a scale factor of 1.0 and a secondary image will be scaled to double size.

 

A usable DPi is 150 dpi. For high quality images on high resolution screens set to 300.

 

Specify the desired jpeg quality (0 - 100). Default is 90.

 

A semicolon separated list of terms. If an image name starts with one of them, it will not be exported.

A widely spread habit is to simply stick new text boxes over unreadable text in an image.

DON’T do this!

Finish the image in your preferred imaging software: rub out unwanted parts and write new readable text. Like this, the image is complete and a unity.

Paste over text boxes are exported AFTER the image and are loosing the direct context to the image.

Links to external web sites may be achieved using InDesign‘s Hyperlinks Palette.

 

The palette may be found from InDesign’s main menu:

Mark the text which should act as a Hyperlink like, for example, this address:

This also can be any text which does not look like a web address.

At the Hyperlinks palette, you now create a new link (marked red).

 

The information in the URL field is the link target.

More information on URL Hyperlinks can be obtained from the InDesign manual

The proper functionality of a given link may be tested within InDesign by clicking on the small right pointing arrow in the Hyperlink palette.

«BatchXSLT for InDesign» automatically will create an XML or HTML tag which may be used by web applications and which will work as a clickable active link in any web browser.

Particularly in an automated production environment it is very convenient to define web links using style sheets.

Create a new Character Style named

 

An Internet address like www.aiedv.ch which is marked with this style turns into an active web link when clicked in a Browser. However, in a page PDF, such ‘styled’ links are not active.

The «BatchXSLT for InDesign» manual describes, how to create any number of such style sheets which will become active when clicked.

Document indexes whose page numbers are acting as active links and actually flip to the chosen page make your readers happy!

Create a new Character Style named

and mark the page numbers in the index lines with this style.

You may create any number of such styles as long as their name starts with ‘gotoPage’ like ‘gotoPage bold’.

When the reader clicks on one of these page numbers the desired page is shown.

The document index entries on the 2nd page of the front cover of this document exactly work like this.

Within the target article define a new Hyperlink destination “Text Anchor”. Such a destination anchor is defined at the article titled “Links with Script Labels” on the following page. The anchor is set right before the title.

After this, mark the text which can be clicked to jump to the article and define it as new Hyperlink to this “Text Anchor”:

 

 

A click on the text will flip the page and show the article.

This works for plain text and also anchored text boxes which may look like a button.

To add interactive meta data to an image or a text box – do this: Activate the “Direct Selection Tool” and then the image or text box. At the „Script Label“ Palette make entries with the syntax: Keyword:Content##

Acceptable keywords are:

title – A help text which is shown in the browser when the mouse is moved over this item

href – The URL which must be called when the mouse is clicked

target – the target window in which the URL should be shown

text – an additional text to show in web display

The ‘href’ attribute can even contain Javascript like:

 

 

You also can write your own more or less complex Javascipt within ‘custom.js’ and call it from such a href definition:

 

 

Like this, your web site can be even more interactive, informative and therefore more attractive for readers.

The text line below was marked and the defined as a hyperlinks to a page destination using the Hyperlink palette.

 

Text and image boxes may be defined, to open external web sites or jump to a page and show a certain article.

The button itself is not shown in the article window.

#dirlinkn:https://google.com#

 

This also may be empty text boxes, for example, to mark a link on a full page add. Underlaying links on the image then act as avtive hyper links.

AT LEAST ONE space must be typed in the text box.

#dirlink:https://google.com#

Create and style a text box like a button. Mark the button text and define a new link pointing to the desired page using the Hyperlinks palette.

 

#dirlinki#

Again, create and style a text box like a button.

 

To jump to a page index (0 based page number in the document):

#dirlinki:p=6#

 

To jump to a page name:

#dirlinki:P=XII#

The same effect can be obtained by adding above labels to the image box.

#dirlinki:p=2#

Jumps to the TOC page 2

At the beginning of the text in the target article (in this case the Disclaimer), a target text anchor must be set - we named it ‘disclaimer’.

Then, activate the ‚Button Text’ and define a hyperlink which points to the defined target text anchor.

 

#dirlinki#

Open the TAble Of Contents by defining a label to the target article box.

#dirlinki:l=TOC#

Opens the TOC

Create and style a text box like a button or use an image.

#dirlinki:s=legal notice#

Create and style a text box like a button or use an image.

#dirlinki:S=image text box#

Simply create a document index using InDesign’s “Table of Contents” feature:

a) Define the TOC

b) Create the TOC

 

This option can be used when a TOC must be designed different to InDesign’s TOC feature.

 

Use InDesign’s “Table of Contents” palette to define and create your TOC.

Nothing special: add all the styles which should go into the index, set the index level and set the style for this level.

 

As mentioned in an other article, we need a special character style to mark the plain page number. It’s name must be ‘gotoPage’.

Set the style for the ‘Page Number’ to ‘gotoPage’ like shown in the image below (marked red). This may be any character style who’s name starts with ’gotoPage’ like ‘gotoPage bold’ or ‘gotoPage_12pt’

Now save and create your table of contents. Put it on a ‘normal page’ – do NOT put it on a master page! Objects located on master pages are not exported.

You now may check the page numbers in the table of contents: it’s character style must be set to ‘gotoPage’.
As browsers can not display ‘tabbed text’ like page layout programs can, you might want to reformat your TOC as a real table. Like this the TOC shown in a browser will be a nice looking formatted table.

Sure, sound and movies are nonsense for printed publications. However, they make sense if an online issue should contain additional information for readers, students or shoppers.

Examples:

– Training material with enhanced information from sound and movies.

– Possible positions of a chair should be shown in a sales catalog.

– You want to sell your used car like shown in the following „Mini“ add.

The printed document shows the image only, when online, the reader can watch a movie.

Click the image to see this racer in action! (With Power Pack)

moviewidth:width in pixels (if missing => auto detect width)

movieheight:height in pixels (if missing => auto detect height)

moviecontrols:true or false (if missing => true)

movieautoplay:true or false (if missing => true)

movieprimary:media file name[;mimetype]

moviealternate:media file name[;mimetype][,...;...][,...;...]...

 

The three boxes of this small article do NOT touch each other.

One way to export all three boxes as an article unity is to group them together.

We all know it: An article consists of one or more boxes containing text or images. A special system called “Articles Components Recognition” (ACR) takes care to merge boxes into article unities.

Several properties of boxes and their layout are important to help to build an article from single boxes:

– overlapping

– grouping

– chaining

The boxes of this first example article, which we read as an entity in a Newspaper, are neither overlapping, nor grouped or chained.

Each box is exported as independent text. You can verify this by moving the mouse over each box and click on it.

The other examples on this page use the attributes mentioned above to build and export whole articles: grouping, overlapping and chaining.

The background color helps to see the boundaries of the different boxes. The bounding box is THE keyword for building articles.

The same three boxes which do NOT touch each other.

Chaining boxes will output the text in exactly the same order the boxes are chained.

Chained boxes NEVER are split – the whole text is exported as one article, even if the text goes over multiple pages.

The rectangular horizontal bounding box (dotted) of rotated objects catches other objects into a single article.

Objects in an article entity are sorted TOP - DOWN if the chain order does not command anything else.

In this example, the chain order is changed to export a different flow of reading:

First the lead box, then the title and as the last box the text.

Box#1: This box is chained with the TITLEbox. Each box which catches an other box builds a new combined rectangular bounding box to catch more boxes into the same article.

Boxes with ‘unassigned’ content do NOT catch other boxes to an article.

An other non-cathing box is a line.

Box#2: This box should be catched by the combined bounding box of TITLEbox and Box#1. However, in the export dialog we have checked “Chained boxes don’t catch”

Box#3: This box is not covered by any catching bounding box. But, it is grouped with Box#2!

If you have a column with several articles (like ‘Notes’), on a colored background box, then define this background box to have ‘unassigned’ content to export all articles separately.

If you want them to be exported as a single article with several sub-articles, then define the background box as text or image.

Box#4: The image on the left as well as this text box are standalone elements.

If the check box “Chained boxes don’t catch” were not be checked, Then these 6 elements would have been merged into a single article. Except Box#5

Box#5: This box does not touch any of the above boxes or bounding boxes and therefore is exported as a standalone article. It would be catched only if the catch radius would be large enough.

The exported XML data format is the same for most output modes. However, varying embedded XSL transform sheets control the behavior in a browser. Except „Article List Simple XML/HTML“ creates a simplified XML format.

When exporting page JPEGs (standard for flip books), the width of these page previews may be stated here. 500 means 500 pixels in width.

Multiple sizes of page images are stated like this:

500//800//1000

A maximum of 4 page sizes may be given. Depending on the screen size, the ideal page image will be loaded automatically.

The higher the image DPI, the better the image.

90 results in a good quality page JPEG at a reasonable file size.

When checked, a PDF of each single page is created in the selected quality.

When checked, a PDF of the entire document is created in the selected quality.

When checked, double page PDFs are created.

When checked, all additional elements and attributes available as PRO attributes are exported. See chapter „Technical Reference“.

– No splitting:

Box chains are not unchained. The entire text of the box chain is attached to the first box.

– Split at page change:

Chains crossing the page boundary ar unchained. This allows a page-wise flipping through a book’s pages.

– Split ALL chained frames:

All chained boxes are split.

 

By default, images are exported in JPEG format.

See previous article on image sizes.

When checked (default), output images always are re-converted even if they already exist.

Catch Radius: Default setting is 0. This means, that touching boxes are captured into the same article. Increasing the radius (in pixels), results in catching more boxes positioned in the surrounding area.

The check boxes suppress the catching behavior of certain boxes like for example boxes with ‘Unassigned’ content or empty text and image boxes.

 

These options allows to prevent unused elements from being exported.

To ‘Exclude Layers:’ specify the layers as a comma separated list of layer names like:
noexp,images,whatever

Various options controlling the behavior in a browser.

 

If empty, a CSS matching the documents styles is created using the document’s name as file name. If set (for example NYT.css), a CSS named NYT.css is created if it not already exists.

When checked, Special characters from style names are replaced by plain ASCII characters.

These options are used to (for example) to prevent users from clicking on images.

 

Various information on output paths, settings file and transformer path.

ALWAYS use paragraph or character style sheets to style your text!

Styles contained in a document are exported into an external CSS file (Cascading Style Sheet), and enables us to let the text look as expected in any medium. Like this, it is very simple for a web developer to modify the appearance of text when viewing it online within a browser.

So: Do not set paragraph and character formatting ‘attribute by attribute’ but use styles! ‘Manually’ changed attributes like font family, the size, bold and italic are more difficult to customize for browser views.

The CSS file is exported to the folder ‚XSLCSS‘ within the ‚Export‘ folder structure and receives a name similar to the original InDesign document, ending with the filename extension ‚.css‘.

The style names used in InDesign may be found in this .css file as class names but, after all, they are still recognizable.

These style sheets for the browser may be adapted with any standard text editor to match the display need on the Internet: for sure, the original font family used for InDesign will be replaced with a font like ‘Verdana’ which is a save font for Internet applications. No problem to adjust the background color for special titles like the section bars in this document.

Distinct, uniquely identifiable document names mainly make sense when data will be transferred into a database, especially to full-text search databases.

Name your documents like this:

A shortcut for the object, for example NYT for “New York Times“ with an added issue date. So: The NYT Newspaper issue on day 14 of September 2008 would have the name:

As a separator in the file name always use an underscore.

If you put standalone documents on the Internet, this naming convention is for your understanding and pleasure only.

To bypass the problem of inadequate fonts when printing, text often is converted to Outlines and embedded into the document. This mainly is a common praxis when producing ads received from online advertisers.

Outlines, also known as paths, may not be re-translated to browser-readable characters and therefor are lost during the export process and will appear as empty box in a browser!

For aesthetic reasons people like to manually format text lines.

Such manually inserted line and paragraph breaks are exported too and lead to unwanted line breaks in a browser view: A line break in the middle of a sentence, a single word on a line and so on.

Compared to a printed document, on the Internet a limited number of fonts is acceptable only.

Rotated objects always are exported in the un-rotated state. A browser is not able to rotate images or text.

If you have to rotate an image for print output, then do this (in your preferred imaging program) in a way, that your needs for print and the un-rotated web output conform to your requirements.

If you have defined recurring elements (like page heads) on a master page but need to export their content, then you have to explicitly place them on the real document pages.

There are many ways to produce a publication. a) All pages in a single InDesign document or b) Each page is contained in its own document. c) Chapter by chapter and all these chapter documents are organized in an InDesign book file.

«BatchXSLT for InDesign» can handle this! It creates a flip page book containing the entire publication.

All the rest is done automatically: open each document and export it and then merge them all into one output file.

If the imported pages have the section page number set, the files listed in the book must not be sorted.

Just to show how read-flow can be controlled:

 

The upper image of this article is anchored right before the paragraph end in listed item 3.

 

The lower image is anchored after item 4.

 

Both images then are positioned outside the parent text box by setting the X and Y position at the Anchored Objects options menu.

The look and feel of the created HTML file, the flip or sliding page ebook, is just one of the countless possibilities to visualize the initially exported XML data.

Like mentioned before, the exported base data is plain “All Purpose XML”. “All Purpose XML” also means to be able to display it as such a flipping pages ebook.

A widespread application also is to push article by article into an existing web system.

An other application is to build an own e-paper system or an article database which rely on this XML.

All those who want to use the functionality of the created “Standard” eBook may read the following articles to learn how and where adjustments can be made.

Use the developer tool of your browser. It helps you to find the CSS class names you might want to change!

The following screen shot shows what fields to use from InDesign’s Document Info Panel, to automatically set the web site’s title, logo, link and meta tags.

The window to set the document information may be found in the InDesign main menu:

File -> File Info

Document Title –> Builds a web site title and goes into the HTML title tag

Author –> follows the web site title

Copyright Info URL –> follows the Author on the same line

The red shaded part of the Description goes into the meta tag ‘description’

The yellow shaded part of the Description controls the logo area:

The logo can be controlled through a list of keyword=value pairs separated by ‘*#*’

The entire Description string (in a single line) for this Guide is:

Where the keyword=value pairs are (all keys and values are optional):

These fields may include XHTML Tags:

This allows, for example, to define additional buttons or a different formatting.

Example for the CopyRight Info:

<a href=“http://www.mydomain.com/manual.pdf“ title=“To the Manual“>Manual</a>

The look and feel of the created web site is controlled by external CSS and Javascript contained in the ‘XSLCSS’ folder within the ‘Export/out/...’ folder structure.

If you want to modify the appearance of the site, you need to make changes in some of these files.

 

In the XSLCSS folder a CSS file can be found named like the original document: MyDocument.css. It contains the styles used to represent the exported document’s fonts. Use this CSS to adjust font size and family, paragraph alignment, indents and more.

 

The subfolder XSLCSS/flipbook/ contains a file named flipbook.css which can be changed to adjust the web site’s look: Background images, logo, button positions and more.

Example to set a different logo:

 

The behavior, the user interaction is controlled by the Javascript ‘flipbook.js’ contained in the subfolder XSLCSS/flipbook/. The source to this packed version can be requested by licensed users.

An other Javascript named ‘custom.js’ contains the content of the ‘Quick Links’ popup at the web site’s top right corner.

The flipping pages eBook can adjust itself to any monitor size.

By default, scaling is enabled (but for IE 7 and 8 which can not scale).

In the program package you may find the so called XSLCSS Master Folder:

*Program folder*/BatchXSLT4InDesign/BatchXSLT/XSL/XSLCSS

The entire content of this folder is copied into the “Export” folder structure during a document export if it does not already exist there.

So, if you make changes in any of the files and whish that all the changes become permanent for all other exports then copy the changed file(s) into the XSLCSS Master Folder.

Example: You have changed the CSS reflecting the document’s styles and want them to be used for any further exports (same Newspaper new issue) then copy it into the Master Folder.

 

Hint: If such an adjusted CSS file exists under the chosen name within the XSLCSS folder it will never be overwritten!

 

The exported HTML eBooks may dynamically be integrated into an existing web site!

The HTML may be integrated into an iFrame or into a DIV element!

The page images of a web site are loaded dynamically– this means:

The first few page images are loaded immediately for readers can start reading and navigating very fast. The remaining pages are loaded in background.

This behavior can be adjusted.

Example: A certain amount of page images should be loaded immediately, other pages on demand only.

 

Many of such settings easily can be adjusted by programmers.

Several elements can be influenced via CSS and/or URL parameter. Either this takes place in the „flipbook.css“ or at the browser’s address line when calling the book HTML.

The special class defined in the CSS are solely used by the Javascript „flipbook.js“ to manipulate page elements.

 

Example using URL parameter: www.mysite.com/data/DB/..../mybook.htm?thumbs=0&toc=0

Means: Turn off the scrollable page navigation and the table of contents button

Such a call with parameters does not work for Internet Explorer and local files.

 

Using URL parameters a given page and/or article may be opened when the web site loads.

 

Example using URL parameters: www.mysite.com/data/DB/..../mybook.htm?p=3&a=9

Means: Open page 3 and show article with ID 9

 

Such a call with parameters does not work for Internet Explorer and local files.

 

Open the HTM file in a plain text editor.

Search for the article via text content.

The found article is contained in a HTML DIV Element

The attribute „id“ denotes the article ID as well as the page number:

In the browser click on an article. The article display window opens. Leave the mouse on an empty area until the tool-tip shows the article’s ID.

 

The following diagram illustrates, how data is stored into a clear and self-explaining folder structure, so it can simply be copied to any type of publishing medium.

The position of the folder ‚XSLCSS‘ is most important! It contains the programs to turn the static plain XML data into an interactive document for Browsers.

These programs are referenced from the XML and HTML file relatively to their own location in the folder structure. The default setting is:
„../../../XSLCSS“.

We assume that you will not make document exports for your own pleasure, you might want to publish your text and images to the public.

Viewing exported eBooks on your local machine exactly works the same way on any other medium!

 

Copy the folder structure with the exported data to any web server using an FTP upload program. Keep in mind, that the folder „XSLCSS must be reachable relatively to the exported data.

 

The folder „XSLCSS“ is accessed by the XML and HTML files relatively to their own location. For example: ../../../XSLCSS

 

After having copied all Files and folders you may set a link on your web site pointing to the HTML file.

 

 

You may copy all data in the same manner as you would transfer it on an Internet server.

Not everybody knows how to use FTP transfer programs or has one available.

The software package «BatchXSLT for InDesign» contains a Javascript, which helps to load the exported data on a web server. The script is named „ftpToWebArchive.jsx”.

As you already have made it available to InDesign during the previously completed software installation, you now may find a list item in InDesign’s Scripts Palette.

Call it with a double click and the main FTP Transfer window pops up – see below image:

Enter the information for the following fields:

for example: www.aiedv.ch

This is the base path to the data folder on the web server like „data/ePaper“ directly below the „FTP Domain Name“.

 

The data structure below the path given in „Source Data Path“, will be copied 1 to 1 into the „Data Root Path“. The folder hierarchy will be preserved.

 

If this sounds too cryptic to you, then you should ask your web master for help.

These are the user name and associated password which will enable BatchXSLT to log into the FTP server and to transfer data.

Activate the check box ‚Save these settings‘ for the following calls of this script will not need any further details to start a transfer.

 

Discussing this topic would go beyond the scope of this guide.

Please, read the manual to integrate the full-text search module. It may be found in the software package at the folder

In case of troubles: ask your web master for help.

If anything does not work like expected, then you may set «BatchXSLT for InDesign» into the DEBUG mode.

Do it this way:

Open the file

with a simple text editor and change the line:

to

Restart «BatchXSLT».

BatchXSLT is a very powerful fully automatable XML Transformer for all machines with installed Java version 1.6 or newer.

You can use it for all your XML transformations, either in Drag/Drop mode or in batch mode.

Settings made in the main export menu to create a certain type of export can be saved using any desired name and then can be restored to create the same type of export again.

These settings may be found within your HOME folder at the path:

with the file name extension „.set“

In all cases where you have trouble like empty XML/HTML output or no converted images, check the LOG file. You can find it at your HOME folder and is named

There might be some older log files named .txt01, .txt02 ...

Open it with a plain text editor.

If there can be not found any hint, then package your InDesign document (with images and fonts), zip (or stuff) the package folder and email it along with the log file to us. If the files are too large to send by email, put it on a web server and send us the link for we can download it.

 

This manual can be found online at:

Trash the folders:

“BatchXSLT4InDesign” contained in the system’s Application folder,

“BatchXSLT4InDesign Scripts” in InDesign’s Script Panel folder,

“BatchXSLT4InDesignComm” and “Export” in your Home folder

 

Use the uninstaller found in the Application folder.

And then trash:

“BatchXSLT4InDesignComm” and “Export” in your Home folder

THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PRODUCER OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.