The reason is that translation files are often outdated. For outdated files this would mean that, when we are using class constants, the user would see a constant instead of an english text. Generally it is always better to display a user english text instead of a cryptic constant.
Thomas Weidner Zend Framework Certified Engineer & I18N Team Leader http://www.thomasweidner.com -----Ursprüngliche Nachricht----- Von: tridem-zend [mailto:[email protected]] Gesendet: Montag, 21. März 2011 11:14 An: [email protected] Betreff: [fw-general] Re: Zend_Validate_* now translatable! Regarding http://thomasweidner.com/flatpress/2010/01/17/translating-validation-message s/ http://thomasweidner.com/flatpress/2010/01/17/translating-validation-message s/ , I took a look at the translation files located in /resources/languages/**, f.e.: return array( // Zend_Validate_Alnum "'%value%' is an empty string" => "'%value%' ist ein leerer String" ); Is there a reason the language file can or does not use the class constants? return array( // Zend_Validate_Alnum "'alnumStringEmpty" => "'%value%' ist ein leerer String" ); return array( // Zend_Validate_Alnum Zend_Validate_Alnum::STRING_EMPTY => "'%value%' ist ein leerer String" ); -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Zend-Validate-now-trans latable-tp648192p3393102.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected] -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
