IMPORTANT: This is a message documentation task - not a language task, do not translate anything to any language, instead describe what the key is for / about.
This GCI task could be split to multiple tasks. Each task should result in at least 5 keys being documented.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Petrb | T179983 (tracking) Manage "google code in" for huggle: import all tasks and mentor them | |||
| Resolved | Petrb | T150089 (recurring) Document all missing keys in translate docs |
@Petrb: This task welcomes clearer steps and expectations. I click your link and I have no idea what I am supposed to "document" and how...
Best documentation is at:
https://mediawiki.org/wiki/Localisation#Message_documentation
We use translatewiki.net as a translation platform. When a translator want to localize a text, he doesn't know what param is behind $1 or a similar key. And sometimes even if no param is used a string can be strange. So the purpose of this task is to look in the code to see where the string is used (you can use the Github search function by entering the string name, I tel string the param of _l("my-loc-name"),that correspond to Hello ! in English). When you understand what correspond to this key, you have to add a small explanation in huggle/Localization/qqq.xml. This special file contain all the explanations of each string.
Don't hesitate to ask if we can help you somewhere. When it's good for you, please create a PR on the Github repo.
This task doesn't require pull requests, it's all done within TWN. qqq.xml file in repo shouldn't be changed by hand, it would be overwritten by a bot from TWN anyway.