On 10/23/07, Bill Moseley <[EMAIL PROTECTED]> wrote: >> We have quite the existing translation system here at work (all our >> business is overseas and we do 16 different languages), and using >> English as the key is pretty much a non-starter in our system. (It >> also makes it a bit harder to change the English text.) > > Do you have a "system" for picking error codes such that the don't get > repeated?
Yeah, the constants are in a module that inherits from Rose::HTML::Object::Messages, which will puke when you try to load it if you repeat a message id: Could not add message 'SOME_NEW_MESSAGE' - a message with the id 1701 already exists (SET_PARSE_ERROR) And it'll warn if you repeat a name: Constant subroutine Rose::HTML::Object::Messages::SET_PARSE_ERROR redefined at ... Not that it matters much for us since our translation system itself (big scary thing with a Windows front-end and its own database) ensures that message ids are not repeated, and we use the same message ids on the Perl side. > And when a new validation error id is added into the code does the programmer > also update one of the language templates -- and then notifies the language > team? The programmer adds the message id constant and enters the English text. Periodically (usually a few times daily when we're busy), a "sync messages" job is run that merges the work done by the translators and the new messages added by the developers. (Both parts talk to our version control system to do their work.) -John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
