Ticket #68 (closed enhancement: fixed)

Opened 4 years ago

Last modified 3 years ago

Suggestion: Language Translation.

Reported by: tgudmu Owned by: madair
Priority: P1 Milestone: 2.0
Component: Core Version: 1.0.6
Severity: Minor Keywords: language, fusion, translation
Cc: External ID:
state: Analysis Requested Browser: All
Operating System: All

Description

For labels in the ApplicationDefinition it could contain an ID of a label instead of the label itself. Then, when parsed a lookup can be made in a locale file to get the correct translation of a label. This will avoid hard-coded values in the ApplicationDefinition.

Change History

Changed 3 years ago by pagameba

  • priority changed from P2 to P1
  • state changed from New to Analysis Requested
  • milestone changed from 1.1 to 2.0

Good idea. The OpenLayers.i18n function can be used for this and we don't even have to change much - if you pass a string in that doesn't have a translation, it should return the string itself. This means a bit of overhead for ApplicationDefinition files that aren't using this but it would make it much easier for translating applications.

Changed 3 years ago by madair

  • status changed from new to closed
  • resolution set to fixed

(In [1759]) closes #68: allow I18n dictionary keys to be used in the AppDef? files; change StatusItem? to StatusText?;

Note: See TracTickets for help on using tickets.