I don't consider this as a bug, input choices are defined by a key/value pairs which should be managed by a datasource, I mean outside the form. The changeset is usefull if the key/values are defined inside the form, which is, from my experiences, rarely used [1].
I really think a widget's option should be defined to enable or disabled this feature. [1] http://rabaix.net/en/articles/2009/07/27/wording-is-not-a-developer-job-part-2(I don't like the __() usage in the model) On Mon, Nov 16, 2009 at 3:59 PM, Bernhard Schussek <[email protected]>wrote: > > Hi Thomas, > > Choices of a select widget are basically "labels" of the options. > Since all other labels in the form framework are translated > automatically, untranslated options (and other texts in widgets) are > not consistent and can be considered bugs IMO. > > Do you agree with this? > > Of course, there are always people who work around bugs, but they > still remain bugs and we need to fix them. > > Bernhard > > > > -- Thomas Rabaix http://rabaix.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
