Changeset 27115 for documentation


Ignore:
Timestamp:
2013-03-25T08:16:09+13:00 (11 years ago)
Author:
jlwhisler
Message:

Changes to PDFbox through Associated files. Added |3.05 to Version’s current attribute. Added AutoText for GS3 to correspond with GS2’s coredm keys – so tutorials for GS3 can be generated properly from a Greenstone 3 installation. Modified format statement for equivalent document link in associated files.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • documentation/trunk/tutorials/xml-source/tutorial_en.xml

    r27114 r27115  
    11231123</Title>
    11241124<Prerequisite id="word_pdf_collection"/>
    1125 <Version initial="2.85" current="2.85"/>
     1125<Version initial="2.85" current="2.85|3.05"/>
    11261126<Content>
    11271127<Comment>
     
    11641164</Title>
    11651165<SampleFiles folder="Word_and_PDF"/>
    1166 <Version initial="2.70" current="2.85"/>
     1166<Version initial="2.70" current="2.85|3.05"/>
    11671167<Content>
    11681168<Text id="ep-2">Greenstone converts PDF files to HTML using third-party software: <AutoText text="pdftohtml.pl" type="italics"/>. This lets users view these documents even if they don't have the PDF software installed. Unfortunately, sometimes the formatting of the resulting HTML files is not so good.</Text>
     
    13591359<Text id="ew-a">Enhanced Word document handling</Text>
    13601360</Title>
    1361 <Version initial="2.70w" current="2.85"/>
     1361<Version initial="2.70w" current="2.85|3.05"/>
    13621362<Prerequisite id="word_pdf_collection"/>
    13631363<Content>
     
    13741374</NumberedItem>
    13751375<NumberedItem>
    1376 <Text id="ew-5"><b>Build</b> the collection. You will notice that the Microsoft Word program is started up for each Word document&mdash;the document is saved as HTML from Word itself, to get a better conversion. <b>Preview</b> the collection. In the <AutoText key="coredm::_Global:labelTitle_"/> list, notice that <Path>word03.doc</Path> and <Path>word06.doc</Path> now have a book icon, rather than a page icon. These now appear with hierarchical structure.</Text>
     1376<Text id="ew-5"><b>Build</b> the collection. You will notice that the Microsoft Word program is started up for each Word document&mdash;the document is saved as HTML from Word itself, to get a better conversion. <b>Preview</b> the collection. In the <MajorVersion number="2"><AutoText key="coredm::_Global:labelTitle_"/></MajorVersion><MajorVersion number="3"><AutoText key="gs3::metadata_names::Title.buttonname" /></MajorVersion> list, notice that <Path>word03.doc</Path> and <Path>word06.doc</Path> now have a book icon, rather than a page icon. These now appear with hierarchical structure.</Text>
    13771377<Text id="ew-6">The default behaviour for <AutoText text="WordPlugin"/> with <AutoText text="windows_scripting"/> is to section the document based on <AutoText text="Heading 1" type="quoted"/>, <AutoText text="Heading 2" type="quoted"/>, <AutoText text="Heading 3" type="quoted"/> styles. If you open up the <Path>word03.doc</Path> or <Path>word06.doc</Path> documents in Word, you will see that the sections use these Heading styles.</Text>
    13781378<Text id="ew-7">Note, to view style information in Word 2003, you can select <Menu>Format &rarr; Styles and Formatting</Menu> from the menu, and a side bar will appear on the right hand side. (In Word 2007 and later, find the <Menu>Change Styles</Menu> button on the far right of the menu ribbon. Click on the tiny <Menu>Expand</Menu> icon to its bottom right to display the styles side bar.) Click on a section heading and the formatting information will be displayed in this side bar.</Text>
     
    14831483</Title>
    14841484<Prerequisite id="word_pdf_collection"/>
    1485 <Version initial="2.85" current="2.85"/>
     1485<Version initial="2.85" current="2.85|3.05"/>
    14861486<Content>
    14871487<Comment>
     
    15221522<NumberedItem>
    15231523<Text id="assoc-files-15">Building the collection at this point will have the effect that internally Greenstone will have captured this relationship between the different file versions of the same documents; however, until we make some adjustments to the format statements, none of this will be visible to the end-user. The collection built at this point (with default settings) allows a user to search the text from the Word document, browse by title metadata and so on, but when it comes to the point of viewing a document there will only be the choice of viewing the Word version of the document, or the HTML version that Greenstone automatically generates by processing the Word document.</Text>
    1524 <Text id="assoc-files-16">To go beyond this, the key change to make is to alter the part of the <MajorVersion number="2">default VList statement that says:</MajorVersion><MajorVersion number="3"><AutoText text="documentNode"/> template of the <AutoText key="coredm::_Global:labelBrowse_"/> format statement which chooses between <Format>thumbicon</Format> and <Format>srcicon</Format>, and replace this with a reference to <Format>equivDocIcon</Format> instead.</MajorVersion></Text>
     1524<Text id="assoc-files-16">To go beyond this, the key change to make is to alter the part of the <MajorVersion number="2">default VList statement that says:</MajorVersion><MajorVersion number="3"><AutoText text="documentNode"/> template of the <AutoText text="Browse" /> format statement which chooses between <Format>thumbicon</Format> and <Format>srcicon</Format>, and replace this with a reference to <Format>equivDocIcon</Format> instead.</MajorVersion></Text>
    15251525<MajorVersion number="2">
    15261526<Format>
     
    15561556<MajorVersion number="3">
    15571557<Text id="assoc-files-20-3">The second (more minor) change in this edit is to simplify the statement a bit. The original uses a <Format>&lt;gsf:choose-metadata/&gt;</Format> statement to show a thumbnail version of the document, if Greenstone has one, in preference over the source icon. Since in this collection we have no thumbnails generated, it has been simplified by eliminating the <Format>&lt;gsf:choose-metadata/&gt;</Format> combination and going straight to the <AutoText text="ex.equivDocIcon" type="italics"/> metadata item.</Text>
    1558 <Text id="assoc-files-21-3">To make the change then, switch to the <AutoText key="glidict::GUI.Format"/> panel and edit the <AutoText text="documentNode"/> template of the <AutoText key="coredm::_Global:labelBrowse_"/> format statement</Text>
     1558<Text id="assoc-files-21-3">To make the change then, switch to the <AutoText key="glidict::GUI.Format"/> panel and edit the <AutoText text="documentNode"/> template of the <AutoText text="Browse" /> format statement</Text>
    15591559<table>
    15601560<th>
     
    15891589<Format>
    15901590&lt;td valign=&quot;top&quot;&gt;<br />
    1591   <highlight><Tab n="1"/>&lt;gsf:link type=&quot;equivdoc&quot;/&gt;</highlight><br />
     1591  <highlight><Tab n="1"/>&lt;gsf:metadata name=&quot;equivDocLink&quot;/&gt;<br />
     1592  <Tab n="1"/>&lt;gsf:metadata name=&quot;equivDocIcon&quot;/&gt;<br />
     1593  <Tab n="1"/>&lt;gsf:metadata name=&quot;/equivDocLink&quot;/&gt;<br />
     1594  </highlight>
    15921595&lt;/td&gt;<br />
    15931596&lt;td valign=&quot;top&quot;&gt;<br />
Note: See TracChangeset for help on using the changeset viewer.