Bill Moseley wrote: > On Tue, Oct 23, 2007 at 02:12:08PM -0400, Christopher H. Laco wrote: >> Bill Moseley wrote: >> [snip] >>> Yep, although I prefer to use English as the key to the language files >>> instead of an ID. Easier to understand when looking at specific >>> validation code. I can also fall back to using the ID (the English >>> error message) if the lookup fails in the language file. >>> >> That is, until you change the English message,,,,then you have to change >> it in all of your lang files since it's the key. :-( > > Well, I believe there's tools that will help with that. Plus, I'd > rather mess up that and have > > Error: You entered the wrong password > > sent to the non-English speakers than: > > Error: ERR_WRONG_PASSWORD > > or > Error: ERROR_23 > > ;) > >
Yes, to each their own. I think that's a damned if you do, damned if you don't situation, if the answer changes depending on the project. Personally, I always use keys, and consider _AUTO and the exposure ERR_WRONG_PASSWORD an all out failure. I've always wanted to have a test module that scoured source for keys and ensured they were in all l18n files. -=Chris -- Let them eat cake and false positives. -----BEGIN NSATT SNOOP BLOCK----- building bomb tower terrorist grenade c4 explosive plot hijack plane police feds white house guns dirty device convoy president war chemical death drop off mule undercover launch rocket drug covert cell cerin mass infidel Allah package subway mass ------END NSATT SNOOP BLOCK------
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- 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
