Differences

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

--- en:supporting_other_locales [2020/04/29 06:59] – anupama
+++ en:supporting_other_locales [2023/03/13 01:46] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Supporting running Greenstone in other locales on Windows 10 ======
@@ Line 67: / Line 70: @@
   * Next, use your text editor to open your GS3's to open the file ''build.xml'' for editing.
   * Locate the line that contains:\\ <code><exec executable="${catalina.home}/bin/startup.bat" osfamily="windows" dir="${catalina.home}/bin" spawn="true"></code>\\ and paste the following in a new line immediately after:\\ <code><env key="JAVA_TOOL_OPTIONS" value="-Dfile.encoding=UTF-8"/></code>
-  * Also locate the line containing:\\ <code><exec executable="${catalina.home}/bin/shutdown.bat" osfamily="windows" dir="${catalina.home}/bin" spawn="false"></code> and once more, paste the following in a new line immediately after it:\\ <code><env key="JAVA_TOOL_OPTIONS" value="-Dfile.encoding=UTF-8"/></code>
+  * Still in ''build.xml'', also locate the line containing:\\ <code><exec executable="${catalina.home}/bin/shutdown.bat" osfamily="windows" dir="${catalina.home}/bin" spawn="false"></code> and once more, paste the following in a new line immediately after it:\\ <code><env key="JAVA_TOOL_OPTIONS" value="-Dfile.encoding=UTF-8"/></code>
   * Save and close the file ''build.xml''.
   * Relaunch GLI or the Greenstone Server Interface and preview your collections. They should now hopefully work.
@@ Line 84: / Line 87: @@
   * Try running GLI or the Greenstone Server and previewing your collection now. If there are still issues, see whether the DOS prompt contains error messages mentioning that mention issues running ''pluginfo.pl''. If so, see step 2 below.
+===== ANOTHER RELATED SYMPTOM AND ITS FIX =====
+//We noticed the following symptom only once in the 3 test cases so far. It has not occurred in the remaining 2 test cases, so although we document its solution here, you may not need to carry out the
+instructions for this solution until you actual notice the problem (the symptom) described here.//
-. **SYMPTOM:** Unable to successfully and completely run certain perl scripts successfully such as ''perl -S pluginfo.pl -describeall'', despite setting up the Greenstone environment by running gs3-setup.\\ As a result, GLI may fail to launch properly.
+**SYMPTOM:** Unable to successfully and completely run certain perl scripts successfully such as ''perl -S pluginfo.pl -describeall'', despite setting up the Greenstone environment by running gs3-setup.\\ As a result, GLI may fail to launch properly.
 You can test if this is the case by opening a new DOS prompt, using it to navigate into your Greenstone 3 installation area and then running the following 2 commands in sequence there:\\<code>gs3-setup.bat
@@ Line 102: / Line 108: @@
      - Use the Windows file explorer to go to ''perllib/cpan/Encode'' (which in a GS3 installation is located within its ''gs2build'' subfolder). Then rename the existing ''Locale.pm'' file to ''Locale.pm.old'', then you'll finally be able to rename the ''Locale.pm.forLocaleIssue'' file to ''Locale.pm'' and rename ''Alias.pm.forLocaleIssue'' to ''Alias.pm''.
      - Use a text editor to open up ''perllib/plugins/DirectoryPlugin.pm'' (in a GS3 installation, this is located withing GS3's ''gs2build'' subfolder). Somewhere near the top of this file, find the line that says:<code>#use Encode::Alias;</code>\\ and check out the ''#'' sign at the start of that line so that you get<code>use Encode::Alias;</code>\\ Then save the file with this change.