Differences

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

--- en:release:3.09_release_notes [2019/12/13 04:40] – anupama
+++ en:release:3.09_release_notes [2021/02/09 04:16] – [Using filenames containing &, < and > in GS3.10 collections] anupama
@@ 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 332: / Line 332: @@
 ==== 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 ''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 ===
@@ 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 >===
+===Filenames in collections should not contain < and >===
-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.
+[**Note:** [[https://stackoverflow.com/questions/1976007/what-characters-are-forbidden-in-windows-and-linux-directory-names|Windows disallows < and >]] characters in filenames anyway, so it's best to avoid such filenames even on other Operating Systems in cases where you may tranfer a Greenstone collection with documents' filenames containing < or > from one operating system to a GS3 running on Windows at any point.]
+In order to have better handling of different file and filename encodings, an [[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. In Dec 2019, which is months after 3.09's release, Greenstone was modified so that GLI can now accept & in filenames. However, filenames containing < and > characters continue to make metadata.xml invalid, as a result of which, GLI won't be able to reload the metadata therein.
+A workaround is to use different characters for < and >, such as [ and ] or ( and ), or leave them out from filenames.
-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.
 ===Greenstone applets (Phind, Collage) crash Firefox===
 See [[https://bugzilla.redhat.com/show_bug.cgi?id=789959|bugzilla report]].