Differences

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

--- en:supporting_other_locales [2019/12/13 03:51] – anupama
+++ en:supporting_other_locales [2019/12/13 04:06] – anupama
@@ Line 1: / Line 1: @@
-====== Supporting other locales on Windows ======
+====== Supporting other locales on Windows 10 ======
 Greenstone testing work tends to be done in an English locale, with English specific settings. However, Greenstone is meant to support language users around the world, whose PCs and laptops may be set to different locales and other language settings.
@@ Line 5: / Line 5: @@
 Months after Greenstone 3.09 was released, we discovered that on a machine running Windows 10 which was set to the Chinese locale and other related settings, different aspects of Greenstone 3 did not function out of the box.
-**In particular, the following issues were detected, with their causes and fixes described below:**
+**In particular, the following issues were detected, with their causes and fixes (which work on Windows 10) described below:**
 . **SYMPTOM:** Visiting http://localhost:8383/greenstone3/library after running the Greenstone 3 server shows an empty page. If you try to investigate this issue on Windows, GS3's tomcat server output in the black DOS window can contain some strange characters or legitimate characters from other languages randomly interspersed within a display language when interfaceConfig.xml is being parsed for loading in. The tomcat and greenstone logs, located in GS3/packages/tomcat/logs/catalina[...].out and GS3/web/logs/greenstone.log respectively, may contain similar output with multiple character sets wrongly interspersed.
@@ Line 42: / Line 42: @@
   - Save and close the file.
   - If not launching Greenstone applications from the Windows Start Menu, then when you next run any part of the Greenstone suite hereafter to test the fix, make sure to use a fresh DOS prompt so that the updated greenstone environment will be used when you run ''setup.bat'' in greenstone 2, or ''gs3-setup.bat'' in Greenstone 3 which internally runs its ''gs2build\setup.bat''.
+  - Windows requires further configuration changes followed by a restart. The most important is the 3rd one below:
+     * Rightclick on your Windows Desktop, choose Display Settings. In the search box, search for "Language Settings". Then the ''Language'' configuration page opens, under ''Windows Display Language'' select the language setting appropriate for you.
+     * Go to Control Panel > Clock and Region > Region.
+        * In the ''Formats'' tab, under ''Format'', select your language/country's language format setting.
+        * In the ''Administrative'' tab, under the ''Language for non-unicode programs'' section, press the ''Change system locale'' button. Your preferred locale may already be selected, if not select it here.
+        * **Most importantly**, still in the Adminstrative tab, **on Windows 10,** there is a tickbox option for ''Beta: Use Unicode UTF-8 for worldwide language support''. Ensure you tick this. (Details of what this setting does when you switch it on are [[https://stackoverflow.com/questions/56419639/what-does-beta-use-unicode-utf-8-for-worldwide-language-support-actually-do|here]].) While investigating the overall encoding issues described on this page in a Chinese locale, we found that this new setting available on Windows 10 more fully supports the encoding fixes listed above. Earlier versions of the Windows OS may not provide complete support because this new setting is absent.
+     * Don't forget to restart your machine.