#10 Form label should use I18n - Rails I18n

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, priority, updated	tickets sorted by #, priority or updated
Combine keywords for powerful searching.
Use advanced searching »

#10 new

Form label should use I18n

Reported by iain | August 24th, 2008 @ 12:50 PM

As described on: http://rails.lighthouseapp.com/p...

"Form labels should look in active_record.human_attribute_names namespace in the I18n system for the correct label text."

But using the default translation methods for columns I made earlier, so STI works and stuff...

And a step closer to the solution for translating scaffold. http://i18n.lighthouseapp.com/pr...

Comments and changes to this ticket

Jacek Becela November 24th, 2008 @ 01:26 PM
1. Already using plugin version of this patch.
Jacek Becela November 24th, 2008 @ 01:27 PM
Should be a +1 up there.
Yaroslav Markin November 24th, 2008 @ 02:18 PM
Sure, plugin works just great. We've got a ticket in Raisl lighthouse on merging.
Andreas Neuhaus December 2nd, 2008 @ 01:02 PM
+1

I also had this idea while creating views with forms in an i18n-enabled Rails app and my idea of a solution was almost the same.
Lars Hoeg January 7th, 2009 @ 10:02 AM
+1 Works for me! Was just about to create a similar patch as I needed this on current projects, only this patch seems to be a bit more generic.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.