Forum .LRN Q&A: what happened with the translated messages??!?!

hi:

I know that was a server upgrade, and so some of the messages got lost. I assume that this happened with pt_PT and pt_BR, which had almost all the messages translated and now there are about 100-200 less.. but with gl_ES I had also 1600+ translated messages and now only appear 600+!!

what happened? is there any way to retrieve the "lost" messages?

It seems in acs-datetime en_US there are some missing as well. There used to be about 20 in it, now there are only 3 left, and a freshly installed calender shows a bunch of messages like this:

MESSAGE KEY MISSING: 'acs-datetime.Today'

Did you check wether the messages were used by another non-core package before removing them?

Tilmann,
good catch about the acs-datetime keys. Actually the test servers also caught it for me, but you posting her made me fix it sooner. Sometimes when I fix one bug I introduce another, see this commit: http://xarg.net/tools/cvs/change-set-details?key=EE8D222D64FA3B78E0F53A77DAD282AFFBDC417C

Notice the acs-datetime.en_US file that is there and has nothing to do with what the commit was supposed to do. When the test servers are recreated tonight calendar should be back in business again.

The original problem with missing keys arose because the keys were not present in any scripts as package_key.message_key and therefore my consistency check script thought they were no longer used. It is very important that you *never* do dynamic message lookups like this:

set message_key [generate_message_key_dynamically]

set text [_ $message_key]

Instead you can do something like this:

set message_key_array {
  lookup1 package_key.message_key1
  lookup2 package_key.message_key2
}

set text [_ $message_key_array([generate_lookup_dynamically])]

Ok, that was maybe not so readable. The point I wanted to make is that package developers need to have their keys represented as package_key.message_key somewhere in their scripts or else the message keys risk being removed.

Now it is: http://cvs.openacs.org/cvs/openacs-4/packages/acs-datetime/catalog/acs-datetime.en_US.ISO-8859-1.xml?rev=1.15&content-type=text/x-cvsweb-markup