Forum OpenACS Development: What to do about site-specific changes to acs-lang message keys?

Collapse
1: What to do about site-specific changes to acs-lang message keys?
Posted by Dave Bauer on 01/04/04 11:10 PM
How should site changes to the acs-lang messages keys be handled?

Here are some situations I can think of:

1) English only (or single language) site. Site admin wants to change the text on some pages. It's in the message catalogs. One way (the only way?) is to "translate" the message keys in the default language.

2) Multiple langauage site. I am not sure this raises an issues that are not in the first case.

What happens if the site wants to merge with CVS?

Is it OK to change the message keys for site-specific changes in wording?

Collapse
2: Re: What to do about site-specific changes to acs-lang message keys? (response to 1)
Posted by Rocael Hernández Rizzardini on 01/05/04 04:29 PM
I think you probably won't have any trouble if the site-wide-admins are carefull to not write back your changes in words of the message-keys back to the message catalogs and just keep it into the DB.

So, you change all the words / sentences that you might like, but you don't re-write the catalogs with the info in the DB. So no changes are seen in the catalog files but the words for the user will be changed. The only thing is that you should do this changes in the live site, since there is no way to pass the word message-keys changes done in the DB from a dev to prod, unless you dump your keys.
Will be easier to do it into the prod using the UI from acs-lang.

Collapse
3: Re: What to do about site-specific changes to acs-lang message keys? (response to 1)
Posted by Dave Bauer on 01/05/04 04:49 PM
Rocael,

I would think a better procedure would be like this:

Change message keys on staging server. Write out to the catalog files. Check these into my local CVS repository. Update the production site. Import new message keys from catalog files into production site.

Or possibly do it on development, then test the import of the keys on staging, if you have that type of setup.

Collapse
4: Re: What to do about site-specific changes to acs-lang message keys? (response to 1)
Posted by Rocael Hernández Rizzardini on 01/05/04 05:58 PM
Yes, that'll be the best method, I understood that you might want to avoid "conflicts" between openacs CVS & your local CVS for upgrading the catalog files, so I was suggesting another possibility =)