Make list of contexts used more evident for developers [#1034882]

Randy Fay points out that the list of contexts used is hard to get to (and requires translation team membership), while contributed module maintainers could use that data to choose appropriate contexts. We should have functionality to expose the contexts used so far and the strings under those contexts to give an idea to developers about the right contexts to pick.

Comments

Comment #1

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 21 January 2011 at 14:19

Comment #2

zirvap CreditAttribution: zirvap commented 21 January 2011 at 21:33

Issue tags:

+string context

By the way: l.d.o. includes strings from all releases of modules. This list should show contexts only from latest major release of each module. If someone introduces a mis-spelled or redundant context in some beta-release and later fixes it, we don't want the wrong context listed here for all future, to confuse others and increase the risk of the mistake propagating to new modules.

Comment #3

Gábor Hojtsy

he/him

Hungarian

Hungary

CreditAttribution: Gábor Hojtsy commented 23 March 2011 at 14:44

Title:

Expose contexts and where are they used for everybody

» Make list of contexts used more evident for developers

Well, in fact, anybody can browse any translation team without becoming a member, so they can figure out all available contexts and their use, but the UI and navigation for that is far from optimal. Anyhow, retitling for that.

Comment #4

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna commented 17 January 2013 at 12:34

There should be a standard page in the documentation for tracking the contexts and where they are used, developers should't have to dig (and dig, and dig) to find this.