Use gettext for Localization

Registered by Rob

Greeble's current localization method loads hundreds of strings into a global array at runtime. This is costly and unnecessary. The benefit of this method is that the strings are easy to change: it allows run-time changes to localization strings, it allows easy creation of a web interface for updating localization strings, and it does not require the developer to be familiar with yet another purpose-built syntax.
It may be that the performance hits outweigh these benefits enough for Greeble to switch to gettext.

Blueprint information

Status:
Complete
Approver:
Rob
Priority:
Undefined
Drafter:
Rob
Direction:
Needs approval
Assignee:
Rob
Definition:
Obsolete
Series goal:
Accepted for 3.5
Implementation:
Unknown
Milestone target:
milestone icon 3.5b
Completed by
Rob

Related branches

Sprints

Whiteboard

Current localization has negligible performance impact. It stays until there is further reason for changing it.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.