Index: openacs-4/packages/acs-core-docs/www/update-translations.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/update-translations.html,v diff -u -r1.19.2.1 -r1.19.2.2 --- openacs-4/packages/acs-core-docs/www/update-translations.html 2 Mar 2019 19:30:06 -0000 1.19.2.1 +++ openacs-4/packages/acs-core-docs/www/update-translations.html 3 Sep 2021 09:15:36 -0000 1.19.2.2 @@ -2,14 +2,14 @@
Identify any new locales that have been created. For each new locale, check the parameters, especially that the locale is in the format [two-letter code for - language, lower-case]_[TWO-LETTER CODE FOR COUNTRY, + language, lowercase]_[TWO-LETTER CODE FOR COUNTRY, UPPER-CASE], and create a sql command. A example sql command for creating a locale is:
insert into ad_locales (locale, label, language, country, nls_language, nls_territory, nls_charset, mime_charset, default_p, enabled_p) values ('fa_IR', 'Farsi (IR)', 'fa', 'IR', 'FARSI', 'IRAN', 'AL24UTFFSS', 'windows-1256', 't', 'f');
Put this command into the following four files. For the - upgrade files, the correct file name will depend on the + upgrade files, the correct filename will depend on the exact version.
/packages/acs-lang/sql/postgresql/ad-locales.sql
/packages/acs-lang/sql/postgresql/upgrade/upgrade-current-version.sql
/packages/acs-lang/sql/oracle/ad-locales.sql
/packages/acs-lang/sql/oracle/upgrade/upgrade-current-version.sql
Make a backup of the production database. Restore it as a new database. For example, if upgrading from OpenACS 5.1.1, and the site name/database name is translate-511, create translate-512b1.
Check out the latest code on the release branch (e.g., oacs-5-1) as a new site, using the new site name (e.g., /var/lib/aolserver/translate-512b1. Copy over any local settings - usually, /etc/config.tcl
and /etc/daemontools/run
and modify appropriately. Also, copy over several translation-server-only files:
...TBD