TransXChange Publisher Beta Version 2.0f_1 (c) 2004 Crown Copyright. Developed by Kizoom limited. http://www.kizoom.com 27 October 2004 ============================================================ 1. Prerequisites Java Runtime Environment (JRE) version 1.4.2 (or later) Available from http://java.sun.com/j2se/1.4.2/download.html. To check your current Java version (a) Open a command prompt. (b) Type "java -version" at a command prompt. If you have java correctly installed, you should see a message telling you the version of Java currently installed. 2. Installation 2.1. Unzip the publisher distribution into a base directory on your machine. You should see the following top level contents. /TransXChangePublisher-app-2.0f_1.jar /documents /schema /transforms /catalog.xml /publish.bat The /schema directory includes the TransXChange XSD schema files - these are used to validate documents before publishing them. The /documents directory includes a sample document you can use to try out the publisher. 3. Running the publisher 3.1. Open a command prompt and change directory to the base directory where you installed the publisher. 3.2 Invoke the publisher by typing publish document_name For example, to run the publish documents\2.0f\linear.xml Unless otherwise specified, output is placed in the same directory as the input document The file name will be the same with a .pdf suffix, for example documents\2.0f\linear.pdf 3.3. You can type "publish -help" to see the allowed command values. 4. Command line parameters The publisher has a number of optional command line parameters publish [ [-vosa | -full | -timetableOnly] [-pdf | -docbook] -help] transXChange_file [output_directory] Type "publish -help" for more information. =================================================== 5. Limitations This is a beta version of The TXC publisher and has a number of limitations. Please report defect reports and other feedback to schemer@kizoom.com 5.1 Beta 'as is' Status - The publisher has only been tested on a Windows 2000 and XP platforms. - Only a limited set of test cases has been run so far. 5.2 Limitations on current use. - FlexibleServices not fully supported - Some other documentary annotations are not included, eg via points 5.3 Planned Further improvements to presentation and usability - Addition of Logo. - Embedding of supporting docs which are images (Pending minor schema revision to support these better) 6.0 Changes in 2.0f_1 - Support for 2.0f schema - Revised layout to follow VOSA form layout - Support for separate inbound/outbound - Segregate timetables by day type if appropriate : Monday-Friday, Saturday, Sunday - Support for large timetables with page overflow