Jump to content

Template talk:Translation2

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 11 years ago by Amqui in topic Need help line

To migrate to this system

  1. Move Template:Translation2Template:Translation
    Move Translations/request2/openTranslations/request/open
    Move Translations/request2/closedTranslations/request/closed
  2. Move the source to its proper language page (most likely /en)
  3. Update the old status page to this system by creating a Template:Translation/[PAGENAME] and filling in the fields.

To-dos adjacent



not Todos, since some may not be specific enough to code, and since I realized I was not capable to DO them myself. Todos may be available very soon, in a more elaborate fashion.

Though I initiate this list, everyone is invited to give their voices. Thanks. --Aphaia 18:02, 10 January 2008 (UTC)Reply

Add 'ready' status

The following discussion is closed.

This template seems to me to assume the final destination of translated documents are meta, but not always so. Translations may be moved to another wiki or mailed, if necessary (e.g. WMF wiki). We need thus a status who represented 1) update finished and 2) not yet published in a full sense.

Currently I have no idea how can we add this status ... Aph. --Aphaia 18:02, 10 January 2008 (UTC)Reply

A status called "done" or "ready" would be easy to add, but I'd prefer to keep the number of options to a strict minimum so it's as simple as possible to use for regular editors. Maybe we could rename "published" to "ready", and transcom can keep track of published translations. This would also be more reliable, since otherwise some translations won't be published because someone accidentally marked it as already published. I'll talk to you on IRC about it next time I see you. —{admin} Pathoschild 03:19:06, 11 January 2008 (UTC)
I am very reluctant to keep tracks by my hand or such separated documentation. On recent request (Fundraising FAQ), it shows us such hand-tracking system bring us more failure or neglecting of existing (and done) works. For fundraising translation Sabine kept tracks somewhere we don't know or just failed to find and it made the coordination task difficult when she disappeared (and not back). Tracks should be visible, shared and integrated part of system I think. --Aphaia 11:16, 11 January 2008 (UTC)Reply
Or - thus said, since uploading isn't necessarily tasks of Transcom! - let me see: we can individually request for release/publishing etc? With another template or category, which allows us to generate a list on which WMF editors know which language they can help move. But still it is a bit strange for meta pages to be called "ready" ... "done" perhaps? --Aphaia 16:29, 11 January 2008 (UTC)Reply
When we tested the new system out, we found that a new "in-between" status would in fact be helpful, so Done. Cbrown1023 talk 02:38, 13 January 2008 (UTC)Reply

Subpage support

The following discussion is closed.

Currently, unless I misunderstand, it doesn't work on a subpage. The translation menu leads you to wrong page (e.g. You create a page Fundraising 2007/Thank you, make a translation template and put the latter on the former. The "uncreated" link on the menu may be a link to "Thank you/xx", not Fundraising 2007/Thank you/xx". I would love to see this problem fixed but no idea how-to. Aph. --Aphaia 18:02, 10 January 2008 (UTC)Reply

The edit link wasn't working because the "page" field should be "Fundraising 2007/Thank you", not "Thank you"; it is the full title of the page being translated (the same title you would use to link to it). I corrected and updated the template, so it works now. —{admin} Pathoschild 03:19:06, 11 January 2008 (UTC)
Ah thanks, now I see. So it was not a tweak. Aph.

More per-translation info

The following discussion is closed.

Or its later additions, that is:

  • Start date of request: (helpful to sort out)
  • Deadline of request: very important
  • Link to the diff and source the translator took and the current version of source file
  • Link to the final destination (preferable option, need when the document will be published on another website)

Thanks for your attention. --Aphaia

These features don't exist in the former translation templates. For example, Jimbo's 2007 fundraising video page has the notes written manually.
After discussing with you on IRC, these are the features I will implement in a few days:
  • An optional link to the final destination of the translation;
  • When the source page was last updated;
  • A diff between the current source page and the version they translated, if different.
{admin} Pathoschild 22:57:28, 11 January 2008 (UTC)
Hello how are you doing? Here sunny. Btw, a bit late, but I found a better example, see this (permlink to a version of Translation requests/WMF/Current staff/status)] for what I would have liked to mean. --Aphaia 05:39, 15 January 2008 (UTC)Reply
Done, and I updated the documentation. —{admin} Pathoschild 18:31:09, 28 January 2008 (UTC)

Thanks! Well I found another problem in this change, which I had failed to perceive before. Or I may misunderstand and make a silly question.

A param newly add to {{translation2}}

|source revid  = {{{source revid|}}} 

can be vary in each templates used on a particular ongoing translation? It may vary (one group may start before a significant change, and another may start just after the change...). So what we should get will be {{translation/blablabla|source revid=}}. That is one result of the recent changes? Cheers, --Aphaia 04:57, 29 January 2008 (UTC)Reply

Hai. If you add the code shown in the documentation, then you can specify the source revision ID on each individual translation. For example, see the code and the bottom of the translation box on Privacy policy/fr. —{admin} Pathoschild 13:19:53, 29 January 2008 (UTC)
Arigato. If we have this information on "documentation" as a reminder for each translators, it would be great. --Aphaia 13:36, 29 January 2008 (UTC)Reply
Already done. :) —{admin} Pathoschild 14:50:39, 29 January 2008 (UTC)

Sort translations by category

The following discussion is closed.

Translations were used to sort by status with category, and it enables us to have automated lists (see Translations/Finalizing requests). This feature is not so much frequently used but useful for regular overhaul (twice or thrice a year), at least for me. Is there any alternative or we need a further merger this system to the old one? --Aphaia 03:51, 27 January 2008 (UTC)Reply

This should probably be able to add if needed. Which categories did you want added? Cbrown1023 talk 15:50, 27 January 2008 (UTC)Reply
All statuses except missing (since the page doesn't exist, it may be pointless to list them up) and published (now they leave from our hand).
One another newly found concern is (again) guidance on the top - about renaming necessity. Pages which will be uploaded to the foundation website need to be properly renamed, that is, pages should be localized by move, and the old system (the "ugly remark" Pathos called) gives twice this kind of warning if I recall correctly. --Aphaia 03:46, 28 January 2008 (UTC)Reply
For managing content and ongoing translation by language and by their progress I feel it a great loss even if we thank the flexibility of the current template and cool appearance. Now translation cannot be classified by status (progress) or "translation in so-and-so language" so I have no way to get a list of pages on which I need to talk with those translators. Without this feature, I think we have to go back to the previous system. It makes me to give a look to each page and make a list by hand which was generated with DynamicPageList before (e.g. Translations/links/zh). --Aphaia 14:50, 1 February 2008 (UTC)Reply
Done. This means the new system uses a different set of categories than the old system (see Category:Translations by status), so if you want to list older pages you'll need to have side-by-side DynamicPageLists until we switch them to the new system. —{admin} Pathoschild 22:38:10, 01 February 2008 (UTC)
The following discussion is closed.

Why Privacy policy doesn't show on the list at TR, while it has new translation template? --Aphaia 22:41, 27 January 2008 (UTC)Reply

That will bewas fixed when the categories you asked for are added. —{admin} Pathoschild 18:35:13, 28 January 2008 (UTC)

var: destination


(following #More per-translation info)

I am afraid the var name "destination" is a bit confusable. It sounds me the final destination of each ongoing translations, but actually the page where the source file was taken. Pathoschild and I discussed on that and thought out a new name for this variable, say "published at". Just a note. --Aphaia 17:59, 1 February 2008 (UTC)Reply

Preload file

The following discussion is closed.

I didn't realized you would like to sweep away the preload settring, when you asked me to nod to delete Template:Translation2/request :( It brings me an inconvenience, I don't want to scratch each request or to let the other do. So sorry for late correction, I have to say that I mind you deleting it and would like you to keep (back) the preloading file feature greatly. --Aphaia 10:56, 8 February 2008 (UTC)Reply

That's fine; I didn't realize you were using it for preloading. —{admin} Pathoschild 13:39:45, 08 February 2008 (UTC)

'Needs proofreading' status


I saw this status in some docs (doc of this template and Translation FAQ) but it seems it doesn't work. Seeing the code of Template:Translation2/link I think this status had never been implemented. Is it possible to do it now ? it would be very useful (although it could de facto change the current habits. ~ Seb35 11:52, 2 January 2009 (UTC)Reply

Done :-) Cbrown1023 talk 19:16, 3 January 2009 (UTC)Reply

Disable status categories


There should be a parameter to declare that the translation request is closed hence the translations are not going to be published, proofread or completed and won't be categorized in the relevant status categories. Currently we have status categories flooded with old translations. This could be avoided if translation requests were handled perfectly, but perfection is not always possible. Nemo 11:22, 28 October 2011 (UTC)Reply

Need help line


Good day, I think the need help line right at the top of every page using that template is way too prominent. It is in bold and get over the introduction of every page. Maybe a simple note "Need help" in the bottom of the box to the right would be enough. I mean translating the page is important but it shouldn't get over the real intent of the page. Please see Global sysops for an example of what I am talking about. Thanks, Amqui (talk) 23:54, 24 November 2012 (UTC)Reply

Not done: it's not more prominent than the translations box, and it's needed to understand it. Removing the help/docs/communication line would increase rather than reduce clutter, by making the side-box such. What you can do to reduce ugliness is to migrate translations to Translate extension (I can show you how, ask on my talk if needed). Thanks, Nemo 01:52, 25 November 2012 (UTC)Reply
I already suggested them to migrate to the extension. The translation help line is too prominent on the page itself, not compare to the translations box. The way it looks now, it`s like if this was the subtitle of the whole page itself. Amqui (talk) 01:57, 25 November 2012 (UTC)Reply