Improving uPortal i18n Support

Owned by Jen Bourey
Last updated: Oct 28, 2010 by CarlosAVersion comment
1 min read

Planned 3.3 Improvements

  • Move all message strings (for JSPs, XSLTs, Java, JavaScript, etc.) into a single file
  • Use semantically meaningful keys
  • Eliminate repeated messages
  • Provide automated message file translations to serve as a starting point

Additional Feature Requests

  • i18n support for portlet titles and descriptions
  • Language-specific DLM fragments
  • Use browser locale to set language for guest users and authenticated users with no recorded locale preference
  • i18n support for tab names
  • Ensure portal locale is passed to portlets
  • Add i18n support to default bundled portlets

Language Volunteers

Language

Volunteer

Spanish

Carlos Alonso / Universidad Publica de Navarra

Macedonian

Vangel Ajanovski / Institute of Informatics, Saints Cyril and Methodius University in Skopje

French

Vincent Bonamy / University of Rouen / EsupPortail

Latvian

Arvīds Grabovskis

Internationalization Issues for 3.3

key summary priority status updated

Unable to locate Jira server for this macro. It may be due to Application Link configuration.