en:release:3.09_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:3.09_release_notes [2020/05/10 23:32] – anupama | en:release:3.09_release_notes [2021/02/09 04:15] – [Filenames in collections should not contain &, < and >] anupama | ||
---|---|---|---|
Line 332: | Line 332: | ||
==== Troubleshooting ==== | ==== Troubleshooting ==== | ||
+ | |||
+ | === Some perl scripts don't run properly or to completion === | ||
+ | //**If you're running Greenstone 3 on a non-English locale**// and certain perl scripts don't run properly or completely, such as when you run '' | ||
=== You see an empty page when visiting the Greenstone 3 library home page on Windows === | === You see an empty page when visiting the Greenstone 3 library home page on Windows === | ||
Line 425: | Line 428: | ||
If you get this error, then please install the CGI module for your system perl. | If you get this error, then please install the CGI module for your system perl. | ||
====Work Arounds==== | ====Work Arounds==== | ||
- | ===Filenames in collections should not contain | + | ===Using filenames containing |
- | In order to have better handling of different file and filename encodings, a [[http:// | + | The Enrich panel in GS3.10's GLI is better able to handle |
+ | - &, < and > | ||
+ | - and other non-basic ASCII characters. | ||
+ | When you create a collection and assign it metadata in GLI that contains | ||
+ | |||
+ | The second set of characters listed above are still not recommended for use in metadata when dealing with a remote GS3 server, as that has to do with successfully transferring characters from an operating system in one file system encoding on the client side to possibly another operating system using another file system encoding on the GS3 server side. | ||
+ | |||
+ | It is only GLI's Enrich pane that has been fixed up to support both sets of characters in metadata. No other part of Greenstone has been fixed to cope with these characters, should they likewise struggle with them. | ||
- | A workaround | + | The fix is often in the form of adding hex encoded entities into the metadata.xml file and decoding |
===Greenstone applets (Phind, Collage) crash Firefox=== | ===Greenstone applets (Phind, Collage) crash Firefox=== | ||
See [[https:// | See [[https:// |
en/release/3.09_release_notes.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1