I don't see the problem here, just put a message key into the label renderer variable.
People that have to build an i18n app will be used to it anyways, so there isnt really a difference to doing this in the form builder or in the view. Automagic key generation is bad anyways since you can only do it based on the property path or id of the element, which leads to problems with double message keys for the same message when a form is used at different property path locations. On Mon, 28 Mar 2011 16:28:24 +0200, Bernhard Schussek <[email protected]> wrote: > I agree that we need a simple translation mechanism for those > components. Promoting message keys but not using them in the core is > weird. > > Users need to be able to change the default translations of validation > error messages without relying on the translations we provide in the > core. If we release as is, we can never ever change the default > translations again. > > Bernhard -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
