Differences

This shows you the differences between two versions of the page.

--- en:release:3.09_release_notes [2019/12/13 04:25] – [You see an empty page when visiting the Greenstone 3 library home page] anupama
+++ en:release:3.09_release_notes [2021/02/09 04:15] – [Filenames in collections should not contain &, < and >] anupama
@@ Line 25: / Line 25: @@
   * Download the appropriate binary release for your operating system and run it.
-  * **Note to Mac users:** The security settings in newer Mac OS versions have been altered to by default disallow users from casually opening and running .dmg executables that are not from Apple itself. When attempting to open the Greenstone binary .dmg file, if it pops up an error warning about security, you will need to set up the Security on your Mac to allow you to run .dmg files downloaded from the internet. Otherwise the Greenstone mac binary will not run. To do this, Go to your Mac's System Preferences. Under "Personal", select Security & Privacy. In the General tab, tick "Allow apps downloaded from Anywhere", then confirm that you want to "Allow From Anywhere". You'll need to be admin to do this, otherwise click on the padlock at the bottom left of the Security & Privacy tab and log in as admin.
+  * **Note to Mac users:** The security settings in newer Mac OS versions have been altered to by default disallow users from casually opening and running .dmg executables that are not from Apple itself. When attempting to open the Greenstone binary .dmg file, if it pops up an error warning about security, you will need to set up the Security on your Mac to allow you to run .dmg files downloaded from the internet. Otherwise the Greenstone mac binary will not run. To do this, go to your Mac's System Preferences. Under "Personal", select Security & Privacy. In the General tab, tick "Allow apps downloaded from Anywhere", then confirm that you want to "Allow From Anywhere". You'll need to be admin to do this, otherwise click on the padlock at the bottom left of the Security & Privacy tab and log in as admin.
   * **For Linux**, you will need to set the file to be executable before running it. (e.g. chmod a+x Greenstone-3.09-linux)
@@ Line 211: / Line 211: @@
 Put these two together with a period mark to separate them and use this as the value for your tomcat.server property.)
-. Set up your Greenstone environment if you've not already done so by running ''gs3-setup.bat'' in your Greenstone 3 installation folder (''source ./gs3-setup.bash'' on Linux and Mac machines). And then start up your Greenstone 3 server with:
+. Set up your Greenstone environment if you've not already done so by running ''gs3-setup.bat'' in your Greenstone 3 installation folder (''source ./gs3-setup.sh'' on Linux and Mac machines). And then start up your Greenstone 3 server with:
 <code>
 ant start
@@ Line 333: / Line 333: @@
 ==== Troubleshooting ====
-=== You see an empty page when visiting the Greenstone 3 library home page ===
+=== Some perl scripts don't run properly or to completion ===
-If you're running Greenstone 3 on a non-English locale, then your library home page may look entirely empty. To resolve these and other locale and encoding related issues, refer to [[en:supporting_other_locales|Supporting running Greenstone in other locales on Windows 10]].
+//**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 ''perl -S pluginfol.pl -describeall'', then the problem may be locale/encoding related. To resolve this issue, refer to [[en:supporting_other_locales|Supporting running Greenstone in other locales on Windows 10]].
+=== You see an empty page when visiting the Greenstone 3 library home page on Windows ===
+//**If you're running Greenstone 3 on a non-English locale on Windows**//, then your library home page may look entirely empty. To resolve these and other locale and encoding related issues, refer to [[en:supporting_other_locales|Supporting running Greenstone in other locales on Windows 10]].
 === Content Encoding Error when visiting the local solr servlet page ===
@@ Line 425: / Line 428: @@
 If you get this error, then please install the CGI module for your system perl.
 ====Work Arounds====
-===Filenames in collections should not contain &, < and >===
+===Using filenames containing &, < and > in GS3.10 collections===
-In order to have better handling of different file and filename encodings, a [[http://trac.greenstone.org/changeset/29793|sacrifice]] [[http://trac.greenstone.org/timeline?from=19.03.2015&daysback=30&ticket=on&changeset=on&milestone=on&wiki=on&update=Update|was made]] of being unable to support &, < and > characters in filenames. Filenames with such characters will make metadata.xml invalid, as a result of which, GLI won't be able to reload the metadata therein.
+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 such characters, GLI will now successfully preserve them between GLI sessions.
+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 is to use "and" in place of "&" in filenames. And either use different characters for < and >, such as [ and ] or ( and ), or leave them out from filenames.
+The fix is often in the form of adding hex encoded entities into the metadata.xml file and decoding them back for display in GLI's Enrich pane.
 ===Greenstone applets (Phind, Collage) crash Firefox===
 See [[https://bugzilla.redhat.com/show_bug.cgi?id=789959|bugzilla report]].