en:release:2.87_release_notes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
en:release:2.87_release_notes [2017/09/27 07:42] – [Important Changes and Bug Fixes] anupama | en:release:2.87_release_notes [2020/04/23 07:05] – [Troubleshooting and other Questions] anupama | ||
---|---|---|---|
Line 3: | Line 3: | ||
**Release Name:** 2.87 | **Release Name:** 2.87 | ||
- | **Release Date: | + | **Release Date: |
** Released: ** | ** Released: ** | ||
+ | * Greenstone v2.87: The official Greenstone 2.87. 01 Oct 2017 \\ Binaries for Windows, GNU/Linux 32 and 64 bit, Mac Mountain Lion and Mac El Capitan. Mac Mountain Lion and 32 bit linux binaries were only spot tested. The other 3 binaries were tested more extensively. The sole Windows binary is, as usual, for both 32 and 64 bit machines and was largely tested on **Windows 10** this time.\\ [[http:// | ||
** Release Candidate History ** | ** Release Candidate History ** | ||
Line 34: | Line 35: | ||
< | < | ||
- | The small Greenstone Server Interface (GSI) dialog will display. Pressing its Enter Library button will open a browser onto your Greenstone Digital Library home page.(*) | + | The small Greenstone Server Interface (GSI) dialog will display. Pressing its Enter Library button will open a browser onto your Greenstone Digital Library home page.(1) |
- | By default, the web servers restrict access to Greenstone pages to the local machine. To change this, go to File > Settings in the Greenstone Server Interface dialog, and tick "Allow external connections" | + | By default, the web servers restrict access to Greenstone pages to the local machine. To change this, go to File > Settings in the Greenstone Server Interface dialog, and tick "Allow external connections" |
**Note:** The Windows version of Greenstone includes two server applications: | **Note:** The Windows version of Greenstone includes two server applications: | ||
Line 49: | Line 50: | ||
< | < | ||
- | First, as in (1) above, the Greenstone Server Interface (GSI) dialog will appear. Eventually the Greenstone Librarian Interface (GLI) dialog will appear. Refer to the [[en: | + | First, as in (1) above, the Greenstone Server Interface (GSI) dialog will appear.\\ ** Note**: If you're using the included //apache httpd server// and running GLI starts by requesting you for the Local Library URL, then it expects the library home URL that's of the form '' |
- | (*) If the web page displays a " | + | (1) If the web page displays a " |
- | < | + | < |
**To change the GLI interface language**, run GLI, go to the '' | **To change the GLI interface language**, run GLI, go to the '' | ||
Line 67: | Line 68: | ||
When the client-GLI starts up, a small dialog appears asking you to enter the URL of the remote Greenstone server' | When the client-GLI starts up, a small dialog appears asking you to enter the URL of the remote Greenstone server' | ||
- | | + | * To get your Greenstone installation set up as a remote server so that other GLI clients can connect to it, refer to the section [[2.87_Release_Notes# |
- | | + | |
==== Installing in text-only mode ==== | ==== Installing in text-only mode ==== | ||
* Refer to [[http:// | * Refer to [[http:// | ||
+ | |||
+ | |||
+ | ==== Adding source code to a binary release ==== | ||
+ | Make sure to select the " | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | |||
+ | |||
+ | ==== Installing a source release ==== | ||
+ | |||
+ | Make sure to select the " | ||
+ | |||
+ | * [[http:// | ||
+ | * [[http:// | ||
Line 107: | Line 121: | ||
+ | ===== Learning to use Greenstone ===== | ||
+ | If your Greenstone is up and running and you're ready to start learning about how to use Greenstone, refer to the [[en: | ||
+ | |||
+ | |||
+ | ===== Troubleshooting and other Questions ===== | ||
+ | * Have a look at the [[http:// | ||
+ | |||
+ | * If not, then please consult the Greenstone FAQ at http:// | ||
+ | |||
+ | * If you're running Greenstone 2.87 on a machine where the version of Perl is later than 5.18 (e.g. perl 5.22), as may happen when you upgrade your Ubuntu to 16.04 or later, and your GLI does not start up properly, then first stop and restart GLI in debug mode to get better error reporting: '' | ||
+ | < | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/(/.*){ <-- HERE ,41}/ at / | ||
+ | AutoLoadConverters: | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^[a-z]{ <-- HERE 2..}/ at / | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^[a-z]{ <-- HERE 2..}/ at / | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/ | ||
+ | Getting Download Info: [perl, -S, / | ||
+ | WGet thread is waiting for DownloadJobs. | ||
+ | Failed when trying to parse downloadinfo.pl -describeall | ||
+ | java.lang.Exception: | ||
+ | at org.greenstone.gatherer.gui.DownloadPane.loadDownloadersInfo(DownloadPane.java: | ||
+ | at org.greenstone.gatherer.gui.DownloadPane.< | ||
+ | at org.greenstone.gatherer.gui.GUIManager.display(GUIManager.java: | ||
+ | at org.greenstone.gatherer.Gatherer.openGUI(Gatherer.java: | ||
+ | at org.greenstone.gatherer.GathererProg.main(GathererProg.java: | ||
+ | java.lang.NullPointerException | ||
+ | at org.greenstone.gatherer.gui.DownloadPane.< | ||
+ | at org.greenstone.gatherer.gui.GUIManager.display(GUIManager.java: | ||
+ | at org.greenstone.gatherer.Gatherer.openGUI(Gatherer.java: | ||
+ | at org.greenstone.gatherer.GathererProg.main(GathererProg.java: | ||
+ | java.lang.NullPointerException | ||
+ | at org.greenstone.gatherer.gui.DownloadPane.< | ||
+ | at org.greenstone.gatherer.gui.GUIManager.display(GUIManager.java: | ||
+ | at org.greenstone.gatherer.Gatherer.openGUI(Gatherer.java: | ||
+ | at org.greenstone.gatherer.GathererProg.main(GathererProg.java: | ||
+ | ShutDownHook called... | ||
+ | Attempting to forcibly terminate the GS server... | ||
+ | Issuing stop command to GS2 Local Library Server. Waiting for GS2 server to stop... | ||
+ | Successfully stopped GS2 server. | ||
+ | Done. | ||
+ | </ | ||
+ | |||
+ | 0. Exit GLI in the proper manner if it's running. | ||
+ | |||
+ | 1. Optional: Back up your GS2.87' | ||
+ | |||
+ | 2. Download the '' | ||
+ | |||
+ | 3. Five files should have been extracted: | ||
+ | * Put the 3 Plugin.pm files into your GS2.87' | ||
+ | * put Escape.pm into the '' | ||
+ | * put PP.pm into into the '' | ||
+ | |||
+ | 4. Use a //new terminal// to launch GLI or any commands that previously failed with errors. Hopefully GLI will launch successfully now. | ||
+ | |||
+ | ===== Useful information ===== | ||
+ | * When you've built a collection of documents, you may discover that there appears to be a copy of all these documents in the collection' | ||
+ | By default, Windows doesn' | ||
=====To turn on RSS support: | =====To turn on RSS support: | ||
Line 113: | Line 194: | ||
=====Enabling user comments===== | =====Enabling user comments===== | ||
Refer to the Greenstone 2 tab of [[http:// | Refer to the Greenstone 2 tab of [[http:// | ||
+ | |||
+ | ===== For those migrating from earlier versions ===== | ||
+ | //This section contributed by John Rose for Greenstone 2.86 and copied here.// | ||
+ | |||
+ | Some of the new Greenstone features which facilitate the creation of institutional repositories and other open access collections: | ||
+ | |||
+ | **1. OAI server** | ||
+ | |||
+ | Your collections can easily be made available for remote harvesting using OAI-PMH protocol, which works silently in parallel with normal web access to the collections. All that you have to do is to add a bit of configuration data in the oai.cfg text file in the etc subdirectory under the Greenstone home directory. The data to specify is explained in comment lines in the above file. If the collections to be made available through OAI-PMH do not all use Dublin Core metadata or one of the two other standard OAI metadata sets, the oai.cfg file will need to contain mapping data to translate your metadata into one of the Greenstone OAI-PMH metadata sets (also explained in the comments to the oai.cfg file). | ||
+ | |||
+ | OAI-PMH support has been provided for some time by Greenstone, but there have previously been a few functional gaps, as well as a bug in version in 2.84. From version 2.85 onwards, all official OAI-PMH validation criteria have been tested and satisfied; you will be able to validate your own OAI-PMH server using instructions given in the release notes. If you don't specify the urls for the associated documents in the metadata, the system can automatically generate internal urls so that users can access the full documents from the harvested OAI records. You will also now be able to harvest OAI-PMH records and the associated documents residing in external Greenstone collections (in 2.84, harvesting worked to access information in non-Greenstone collections, | ||
+ | |||
+ | Much information is put up on the web without clear specification of the concerned intellectual property rights. Although this is not good practice in general, when activating the OAI server special care should be taken to ensure that your documents are really available under open access conditions (in the public domain or freely distributable and re-distributable under an open access license such as Creative Commons). Greenstone can only take care of the technical access - for legal and organisational considerations, | ||
+ | |||
+ | Once your OAI server is operational, | ||
+ | |||
+ | **2. PDF metadata** | ||
+ | |||
+ | Prior to version 2.83, reliable import of, and metadata extraction from, pdf files was limited to PDF versions 1.4 and earlier. Starting with 2.84 a new "PDF Box extension" | ||
+ | |||
+ | By using the PDF Box extension, you can extract any metadata entered in standard manner in a pdf file, i.e. the traditional pdf metadata (Author, Title, Subject, Keywords) and/or the newer XMP format metadata (including user defined fields). In general, we recommend that for users interested in extracting PDF metadata, it is better to use the PDF Box extension, even for pdf files in version 1.4 or earlier. | ||
+ | |||
+ | Using the PDF metadata extraction facility means that for PDF files generated by the users with metadata included (either directly with a tool like Acrobat, or by generating a PDF file from a package like Word which can transfer Word metadata to the generated PDF file), these metadata can be automatically incorporated into a Greenstone collection (without having to enter them in GLI or compile a metadata.xml file). This could clearly be of interest to open access applications, | ||
+ | |||
+ | There is a catch: the metadata extraction procedure may not work flawlessly on recent version PDF files which are not " | ||
+ | |||
+ | **3. Section handling for PDF files** | ||
+ | |||
+ | For several years Greenstone has proposed a facility to automatically generate internal section (chapter) information from a Microsoft Office (e.g. Word), OpenOffice/ | ||
+ | |||
+ | Word files can be treated in this way if a compatible version of Word is installed in the computer in which a collection is built (see the tutorial at %%http:// | ||
+ | |||
+ | An example collection has now been prepared to show how this can be extended to PDF files (see %%http:// | ||
+ | a. develop a Word version and a PDF version of the document (conversion of the Word version to PDF or vice-versa); | ||
+ | b. make sure that the heading formats in Word are consistent with what you want for sections and subsections; | ||
+ | c. import the Word file into Greenstone specifying the PDF file as an associated file; | ||
+ | d. use the format statement guidance in the worked example to be able to search on the document subsections and also display the hit terms in the original PDF file (Word or OpenOffice/ | ||
+ | |||
+ | An alternative, | ||
+ | |||
+ | More complete documentation is being developed for all of the above techniques, and we will keep you informed on its progress. | ||
+ | |||
+ | **4. Migrating to 2.87** | ||
+ | |||
+ | To switch to version 2.87 from an earlier Greenstone version with minimal risks, you could i) back up your collections, | ||
+ | |||
+ | If you want to transfer information on users and user groups, the corresponding databases (users.gdb, key.gdb) should be copied from the etc sub-directory in the old collection to the new one. Of course if you have customised your previous version (main.cfg, style.css, macros, etc.), the old versions should also be copied to the new installation. When all is working perfectly, the old installation can be deleted. | ||
+ | |||
+ | |||
+ | ===== Further Notes on Installation and Running ===== | ||
+ | ==== Apache HTTPD Notes ==== | ||
+ | |||
+ | Greenstone binary releases come with the Apache HTTPD web server precompiled and installed by default into Greenstone/ | ||
+ | * To uninstall it, delete the Greenstone/ | ||
+ | * If you have an existing Apache web server installed and you want to set it up to serve your Greenstone, copy the appropriate bits out of Greenstone' | ||
+ | * If you want to use an alternative webserver, then set it up appropriately, | ||
+ | * If you had installed Apache Httpd previously for the sole purpose of serving Greenstone, then you may like to uninstall it and use the one installed by Greenstone. | ||
+ | |||
+ | |||
+ | ==== Additional notes related to running Greenstone on Windows ==== | ||
+ | On Windows, running the Greenstone Librarian Interface (GLI) or the Greenstone Server Interface (GSI) manually from a DOS prompt could be useful in diagnosing anything that goes wrong, since it keeps any messages that were displayed during program execution visible in the DOS window. | ||
+ | |||
+ | To run GLI or GSI from the DOS prompt, first go into your Greenstone installation directory and then | ||
+ | * to run the GSI, type: | ||
+ | < | ||
+ | * to run GLI, type: | ||
+ | < | ||
+ | |||
+ | ==== Notes on using a Terminal or DOS prompt ==== | ||
+ | On Macs, the Terminal is an application that can be found under Applications > Utilities > Terminal. | ||
+ | |||
+ | |||
+ | On Windows, you can start up a DOS prompt by going to Start > Run and then typing cmd. | ||
+ | |||
+ | To go to your Greenstone installation directory using your terminal, you would type: | ||
+ | < | ||
+ | On Windows you would use backslashes (\) in file paths, and on Linux and Mac you would use forward slashes (/). | ||
+ | |||
+ | On Linux and Mac, to run a shell script (Greenstone' | ||
+ | |||
+ | |||
+ | On Windows, to run a batch script (files that end on *.bat), just type its name out in full. | ||
+ | |||
+ | E.g. on Windows: | ||
+ | < | ||
+ | gs2-server.bat</ | ||
+ | |||
+ | E.g. on Linux or Mac: | ||
+ | < | ||
+ | ./ | ||
+ | |||
+ | ==== Using the gsicontrol script ==== | ||
+ | |||
+ | The gsicontrol.sh/ | ||
+ | < | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | </ | ||
+ | You can use it as follows | ||
+ | |||
+ | * In a command window, go to your Greenstone installation folder and run setup.bat (if on Windows) or ' | ||
+ | * Then run " | ||
+ | * Now run " | ||
+ | * In a browser, enter " | ||
+ | * Then type " | ||
+ | * To stop the webserver at any point, from your command window run " | ||
+ | * If you move your Greenstone 2.87 installation folder to another location at any point, then (with the server still stopped), you may first need to run " | ||
+ | * If you forgot the admin password (as is required to access the Administration Pages and to use Remote GLI), this can be reset by running " | ||
+ | |||
+ | ==== Notes on using GLI ==== | ||
+ | In GLI's File > File Associations, | ||
+ | * On Mac, you can type **'' | ||
+ | * To do the same on Windows, type **'' | ||
+ | * To attempt the same on Linux, try typing '' | ||
+ | ==== Working with Remote Greenstone and the GLI-Client ==== | ||
+ | |||
+ | **Instructions** | ||
+ | |||
+ | These instructions are more specific to current and recent Greenstone 2 releases than the [[http:// | ||
+ | |||
+ | The following are steps to follow if you're on **Windows**. On **Unix based systems**, you can skip steps 1 and 2, otherwise things are similar. For instance, on Unix systems, you'll want to launch *.bash or *.sh script equivalents to the batch files listed. Also, you'll want to use forward slashes (/) instead of the Windows' | ||
+ | |||
+ | |||
+ | 1. If the path to your Greenstone installation contains any spaces (i.e. if any of the containing folders wherein your Greenstone is ultimately located contain spaces in their names), open cgi-bin/ | ||
+ | < | ||
+ | Save any changes. | ||
+ | |||
+ | |||
+ | 2. Rename server.exe in your Greenstone installation folder to something else, say " | ||
+ | |||
+ | This is because you will need to use the included Apache web server for the remote Greenstone. By renaming the default library server in Greenstone 2, Greenstone will next look for the apache web server. | ||
+ | |||
+ | |||
+ | 3. Now run the Apache web server included with your Greenstone from the Windows Start Menu, or by opening a DOS prompt and typing the path to your Greenstone 2 installation and then running the gs2-server script. E.g. | ||
+ | < | ||
+ | gs2-server.bat</ | ||
+ | |||
+ | Alternatively, | ||
+ | |||
+ | |||
+ | 4. A dialog (the Greenstone Server Interface) will display. If you want remote clients accessing your Remote Greenstone Server, go to File > Settings of this dialog and tick "Allow External Connections" | ||
+ | |||
+ | It will open a browser and take you to a page like: %%http:// | ||
+ | |||
+ | OR: %%http://< | ||
+ | (where if port were the default 80 it won't be displayed, e.g. %%http://< | ||
+ | |||
+ | |||
+ | 5. Replace the " | ||
+ | < | ||
+ | E.g. %%http:// | ||
+ | (OR: %%http://< | ||
+ | |||
+ | At the end of the browser page, it is imperative that it says something like: | ||
+ | < | ||
+ | (If not check the error messages.) | ||
+ | |||
+ | |||
+ | 6. You may need to give read and write access to the collect folder. Once again, open a DOS prompt. Type the following, or the equivalent of the following for your computer' | ||
+ | < | ||
+ | On Linux you would do: | ||
+ | < | ||
+ | (If on Vista or Windows 7, you installed Greenstone in an Admin area, such as in Program Files, then you would need change the security settings of the collect directory: Right-click > Properties, then set the folder to " | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | 7. Use the browser to go to your Greenstone home web page again. | ||
+ | |||
+ | * Now click on the Administration Page link and add a new user: | ||
+ | * Click the Add a New User link to the left | ||
+ | * You'll be requested for the admin username (type " | ||
+ | |||
+ | |||
+ | 8. Enter the username and password for the new user. The password has to be between 3 and 8 characters long. | ||
+ | * In the Groups field, type " | ||
+ | * Press the Submit button. | ||
+ | |||
+ | |||
+ | 9. You can connect to this server from the Client-GLI application included with any Greenstone installation. Either on the current machine or another machine (assuming you want the Greenstone server on one machine and the client on another), use the " | ||
+ | < | ||
+ | client-gli.bat</ | ||
+ | |||
+ | |||
+ | 10. A dialog will eventually appear asking you for the URL of the Remote Greenstone server' | ||
+ | |||
+ | * If your client-gli is running from a different machine to where your Greenstone server is running, you need to specify the name of that remote machine hosting the Greenstone server: | ||
+ | |||
+ | * If the client-gli is running on the same machine, you can generally type " | ||
+ | |||
+ | |||
+ | 11. It will next ask you for a username and password. Type the values you entered for the new user you created in step 8. | ||
+ | |||
+ | |||
+ | 12. The client-GLI dialog should finally open, and it will look and behave mostly the same as the usual (local) GLI. | ||
+ | |||
+ | |||
+ | ==== Setting up your Greenstone OAI Server and using GLI to download over OAI from a Greenstone server ==== | ||
+ | |||
+ | **Useful resources** | ||
+ | * [[http:// | ||
+ | |||
+ | |||
+ | To get the Greenstone 2's OAI Server to work, edit the file **etc/ | ||
+ | < | ||
+ | repositoryId " | ||
+ | In addition, you will need to edit the same etc/oai.cfg file to also list any collections you want served over OAI. Add such collections by name to the **oaicollection** property. For example, if you have a Greenstone collection called " | ||
+ | < | ||
+ | If you're validating your OAI server and wish to test the resumptionToken, | ||
+ | < | ||
+ | |||
+ | For each collection meant to be served over OAI, edit **the collection' | ||
+ | < | ||
+ | maintainer <type your email here></ | ||
+ | Moreover, if you wish to validate your OAI server against the OpenArchives validator, you will need to remove the default admin email (greenstone@...) in the **creator** and **maintainer** email fields from the **collect/ | ||
+ | |||
+ | |||
+ | If you wish to validate your OAI server, visit %%http:// | ||
+ | |||
+ | However, before you can validate your OAI server and before you can try testing if GLI can download over OAI from it, there are a few things you need to do to make your Greenstone OAI server accessible to the outside world: | ||
+ | * If you're on windows, you will likely need to use the included Apache web server intead of the Local Library Server. To change over to using the Apache web server, change the file extension of server.exe which is found in the top-level your Greenstone installation (you can rename it to server.not for instance). | ||
+ | * Your Greenstone server machine' | ||
+ | * Once that's ready, you also need to tell the Greenstone server that it should make itself accessible to the outside world by turning on the "Allow External Connections" | ||
+ | * Press the Enter library button in the Greenstone Server Interface, and it should open the browser on the home page of your digital library. You will see a URL like: | ||
+ | < | ||
+ | Change it to | ||
+ | < | ||
+ | Note that you want the full hostname including domain. This is the URL you will want to feed into the OAI Validator at %%http:// | ||
+ | If the URL is not accepted for some reason, try pasting it in a new browser window, and suffix "? | ||
+ | < | ||
+ | |||
+ | For further information on your Greenstone OAI Server, read through [[en:OAI]]. | ||
+ | |||
+ | ==== Notes on setting up your Linux system to work with filename encodings alien to your filesystem settings ==== | ||
+ | |||
+ | UTF-8 is a common encoding used in filesystems and for data content. | ||
+ | |||
+ | If you are working on a UTF-8 system, then Java (and therefore GLI) will not give you access to files that do not have UTF-8 filenames. This means that in GLI, attempts to drag and drop files with names that are not UTF-8 will fail on such systems. | ||
+ | |||
+ | GLI will allow one to drag and drop files if the filesystem encoding was set to something that preserved the byte values of filenames (instead of destructively replacing characters that are not valid for the filesystem encoding with an " | ||
+ | |||
+ | Drag And Drop in GLI will work by default on Windows since it is not a UTF-8 filesystem, but rather one that has a large overlap with Native Latin 1. | ||
+ | |||
+ | However, some Linux systems are set to UTF-8 by default, while others do not even have other encodings installed so you can't switch over. | ||
+ | |||
+ | The solution to making GLI work with "alien filename encodings" | ||
+ | |||
+ | |||
+ | **INSTALLING AND APPLYING A NEW FILESYSTEM ENCODING ON A LINUX MACHINE:** | ||
+ | |||
+ | The instructions are derived from the thread of questions and answers [[http:// | ||
+ | |||
+ | First find out whether you are already working with a Linux system set to Native Latin 1 (ISO-8859-1). Check by typing the following in an x-term: | ||
+ | < | ||
+ | If the settings are indeed set to Native Latin 1, it should tell you that (en_US.)ISO-8859-1 is active. | ||
+ | |||
+ | |||
+ | A) INSTALLATION OF A NEW FILESYSTEM ENCODING (Native Latin 1/ | ||
+ | |||
+ | Installation of Native Latin 1 (ISO-8859-1), | ||
+ | < | ||
+ | export LANG=en_US.ISO8859-1</ | ||
+ | |||
+ | If it doesn' | ||
+ | |||
+ | 1. Open / | ||
+ | |||
+ | < | ||
+ | |||
+ | 2. Repeat the above step with the file / | ||
+ | |||
+ | 3. **Optional: | ||
+ | |||
+ | 4. Then in an x-term, run the following to install the new encoding: | ||
+ | |||
+ | < | ||
+ | |||
+ | 5. Restart the machine. | ||
+ | |||
+ | The above 5 steps need to be carried out **once** for en_US.ISO-8859-1 (Native Latin 1) to be supported by the machine. You would still need to apply the new encoding. | ||
+ | |||
+ | |||
+ | B) APPLYING THE NEWLY INSTALLED ENCODING AS THE FILESYSTEM (AND DISPLAY) ENCODINGS: | ||
+ | |||
+ | 6. Having restarted the machine, to make the newly-installed encoding the active one, run the following commands in an x-term again. You do not need Admin rights for issuing the following two commands: | ||
+ | |||
+ | < | ||
+ | |||
+ | export LANG=en_US.ISO8859-1</ | ||
+ | |||
+ | 7. You can check if it all worked by running: | ||
+ | < | ||
+ | Or by running: | ||
+ | < | ||
+ | It should tell you that (en_US.)ISO-8859-1 is active. | ||
+ | |||
+ | 8. Now run GLI from the same x-term to allow it to work with the Native Latin 1 filesystem encoding settings. | ||
+ | |||
+ | |||
+ | |||
+ | ==== Using Greenstone Plugin Extensions to process docx files and recent versions of PDF ==== | ||
+ | Two extensions are available for download: **Open Office and PDF Box**, to process more recent versions of MS office documents and PDF document respectively. | ||
+ | ==== OpenOffice==== | ||
+ | * The Open Office extension provides a document conversion facility if **Open Office //or// LibreOffice** is already installed on the system. In order to use the Open Office extension, | ||
+ | * You will need [[http:// | ||
+ | * you're on Windows and have OpenOffice/ | ||
+ | * you're on Linux and have OpenOffice or LibreOffice installed in a location different from "/ | ||
+ | * Once you have Open Office set up, download the Greenstone extension for it [[http:// | ||
+ | * Before you can use this (or any other Greenstone extension), you will need to quit GLI and GS2-server if either are open and then you will need to relaunch GLI (or run Greenstone scripts) from a fresh command terminal, in order for the extension to become available in the Greenstone environment. | ||
+ | * With OpenOffice and the extension installed and the Greenstone environment set up for this, Greenstone' | ||
+ | ====PDFBox==== | ||
+ | * The PDF Box extension provides support for conversion of PDF documents to text. It supports the latest PDF versions (unlike Greenstone' | ||
+ | * Download the extension [[http:// | ||
+ | * Before you can use the extension, you will need to quit GLI and GS2-server if either are open and then you will need to relaunch GLI (or run Greenstone scripts) from a fresh command terminal, in order for the extension to become available in the Greenstone environment. | ||
+ | * PDFBox generates HTML documents from the PDF that may contain more whitespace between lines and paragraphs than you'd wish. In such a case, you can fix this on a per-collection basis using GLI. Open your collection in GLI, go to the Format panel, select Format Features to the left and DocumentText to the right. In the text-area for HTML Format String below, create an HTML style element to set the top and margin bottoms on a paragraph element to 0. You need to escape curly braces with a back slash. In the end your format statement for DocumentText will look like: <br/> | ||
+ | < | ||
+ | < | ||
+ | p \{ | ||
+ | margin-top: | ||
+ | margin-bottom: | ||
+ | \} | ||
+ | </ | ||
+ | [Text] | ||
+ | </ | ||
+ | |||
+ | ====Usage history==== | ||
+ | If you wish to get some usage output into a file: | ||
+ | |||
+ | 1. Open up etc/ | ||
+ | < | ||
+ | to say: | ||
+ | < | ||
+ | Save the file. | ||
+ | |||
+ | 2. You will need to manually create a new text file called " | ||
+ | |||
+ | 3. Run the web server and usage.txt should become populated with information. | ||
+ | |||
+ | |||
===== Known Issues===== | ===== Known Issues===== | ||
en/release/2.87_release_notes.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1