id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
15376	translation in templates does not allow for a context variable	wildfire@…	nobody	"As per http://docs.djangoproject.com/en/dev//topics/i18n/internationalization/#contextual-markers, one of the newer features of the i18n framework allows for a context to be associated with each translatable string.

This works great, if all your strings are in your views.

However it is not so useful if your strings are in your templates and you also want to present the same context to translators (ideally, a single .po file with all translatable strings and contexts).

What would be nice is an extension to the 'trans' tag so that if two values were given to it, i.e.

{% trans ""Month name"" ""May"" %}

The contextual portion (the first string) in this case is output to the .po file

This may require some extra careful jiggery-pokery if this option is taken since {% trans ""string"" noop %} is also possible."		closed	Internationalization	1.3-beta		duplicate			Unreviewed	0	0	0	0	0	0