i18n logging

Registered by Brad Pokorny on 2013-12-20

During the Oslo meeting on 2013-10-11 (http://eavesdrop.openstack.org/meetings/oslo/2013/) we discussed the integration of Messages into OpenStack vs other approaches, and also came up with some ideas for improving the current implementation and on how to implement the translated logs feature.

After the corresponding blueprint is implemented in oslo (https://blueprints.launchpad.net/oslo/+spec/i18n-messages) we will have the ability to translate REST API responses, and to create additional logs in languages other than the default system locale.

This blueprint is for making necessary adjustments in existing messages so they are translatable (e.g. Messages should not be created with +, but with % instead).

Blueprint information

Status:
Complete
Approver:
Brant Knudson
Priority:
Medium
Drafter:
Brad Pokorny
Direction:
Approved
Assignee:
Luis A. Garcia
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Brant Knudson on 2014-02-04
Completed by
Brant Knudson on 2014-02-04

Related branches

Sprints

Whiteboard

Most of this was done with https://blueprints.launchpad.net/keystone/+spec/user-locale-api :
 - "re-enabling the lazy translation, and making necessary adjustments in existing messages so they are translatable (e.g. Messages should not be created with +, but with % instead)"

The changes that we still have to make are for "create additional logs in languages other than the default system locale" -- and this should be done via a sync from oslo-incubator.

For Keystone, we'll probably also want some updated documentation. For example, we should provide a sample logging.conf file that shows how to configure the secondary log.

Adjusted title, description and id to reflect the reduced scope of this bp -dolph

This was done in https://review.openstack.org/#/c/66681/

(?)

Work Items

Work items:
sync TranslationHandler in gettextutils from oslo-incubator: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.