User talk:MtDu

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Welcome to Wikimedia Commons, MtDu!

-- Wikimedia Commons Welcome (talk) 23:55, 10 December 2015 (UTC)[reply]

Notification about possible deletion[edit]

Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.

If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

And also:

Yours sincerely EugeneZelenko (talk) 15:23, 12 December 2016 (UTC)[reply]

When I said that I see a list of languages I meant the footer: «(help us translate this message:Čeština | Dansk | Deutsch | Deutsch (Sie-Form)‎ | English | Español | Français | Italiano | 日本語 | Bahasa Melayu | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/− )». This should be replaced by a link to Special:Translate. Other than that, this template is now good. --Nemo 07:12, 30 December 2016 (UTC)[reply]

Templates to be converted[edit]

Based on quarry:query/15130, Template:Geograph seems a good candidate as next template to be converted (yesterday I also updated the help page). Nemo 07:12, 30 December 2016 (UTC)[reply]

I made a better query which automatically excludes the templates already migrated to Translate: quarry:query/15279. Login and click "Fork" to be able to rerun and get an updated list (this query takes about 3 minutes). --Nemo 18:49, 7 January 2017 (UTC)[reply]

Comments on templates[edit]

Everything looks good now, great! I'll now ask translation admin rights for you at Commons:Bureaucrats' noticeboard. You may have noticed that users often like to have the list of languages directly on the /i18n page, so if it doesn't cost you anything you can as well add it (with noinclude). Also, when you become a translation admin and mark the pages yourself, you can mark the template title as untranslatable to avoid leaving the translation statistics unnecessarily yellow. ;) Nemo 22:14, 7 January 2017 (UTC) P.s.: For reference, the checkbox you'll see after clicking "mark for translation", as in phabricator:F5249655.[reply]
Yes, the templates look ok. I'd just put in tvar the longer markup strings like [1] but they're not too bad. Nemo 15:01, 8 January 2017 (UTC)[reply]
That's ok (except that tvar for URLs is still preferable), but moving /en is the least important part: what's interesting is to move the other subpages like Template:KOGL/ko and Template:KOGL/zh. Importing translations is the biggest part of the work; Piramidion has helped you so far, but you should do this part too from now on. Nemo 15:42, 11 January 2017 (UTC)[reply]

IMHO would be very useful (but might be tedious, although feasible):

Potentially more complex syntax:

--Nemo 03:14, 13 January 2017 (UTC)[reply]

The new templates are ok, except one string you forgot to make translatable and the Italian text in Template:PD-AB-exempt/i18n/fr which can be deleted.

Continue like this! :) --Nemo 12:53, 13 January 2017 (UTC)[reply]

Blacklisted languages[edit]

Hi! Here's the list of languages, translations to which are disabled globally (source, under "deprecated language codes"):

  • gan-hans
  • gan-hant
  • ike-cans
  • ike-latn
  • kk-cyrl
  • kk-latn
  • kk-arab
  • kk-kz
  • kk-tr
  • kk-cn
  • ku-latn
  • ku-arab
  • shi-tfng
  • shi-latn
  • sr-ec
  • sr-el
  • tg-latn
  • zh-hans
  • zh-hant
  • zh-cn
  • zh-hk
  • zh-mo
  • zh-my
  • zh-sg
  • zh-tw

If you prepare a template for translation and see that some translations already exist, and if you notice that there are translations to any of the languages from the list above, don't move them to /i18n/xx pattern. Leave them as they are and put a "speedy" tag to delete them. If you move them and mark the main i18n page for translation, you won't be able to put the "speedy" tag on those pages. Just to illustrate, I had to ask Nick to delete these two: Template:MIT/i18n/zh-hans and Template:MIT/i18n/zh-hant

BTW, there are some useful pages for TAs:

Thanks Piramadion! I have a few questions

  • In regards to speedy, I just add speedy in curly braces to those old lang pages?
  • In regards to PageTranslation, do I just remove the templates for translation after I am done importing the existing translations?
  • In regards to AggregateGroups, what do I need to do exactly? Pile them all under miscellaneous templates section?
  • In regards to PageMigration, I am currently just using the Move feature on the old pages and moving them to i18n. I do not have the time the next few days to learn Special:PageMigration (GCI ends soon, and I would like to do as much as I can), but I will try to pick that up later.
  • If there's anything else, please let me know.— Preceding unsigned comment added by MtDu (talk • contribs)
As for speedy – yes, but I'd recommend to put it into "noinclude" tags, just in case. And include the reason like "translations to this language are disabled"
As for PageTranslation – I didn't understand the question. Removing a page from translation is generally not recommended, but sometimes it might be useful, for example, if you forget to move some already translated page into the translation system under /i18n. After the main page is marked for translation, you won't be able to import any translations using "move" feature, unless you remove it from translation first.
As for AggregateGroups – there's a section named "Copyright and source templates" – it's the best place for the templates you're currently working on.
As for PageMigration – it would just make your current work a bit easier. You may try it, or not, as you wish ;)
As for the notification – I have added your talk page to my Special:Watchlist, so I'd see if you answered. But if you want to explicitly notify a user, you can use {{ping|Username}} – the user will receive a notification like $1 mentioned you on $4 in "$5".. And don't forget to sign your posts. Just put four tildes (~~~~) in the end, or use the signature button on the edit toolbar.--Piramidion (talk) 02:45, 12 January 2017 (UTC)[reply]
@Piramidion: Thanks for the PageMigration tip! It really helped! I'll see how I can improve my work in the other aspects soon. I just attempted https://commons.wikimedia.org/wiki/Template:MML/i18n and used the Special:PageMigration successfully. However, I noticed that it missed the first translation unit as an option. I had five, but it only provided four, so I had to go back anyway unfortunately. Could you check on this and see if it happens for you as well and see why? However, it does help. :) MtDu (talk) 03:44, 12 January 2017 (UTC)[reply]
Well done! You learn quickly About Special:PageMigration – I tested this and found that it always shows all the translation units except the first one (I added one more, then I enabled page title translation, then I disabled it again, and always had all the units except the first one). It works fine if the page title translation is enabled – on Special:PageMigration we need only the body of the page, not its title, but if it's disabled, that's already a problem. Thank you for noticing that. I'll file a task on Phabricator later – perhaps someone will fix that bug.--Piramidion (talk) 05:23, 12 January 2017 (UTC)[reply]
For these cases, i use next workaround:
  1. Placing {{Speedy}} into talkpage of deprecated translations, with next explanation for admins: "deprecation language; please delete this page through [[Special:PageTranslationDeletePage/<pagename>]]"
  2. Any admin may perform this action.
--Kaganer (talk) 17:48, 12 January 2017 (UTC)[reply]
Thanks for the tip. As for the deprecated languages, it seems that FuzzyBot deletes them on his own (see red links above), so in this case no action is actually needed.--Piramidion (talk) 18:29, 12 January 2017 (UTC)[reply]

The Working Man's Barnstar[edit]

The Working Man's Barnstar
Over 1000 edits, congratulations! Now nothing can stop you from migrating hundreds more templates to Translate. ;) Nemo 06:47, 13 January 2017 (UTC)[reply]

Fuzzying[edit]

You just edit the translation unit (the page in the "Translations" namespace) and add "!!FUZZY!!" to it (usually as very first thing). --Nemo 12:40, 13 January 2017 (UTC)[reply]

Noratelimit[edit]

Just a quick note to let you know that the noratelimit flag has now been added to the translation administrator user right, so you shouldn't now experience any issues moving pages around etc. Thanks to Odder and Dereckson for their coding and deployment skills in getting this task done so quickly. Nick (talk) 14:55, 19 January 2017 (UTC)[reply]

Language footer[edit]

Hi! Please remove the language footer as well, like this: Revision of 230801940. Thanks!--Piramidion (talk) 14:38, 24 January 2017 (UTC)[reply]

Chinese variant translations should not be disabled[edit]

Hello, I'm the creator or major editor and Chinese Simplified (zh-hans) + Traditional (zh-hant) translator for several license templates, including {{MIT}}. I've just found that when you converted autotranslate Templates to ext.translate ones, {{MIT}} for example, the Chinese variant translations were deleted or ruined somehow.

The two variants of Chinese Mandarin language, zh-hans (sometimes represented by zh-cn since China "cn" is the largest region using zh-hans) and zh-hant (sometimes represented by zh-tw for the similar reason) are always in need, there are many difference between the two and people who use one as their first writing system usually cannot write by hand (and some could have difficulty to read) the characters in another system, it's also possible to have more variants zh-cn zh-hk zh-mo zh-my zh-sg zh-tw. Chinese Wikipedia implements zh-hans, zh-hant and 5 other variants - only omits zh-my.

zh-hans, zh-hant and other variants do exist in language settings of Wikimedia Commons. But now {{MIT}} and other templates using ext.translate cannot use those variants. Wikimedia Commons users (or Chinese Wikipedia users) choosing to use one variant may be forced to view the page (it's also possible to view Commons page from local Wikipedia e.g. from the link zh.wikipedia.org/zh-tw/File:1107@692@Hang_Hau_North.jpg) in another language variant. That's not very nice. Back to the time where {{MIT}} used autotranslate, we don't have this problem.

Please restore what they were or find a way to solve the problem, thank you. --Tomchen1989 (talk) 10:15, 22 March 2017 (UTC)[reply]

Relevant discussion: #Blacklisted languages; I also posted it here to seek opinions from more editors and admins. --Tomchen1989 (talk) 00:23, 25 March 2017 (UTC)[reply]
Hi. Translation admins are neither responsible nor able to do anything about this issue. I cannot find any info regarding why these languages have been blacklisted. As for the already translated pages, they will be deleted automatically after they're moved to the translation system, so basically it's better to not move them but nominate them for speedy straightaway. They can be easily restored after the relevant language code stops being blacklisted.--Piramidion (talk) 23:03, 4 April 2017 (UTC)[reply]

A barnstar for you![edit]

The Original Barnstar
Thanks for making the helpful videos. Eric0892 (talk) 00:41, 28 January 2020 (UTC)[reply]