Active
Project:
Localization server
Version:
6.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Jan 2011 at 08:00 UTC
Updated:
31 Jan 2013 at 12:41 UTC
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
rfaysubscribe
Comment #2
zirvap commentedSee also #1035716: [policy, no patch] Decide and document guidelines for using 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 hojtsyWell, 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
damienmckennaThere 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.
Comment #5
gábor hojtsyDamien: the purpose of opening that issue was to figure out what to write on that page. That is not figured out yet...
Comment #6
SebCorbin commentedThis would be cool to offer a page and an API to list contexts. See also #1791612: [META] Find solution for growing number of strings extremely fast