How to Update the translations

Prev	Chapter�16.�Releasing OpenACS	Next

- Update the translation server. (Approach 1: upgrade to the last release; approach 2: upgrade to head or to an alpha or beta release.) Use CVS up. -
This approach puts the translation server at risk. An alternate approach would be to create a whole new checkout on the appropriate branch (such as oacs-5-0), point that at the live production database, import keys (which is safe because keys on the translation server take precedence), then export keys back, and then commit. This gets the keys committed to the right branch without changing the code running on the production site. Updating the production site can then be a seperate exercise.
Go to ACS Lang admin page and click "Import All Messages"
Resolve conflicts, if any, on the provided page. -
Back on the admin page, click the export link. If there are conflicts, the messages will be exported anyway and any errors will be shown in the web interface.
From the packages dir, run the acs-lang/bin/check-catalog.sh script. (This checks for keys no longer in use and some other things. Until it is rolled into the UI, do it manually and check the results and take whatever steps you can intuit you should do.) -
CVS commit the catalog files. Done

Prev	Chapter�16.�Releasing OpenACS	Next

How to Update the translations

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, + 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 + 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
+          
```
+
Shut down the production site and put up a notice (no procedure on how to do this yet.)
Start the new site, and upgrade it.
Go to ACS Lang admin page and click "Import All Messages"
Resolve conflicts, if any, on the provided page. +
Back on the admin page, click the export link. If there are conflicts, the messages will be exported anyway and any errors will be shown in the web interface.
Commit the message catalogs to cvs.
From the packages dir, run the acs-lang/bin/check-catalog.sh script. (This checks for keys no longer in use and some other things. Until it is rolled into the UI, do it manually and check the results and take whatever steps you can intuit you should do.) +
CVS commit the catalog files. Done
If everything went well, reconfigure the new site to take over the role of the old site (/etc/config.tcl and /etc/daemontools/run). Otherwise, bring the old site back up while investigating problems, and then repeat. +

- How to Update the OpenACS.org repository +

+ How to Update the OpenACS.org repository @@ -243,36 +243,36 @@ - Edit packages/acs-admin/www/apm/build-repository.tcl and adjust the Configuration Settings. + Edit packages/acs-admin/www/apm/build-repository.tcl and adjust the Configuration Settings. Request /acs-admin/apm/build-repository on your new server. - - - - The page will find all branches in the cvs repository labeled oacs-x-y, and build a repository channel for each of - those branches where x>=5 (so not for 4.6 and earlier). It will also build a channel for HEAD, - which will be named after what you set in 'head_channel' above. - - - - - For each channel, it'll do an anonymous checkout of packges and contrib/packages, then build .apm files for each package in the checkout. - + + + + The page will find all branches in the cvs repository labeled oacs-x-y, and build a repository channel for each of + those branches where x>=5 (so not for 4.6 and earlier). It will also build a channel for HEAD, + which will be named after what you set in 'head_channel' above. + + + + + For each channel, it'll do an anonymous checkout of packges and contrib/packages, then build .apm files for each package in the checkout. + + + + + The files will be stored on the server's hard drive in the directory specified by the 'repository_dir' variable in the page script, by default "[acs_root_dir]/www/repository/". + + + - The files will be stored on the server's hard drive in the directory specified by the 'repository_dir' variable in the page script, by default "[acs_root_dir]/www/repository/". - - - - - - If you're on openacs.org, everything should now be fine. Otherwise, you need to move the entire directory tree to openacs.org:/web/openacs/www/repository, replacing what was already there. This is automated on OpenACS.org by having a dedicated site just for building the repository, invoked with this shell script. Since the page circumvents security checks for ease of use, the entire site is limited to local requests. The script is called daily with a cron job. @@ -282,17 +282,17 @@ STATUS=`wget --output-document - http://127.0.0.1:8002/build-repository.tcl | grep DONE | wc -l` if [ $STATUS -eq "1" ] - then +then rm -rf /web/openacs.org/www/repository.old mv /web/openacs.org/www/repository /web/openacs.org/www/repository.old cp -r /web/repository/www/repository /web/openacs.org/www/repository fi -

- How to package and release an OpenACS Package +

+ How to package and release an OpenACS Package In this example, we are packaging and releasing myfirstpackage as version 1.0.0, which is compatible with OpenACS 5.0.x. @@ -310,36 +310,83 @@ Done. The package will be added to the repository automatically. If the correct version does not show up within 24 hours, ask for help on the OpenACS.org development forum. -

- - -

- How to Update the translations - +

+ + +

+ How to Update the translations + + + 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, + 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 + exact version. + - - Update the translation server. (Approach 1: upgrade to the last release; approach 2: upgrade to head or to an alpha or beta release.) Use CVS up. - - This approach puts the translation server at risk. An alternate approach would be to create a whole new checkout on the appropriate branch (such as oacs-5-0), point that at the live production database, import keys (which is safe because keys on the translation server take precedence), then export keys back, and then commit. This gets the keys committed to the right branch without changing the code running on the production site. Updating the production site can then be a seperate exercise. + /packages/acs-lang/sql/postgresql/ad-locales.sql - Go to ACS Lang admin page and click "Import All Messages" + /packages/acs-lang/sql/postgresql/upgrade/upgrade-current-version.sql - Resolve conflicts, if any, on the provided page. - + /packages/acs-lang/sql/oracle/ad-locales.sql - Back on the admin page, click the export link. If there are conflicts, the messages will be exported anyway and any errors will be shown in the web interface. + /packages/acs-lang/sql/oracle/upgrade/upgrade-current-version.sql - - From the packages dir, run the acs-lang/bin/check-catalog.sh script. (This checks for keys no longer in use and some other things. Until it is rolled into the UI, do it manually and check the results and take whatever steps you can intuit you should do.) - - - - CVS commit the catalog files. Done - - -

+ + + + + 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 + + + + + Shut down the production site and put up a notice (no procedure on how to do this yet.) + + + Start the new site, and upgrade it. + + + Go to ACS Lang admin page and click "Import All Messages" + + + Resolve conflicts, if any, on the provided page. + + + + Back on the admin page, click the export link. If there are conflicts, the messages will be exported anyway and any errors will be shown in the web interface. + + + Commit the message catalogs to cvs. + + + From the packages dir, run the acs-lang/bin/check-catalog.sh script. (This checks for keys no longer in use and some other things. Until it is rolled into the UI, do it manually and check the results and take whatever steps you can intuit you should do.) + + + + CVS commit the catalog files. Done + + + If everything went well, reconfigure the new site to take over the role of the old site (/etc/config.tcl and /etc/daemontools/run). Otherwise, bring the old site back up while investigating problems, and then repeat. + + + +

Prev	Home	Next
How to package and release an OpenACS Package	Up	Index