Modify

Ticket #81 (new enhancement)

Opened 3 years ago

Last modified 18 months ago

i18n messages lookup

Reported by: mpo Owned by: mpo
Priority: major Milestone: 0.5
Component: < I18N Version: trunk
Keywords: Cc:

Description

We need a solid way to retrieve and use translation sets to be used in the forms.
These sets will simply list key: translation entries.

Unclear now if merging should happen in the client, or at the server.
The former makes pure static development and testing easier.
The latter allows to reuse typical Java Resource bundels (or any other i18n provisioning we'll use on the backend) and just produce the correct set on a specific .../{area}/messages/{locale}.js URI

Attachments

Change History

comment:1 Changed 3 years ago by bruno

  • Component changed from -- unknown -- to modules/kauri-forms

comment:2 Changed 2 years ago by mpo

  • Milestone changed from 0.3 to 0.4

work started, needs completion though

comment:3 Changed 2 years ago by mpo

Some ample further attempt in r1393 and r1395

comment:4 Changed 2 years ago by mpo

The locale.js already contains a Message object that will look into the Locale.messages for a translated text for a given key.

They can be set through locale.setMessages

What is missing though is dynamically loading bundles.

For that the i18n module already provides a client API: (see http://www.kauriproject.org/docs-0_4/310-kauri/316-kauri.html) that will deliver bundles in json from URI's like /bundles/{bundle}/{locale}

The Locale object should be enhanced with a loadBundle(bundleName) to retrieve the bundle.json (note: loaded messages should extend, not replace the set of messages, ie don't use setMessage there)

comment:5 Changed 2 years ago by jgou

  • Priority changed from minor to major
  • Component changed from modules/kauri-forms to < I18N

comment:6 Changed 20 months ago by mpo

  • Milestone changed from 0.4 to 0.4.1

comment:7 Changed 18 months ago by jgou

  • Milestone changed from 0.4.1 to 0.5
View

Add a comment

Modify Ticket

Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.