Bug 1042979

Summary:	[RFE][oslo]: separate translation decorators for different message types
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/oslo/+spec/separate-translation-decorators
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_superseded
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 16:58:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-13 16:51:03 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/separate-translation-decorators.

Description:

In the Icehouse summit, there is a discussion about messages i18n policies. One follow up action is to separate translation decorators for each message types. Then these translation messages will be wrapped in different pot files. Translation teams can decide the translation priorities for these different kinds of messages.

Refer to the meeting minutes in Etherpad: https://etherpad.openstack.org/p/icehouse-oslo-i18n-policies

Specification URL (additional information):

None