Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

form:options tag does not support i18n [SPR-2659] #7348

Closed
spring-projects-issues opened this issue Sep 29, 2006 · 3 comments
Closed

form:options tag does not support i18n [SPR-2659] #7348

spring-projects-issues opened this issue Sep 29, 2006 · 3 comments
Labels
has: votes-jira Issues migrated from JIRA with more than 10 votes at the time of import in: web Issues in web modules (web, webmvc, webflux, websocket) status: bulk-closed An outdated, unresolved issue that's closed in bulk as part of a cleaning process

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Sep 29, 2006

Vaibhav S. Puranik opened SPR-2659 and commented

Currently form:options tag does not support internationalization. There is no way to resolve lables using key. We can support internationalization by many ways. I am describing some ways people have mentioned on forums: (http://forum.springframework.org/showthread.php?t=28342)

<form:select path="selected" items="${command.available}" resolveLabels="true"/>

<form:select path="orderBy">
<form:options items="validOrderBy" var="value">
<spring:message code="orderBy.${value}"/>
</form:options>
</form:select>


Affects: 2.0 RC3

Issue Links:

28 votes, 20 watchers

@spring-projects-issues
Copy link
Collaborator Author

Rick Evans commented

I18N support for the entire form tag library is going to be addressed in 2.1 RC1.

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Feb 20, 2012

Didier Loiseau commented

Also don't forget the same for <form:radioButtons>, but I guess this kind of code would be shared…

Maybe a default i18n key could be generated for enums, extending #8072.

@spring-projects-issues spring-projects-issues added status: waiting-for-triage An issue we've not yet triaged or decided on type: enhancement A general enhancement has: votes-jira Issues migrated from JIRA with more than 10 votes at the time of import in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues removed the type: enhancement A general enhancement label Jan 11, 2019
@rstoyanchev rstoyanchev added status: bulk-closed An outdated, unresolved issue that's closed in bulk as part of a cleaning process and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jan 11, 2019
@spring-projects-issues
Copy link
Collaborator Author

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has: votes-jira Issues migrated from JIRA with more than 10 votes at the time of import in: web Issues in web modules (web, webmvc, webflux, websocket) status: bulk-closed An outdated, unresolved issue that's closed in bulk as part of a cleaning process
Projects
None yet
Development

No branches or pull requests

2 participants