@Aymatth2: Sorry for the delay in responding to you. You don't need any permission to translate pages on Commons. The only privilege of a translation administrator is to mark a page for translation. What page do you want to translate? I can mark it for you if you want. Alternatively, you can request it at COM:TN.
I was exploring translation of COM:CRT, COM:FOP and the individual COM:CRT/country pages.
The first two have translations already, but they are very outdated and are not marked so they link to the translate extension. The non-English versions should either be brought up to scratch and then maintained in sync, or turned into redirects to the English version.
The individual country pages do not have translations apart from COM:CRT/Japan (outdated) and COM:CRT/Mali, which I just did as a trial. I think there would be value in having at least some of the COM:CRT/country pages maintained in their local language and translated to English using the translate extension. French, Spanish and Russian would cover many of the non-English countries. It may be possible to track WIPO to make sure the country pages reflect the latest laws.
The subject needs discussion before launching anything. Outdated translations of pages like these are worse than useless, because they can mislead contributors. But first I wanted to be sure I fully understood how it would be done. Any thoughts on the above? Aymatth2 (talk) 15:34, 10 January 2019 (UTC)[reply]
It is really important to clean up the source page first.
Citations should link to the local language version of the external source if there is one, and quotes should take text from the the local language version. There usually will be local language sources.
There is some risk that the section markers in the English version will be accidentally deleted.
Canada is bilingual, but with most countries the local language may be the prime page and the English version the translation. I think.
I should have linked the English/French infobox templates via autotranslate or something: {{Infobox copyright rules}} and {{Infobox copyright rules/fr}}. Selection should be based on the page language, not the user's preferred language.
The parent COM:CRT page and the shortcuts should be fixed to link to the user's chosen language version where available.
Too many languages I think the general rule is that a template, transcluded into a page, should use the same language as the page if possible. If not, it should use the English version. A link, pointing to another page, should take the user to the version in their preferred language, if available. It may still display the native language name for the link.
Two templates, {{CRT shortcut}} and Commons:CRT disclaimer take a lang= parameter, but default to the page language. {{Cat see also}} uses {{LangSwitch|}}. I think it should also default to the page language, or else these pages should use a variant that does.
No urgency. This is something that deserves careful thought. I like the way Commons:Copyright rules by territory/Canada/fr and Commons:Copyright rules by territory/Iran/fa turned out. There are still some technical glitches, but nothing that cannot be fixed. If we were to proceed, I could translate more pages from the Francophonie, starting with Mali. I am not a native French speaker, but think I can do an adequate first version. The sequence should probably be flipped though: The French version would be the "master" and the English version the translation. Aymatth2 (talk) 18:14, 11 January 2019 (UTC)[reply]
Changed citations from the {{Sfn}} style to the more widely used <ref>{{citation ...}}</ref> style. The citation should be included in the translation unit so the link can be changed to point to a version of the source in the page language if available.
Converted {{See also}} and {{Cat see also}} to plain English. These templates both switch language based on the user's preferred language, where it is more appropriate to switch based on the page language. {{Cat see also}} is very poor, rendering separate translations of "see also" and "category" followed by the category name. The target language may well use a different sequence, like "See the catname category also".
Moved the see also links to the "See also" section.
Changed {{Ok}} and {{NotOK}} to new templates {{OkMark}} and {{NotMark}}. The new templates switch based on page language rather than the user's language.
I would much prefer to use the Translate extension so that outdated translations can be flagged. I do not see great value in the consolidated lists, but could not have got agreement to split out the country pages without them. Maybe the subject can be revisited a year or so from now, when the new structure has settled in and we have more stable page view statistics. Aymatth2 (talk) 20:19, 23 February 2019 (UTC)[reply]
Yes, that seems to do it! Transcluding the output from the translation. I don't want to react too fast, but could implement the same change for the other section transclusion templates, and could close the Phabricator ticket. That is great! Aymatth2 (talk) 20:10, 25 February 2019 (UTC)[reply]
@Aymatth2: I restored Commons:Copyright rules by territory/Canada to the Translate extension. I will reply to the other issues raised by you in this very thread soon. There are still some RTL (right to left) issues on Commons which I need to work on. In the meantime, that would be great if you ask bureaucrats to make you a translation administrator at COM:BN. It is hard for me to cover all +200 countries in the world. We need to divide the work between ourselves. I will cover Asia and another continent. I guess Americas is your own continent and you would probably prefer to work on it. Perhaps you would prefer to work on Africa too, because there are many French-speaking countries there. That leaves Europe to me, and since Europe is a large continent (i.e. has many countries and thus pages), Oceania would be on your shoulders too. Please let me know if that is not the case, or if you have other preferences or priorities. We will find the best practices while we carry on. I am not very familiar with the Translate extension myself. Thanks. 4nn1l2 (talk) 07:19, 26 February 2019 (UTC)[reply]
That sounds like a plan. I was working through all the country pages making standard changes to make translation cleaner, and had got as far as COM:CRT/Latvia when I got distracted by renaming Category:Côte d'Ivoire. I will finish off that job in the next day or so. I am not sure how much actual translation I will do, but can start marking up pages if I get the permission.
You are right, I'm not interested in glory, at least not for this. Also, "I" won't manage to de-admin Jcb over this. I didn't start the desysop-request-proposal. And is this a large event? The thing itself, that's debatable. But the event is quite large. Had everyone been on vacation, this could have been a small event. It's strange. I agree it would be better if the proposal had listed more reasons. It would be better to propose/start a desysop based on the full history. But then, I already tried that and it didn't work. I'm not allowed to document Jcb anymore and per your order, Jcb's talk page is no longer on my watchlist. So whatever Jcb has been doing recently.. I don't have a clue, and I'm not writing it down. Is anyone else writing it down? Who knows, but I'm not counting on it. Proposals for a de-adminship request for Jcb that don't get immediately shut down are not all that common because Jcb is usually only involved in "small" events.
It's all a big mess. But how do you envision a proper desysop-request-proposal could be started? Who do you think could do it? - Alexis Jazzping plz20:44, 27 January 2019 (UTC)[reply]
ببخشید اگر ایمیل به زبان فارسی طبق الگوی زیر باشد اشکالی دارد؟
من بدین وسیله اعلام میدارم که یکی را انتخاب کنید: [نام خودتان] یا [نام دارندهٔ حق تکثیر] خالق و/یا تنها صاحب حق تکثیر انحصاری [اثر را در اینجا توصیف کنید - جزییات اثر را بیان کرده آن را به ایمیل ضمیمه کنید و یا لینکی به آن در اینترنت را ذکر کنید] (میباشم/میباشد).
من موافقت خود را با انتشار اثر یادشده تحت مجوز آزاد Creative Commons Attribution-Share Alike 4.0 International اعلام میکنم.
من تأیید میکنم که با این عمل به هر فردی اجازهٔ استفاده از این اثر در محصولات تجاری و تغییر آن مطابق نیازشان را میدهم، به شرطی که شرایط مجوز و قوانین دخیل دیگر را رعایت کند.
من میدانم که این موافقتنامه محدود به ویکیپدیا یا وبگاههای مرتبط نیست.
من میدانم که مالکیت حق تکثیر و نیز حق انتساب اثر مطابق مجوز انتخابشده، همواره نزد دارندهٔ حق تکثیر محفوظ میماند. تغییراتی که دیگران در اثر اعمال میکنند به دارندهٔ حق تکثیر نسبت نخواهد داده شد.
من تأیید میکنم که لغو این موافقتنامه از جانب من ممکن نیست و اثر مذکور ممکن است بطور دائمی در یک پروژهٔ ویکیمدیا نگه داشته شود یا نشود.
[نام و مشخصات ارسال کننده (برای امکان تائید صحت اطلاعات)]
[اختیارات ارسال کننده (آیا شما رئیس، وکیل و یا خود صاحب حق تکثیر هستید)]
[تاریخ] — Preceding unsigned comment added by Mohamadhosein.a (talk • contribs) 18:24, 10 February 2019 (UTC)[reply]
@Mohamadhosein.a: خیر، اشکالی ندارد. ولی در حال حاضر تا جایی که من اطلاع دارم، مأمور فعال فارسیزبانی آنجا نداریم. بنابراین شاید به نفعتان باشد که ایمیل را به انگلیسی بفرستند. با این همه، اوتیآراس پروسهای زمانبر است و ممکن است شش ماه طول بکشد تا نوبتتان برسد. باید صبر داشته باشید، چون کل فعالیتها داوطلبانه است و تعداد داوطلبها زیاد نیست. 4nn1l2 (talk) 04:55, 11 February 2019 (UTC)[reply]
@Mohamadhosein.a: هر ایمیلی که به سامانه زده میشود، یک شماره بلیت به آن تعلق میگیرد و به فرستنده ارسال میشود. اگر شماره بلیت را اینجا بنویسید، بنده میتوانم خودم به آن رسیدگی کنم چون به اوتیآراس دسترسی دارم. 4nn1l2 (talk) 13:14, 20 February 2019 (UTC)[reply]
Thanks for all your help. We saved what we could...which was a lot more than I imagined with Google Cache Page...that's for sure. Best Regards, --Leoboudv (talk) 06:07, 7 February 2019 (UTC)[reply]
این تصویر متعلق به فرشاد محمدیمهر است، نه میثم تیموری! این سومین یا چهارمین تصویر است که از این کاربر میبینم با نام و رده اشتباه بارگذاری شدهاست.
هرچند زحمت قابل توجهی میکشند ولی کاش در مواردی که تخصص ندارند کمی دقت کنند! به هرحال... لطفا پرونده را بدون جایگذاری به نام صحیح منتقل کنید.
ببخشید که از سازوکار اصلی درخواست انتقال پروندهها استفاده نمیکنم، چون معمولا در این موارد مدیران خارجی دلایل را کافی نمیبینند یا صفحه را با جایگذاری منتقل میکنند! — Preceding unsigned comment added by Maometto97 (talk • contribs) 17:54, 11 February 2019 (UTC)[reply]
@Maometto97: سلام. پرونده را منتقل کردم، منتها با جایگذاری تغییرمسیر چراکه حساسیت زیادی سر حذف کردن این تغییرمسیرها در اینجا وجود دارد واگر تغییرمسیر را حذف کنم، کاربران زیادی به بنده معترض خواهند شد. درستش هم همین است زیرا این تغییرمسیرها ضرری به سامانه نمیرسانند، ولی از آن طرف، حذف آنها ممکن است لینکها (بالاخص لینکها از خارج ویکیپدیا/ویکیمدیا) را بشکند. معمولا فقط تغییرمسیرهایی را میتوان حذف کرد که عمرشان در حد یکی دو ساعت باشد (به روز نکشد) ولی این عنوان اشتیاه مربوط به سال گذشته است. 4nn1l2 (talk) 07:58, 12 February 2019 (UTC)[reply]
درسته، خیلی ممنون. منتها مشکل اینجاست که این تغییر مسیرها معمولا دارای رندترین نام ممکن برای موضوع خودشون هستند، مثلا اگر من بخوام تصویر واقعی میثم تیموری را بارگذاری کنم نام آن آزاد نیست!
جدا از این موضوع، عرض دیگری هم خدمتتون دارم، نمیدونم بحثی که درباره خبرگزاری میزان در قهوهخانه آغاز کردم را مشاهده کردید یا خیر ولی لطفا اگر امکانش هست به اون هم توجه کنید که آیا میشه از تصاویرش استفاده کرد یا خیر چون تا جایی که میدونم حداقل در زمینه گزارش تصویریهای فوتبال، کاملترین گزارشها را نسبت به سایر خبرگزاریها دارد. --Maometto97 (talk) 08:22, 12 February 2019 (UTC)[reply]
درست میفرماید... و خیلی ممنون بابت راهنمایی، سعی میکنم با دستاندرکاران این سایت ارتباط برقرار کنم تا شاید یکی از مجوزهای کریتیو کامنز را جایگزین آن جمله کنند --Maometto97 (talk) 12:39, 12 February 2019 (UTC)[reply]
@Amirsara: سلام. ایمیلتان را چک کنید. سریع پاسخ دادم. در ضمن در همهٔ پروژههای ویکیمدیا بهتر است از صفحات بحث (مثلاً همینجا) برای سؤال یا طرح مطالب استفاده کرد، نه ایمیل. ایمیل معمولاً فقط وقتی به کار میرود که موضوع محرمانه یا به نوعی حساس باشد. تشکر 4nn1l2 (talk) 12:30, 14 February 2019 (UTC)[reply]
Do you think we should keep all these images? I do think we could keep one of them and nominate others for deletion as they are redundant. What do you think? Thank you. T Cells (talk · contribs · email) 17:48, 23 February 2019 (UTC)[reply]
Hello T Cells, I don't think we should delete most of them, as they depict different stages in bubble blowing from different angles. However, some can be nominated for deletion. Personally, I think 07 and 08 are redundant with 06; 14 is redundant with 15; and 09 can also be deleted. I find other images useful. 4nn1l2 (talk) 18:40, 23 February 2019 (UTC)[reply]
درود بر شما؛ پروندههایی با نام Sardar Azmoun's first training with Zenit در Category:Sardar Azmoun بارگذاری کردم که مدتهاست نیاز به بازبینی دارند لطفا در صورت امکان زحمتش را بکشید.
@Maometto97: سلام. این پروندهها چون برچسب OTRS دارند نیاز به بازبینی (LR) ندارند. بازبینی فقط وقتی نیاز است که ۱) اثر مال بارگذار نباشد؛ ۲) اثر در اینترنت برای همگان قابل تأیید باشد. فلسفهاش هم این است که حداقل دو نفر مستقلاً تأیید کرده باشند که فلان اثر، زمانی تحت پروانهٔ آزاد در دسترس بوده تا اگر ۱) سایت خراب شد (پیوند از دست رفت)؛ یا ۲) مالک حق تکثیر نظرش را عوض کرد و پروانه را تغییر داد، بتوان پرونده را همچنان در ویکیانبار نگه داشت، چون پروانههای کریتیو کامانز غیرقابلفسخ هستند. بازبینی کار تقریباً سادهای است و نسبتاً سریع انجام میگیرد.
OTRS پروسهای دیگر است که به صورت مکاتبات محرمانه صورت میگیرد و نیازمند بررسی دقیق و صرف وقت کافی است. الان آزاد بودن این عکسهای زنیت برای عموم قابل تأیید نیست (برخلاف عکسهای مثلاً فارس یا تسنیم). مجوزی که صاحب سایت زنیت فرستاده به زبان روسی است که من از آن سر در نمیآورم ولی چون یک کاربر روسزبان (که قبلاً مأمور اوتیآرس بوده ولی الان نیست) آن را بررسی کرده و Template:FC-Zenit.ru را ساخته، صرفاً اعتماد میکنیم و بیشتر از این نگران نمیشویم. این دست تصاویر نیازمند بازبینی نیستند (چون امکان تأییدش برای بیشتر بازبینها وجود ندارد). خلاصه، الگوی نیازمند بازبینی را از آن تصاویر حذف کردم. 4nn1l2 (talk) 19:57, 28 February 2019 (UTC)[reply]
Your change to Template:Infobox copyright rules for shortcuts is not working, and I cannot see why. When I look at the template, it shows "Shortcut: COM:{{{COUNTRY}}}", which is correct as a no-parameter result. The code look fine. But with COM:Canada it gives "Shortcut: COM:{{{Shortcut}}}", which makes no sense to me. I must be missing the obvious... Seems to be fixed. Aymatth2 (talk) 13:41, 1 March 2019 (UTC)[reply]
See Commons:Currency/fr#Canada. It correctly picks up the French text, at least for now, even though the section header displays as "Monnaie" rather than "Currency" in the translated version. But the box "Texte transclus de COM:CUR Canada" links to the English version. Aymatth2 (talk) 13:41, 1 March 2019 (UTC)[reply]
We could maybe transclude using a template that returns standard section translations. E.g. "Currency" should always be "Monnaie" in French... Transclude from section =={{trCurrency}}==. Or just forget about transcluding non-English. Aymatth2 (talk) 14:28, 1 March 2019 (UTC)[reply]
I marked and translated COM:Mali and COM:Djibouti. With Mali I marked each infobox entry as translatable, but with Djibouti I just put the whole infobox into a translation unit. With both I put section headers and the first paragraph together in one unit. My aim is to minimise the amount of mark-up in the source, since this seems vulnerable to errors. Any thoughts on how long is too long? Aymatth2 (talk) 13:41, 1 March 2019 (UTC)[reply]
You fixed it yourself Special:Diff/341109235, you just forgot to mark the template for translation. I marked it and it started to work.
I think we should create separate templates like Template:CUR Country/fr and also mark the list of countries as a unit of translation so that translators can order the list of countries alphabetically. For example Allemagn would be at the beginning of a French list, but Germany would be at the middle of an English list.
I prefer the Mali method. I also think the name of country should be translated too. Please see COM:IRAN as an example. Persian language is written in a script other than Latin. Headers should be in a separate unit of translation. This is somehow a tradition in marking pages for translation and is emphasized in almost every help page. I would prefer not to break old habits unless there is a strong reason to do so. 4nn1l2 (talk) 15:28, 1 March 2019 (UTC)[reply]
Check if Page/Pagelanguage exists, and if so try to transclude from Page/Pagelanguage#TRsection, else...
Check if Page/en exists, and if so try to transclude from Page/en#ENsection, else...
Try to transclude from Page#ENsection
Transclusion would be done by a sub-template, which would render a heading line, box linking to the source page/section, and the section text.
I agree that the list of countries should be marked as a translation unit, but do not see an easy way to format the list so a translator can easily sort it by translated country name.
We could put a translatable template in between the list of countries and the generic template. E.g.
{{FOP Country/fr|Canada}}
would render
{{CRT Section |Page=Canada |ENsection=Freedom of panorama |TRsection=Liberté de panorama |Level=2}}.
I don't know if that is needed. It would make the lists more compact but less efficient. I suspect these lists will rarely be used. Aymatth2 (talk) 11:13, 2 March 2019 (UTC)[reply]
I will defer to your opinion. I have spent years on Wikipedia, where I expect most editors to be very non-technical, so the less mark-up the better. The combination of translation and transclusion mark-up looks deadly. E.g.
==Freedom of panorama== <!--T:44-->
</translate>
<!-- This section is "transcluded" to Commons:Freedom of Panorama#Canada. Please do not rename or delete it. -->
{{OkMark}} <translate><!--T:24--> for 3D works: {{tlx|FoP-Canada}}</translate> <br />
{{NotMark}} <translate><!--T:25--> usually for 2D works</translate> <br />
<translate><!--T:26-->
Under Section 32.2 (1)(b) of the ...
My first reaction is that this gobbledegook is guaranteed to be messed up by the first editor who tries to make a change.
But I suppose the editors who change pages like these will be more technical than most, so am probably over-concerned.
It is more important to make the pages easy to translate than to worry about mark-up overload.
I will separate out the items in the infobox, and separate the section headings from the text. Aymatth2 (talk) 11:13, 2 March 2019 (UTC)[reply]
I have made the notice jump out a bit more, perhaps too much. I may be over-concerned about the mark-up. Time will tell. Aymatth2 (talk) 13:21, 2 March 2019 (UTC)[reply]
The {{CRT list}} template displays country names translated into the page language, but links only to the English versions of the COM:CRT/ pages. It should link to the PAGELANGUAGE version, if it exists. I tweaked it so the first two entries do: If you are looking at Commons:Copyright rules by territory/Burundi/fr and click on "Comores" in the template, it takes you to Commons:Copyright rules by territory/Comoros/fr. The problem is, it relies on #ifexist, an "expensive parser function". Testing the 200 pages is probably too expensive. Is there a simple solution? Aymatth2 (talk) 17:27, 5 March 2019 (UTC)[reply]
I cannot think of any simple solutions. However, you can use up to 500 expensive parser functions, so there should not be any problems with a navbox of 200+ country-specific pages. There is another problem: the countries are not ordered alphabetically in languages other than English. 4nn1l2 (talk) 18:28, 5 March 2019 (UTC)[reply]
I have moved the Africa entries over to the #ifexist structure. I feel that there is a significant delay. When I view page source, I see
CPU time usage: 0.940 seconds
Real time usage: 1.462 seconds
That compares to this talk page with
CPU time usage: 0.276 seconds
Real time usage: 0.373 seconds
Maybe I am over-concerned. These are not high-volume pages.
The breakdown into continent/region was an attempt to partially solved the sequence problem. The template could be made translatable, with each group of countries in a translatable section, so the translator could sort them. That seems like a difficult task to me, and one that is unlikely to be done for languages where there are fewer translators. It could be simplified by making a template to generate the code. E.g. {{CRT format East Africa}}, giving something like (but with the correct text direction):
The second list can be used to generate versions of the first list in the sequence of any given language. Probably I just reinvented the wheel... Still, there must be a standard way to give translators instructions on how to handle these lists, if only a comment in the translation unit holding the list. Aymatth2 (talk) 14:06, 6 March 2019 (UTC)[reply]
Yes, I think you are reinventing the wheel, please have a look at Template:Countries of Europe which has already solved the problem of sorting by modules.
The problem of too many expensive parser functions can also be solved using COM:Lua.
Wikipedians tend to be quite non-technical, in my experience, but there are more of them, so maybe more chance of finding someone technical. They would be unlikely to have any experience in internationalization. I have converted {{CRT list}} to use Module:Countries. Not perfect:
It displays in the user language rather than the page language.
It sorts "Ivory Coast" under "C" for Cote d'Ivoire, and "North Macedonia" under "M" for Macedonia.
Eswatini links to Swaziland, and Micronesia to The Federated States of Micronesia.
It does not cover various former states and oddities like Aruba and Vatican City, so they need a separate section.
The text is tiny
It only provides a navigation box, so would not handle a transclusion list.
It does not put the list into langage sequence. When I change my preferred language to French, I get. e.g.
The last is the most serious. Not sure if it is a show-stopper. I can't see becoming a Lua programmer, although I may tinker with it a bit. The main push right now, I think, is to get the country pages all marked as translatable. If you look at the East African countries you will see the style I am moving towards:
Move citations out of the way to the untranslated {{Reflist}} at the back,
Leave some short bits of mark-up in the translation units, like {{sref|2006 Sec.13}} or <ref name=Law2012>, so the units do not have to be broken up into very small fragments. I think it should be easier to translate two or three related sentences than just one out-of-context phrase.
Use </notranslate> to cut other mark-up out of the units.
Ivory Coast [1], North Macedonia [2], Eswatini [3], and the French sequence [4] were fixed. According to the English Wikipedia, Micronesia seems to be the name of a region rather than a country, so I'm not sure if we should drop "The Federated States of" part from its name. I'm not familiar with Lua either, but we can get help from User:Dalba, I think. 4nn1l2 (talk) 22:40, 6 March 2019 (UTC)[reply]
That is encouraging – at first glance it seemed that the module did not support language sorting at all. There are still various problems with the French sequence:
Cap-Vert · République centrafricaine · Tchad · Comores · République démocratique du Congo · République du Congo · Djibouti · Égypte · Guinée équatoriale · Érythrée ...
Guinée-Bissau · Côte d'Ivoire · Kenya ...
Somalie · Afrique du Sud · Soudan du Sud · Soudan ...
Tunisie · Ouganda · Zambie ...
Dominique · République dominicaine · Équateur · Salvador · Grenade ...
{{CRT list}} should be made translatable for "Copyright rules by territory", "Unions & former states" and the list of Unions & former states. I will do that.
The "Unions & former states" list can be templated to reduce mark-up and given instructions and a sortable table for translators. I will do that
Module:Countries should also accept language as a parameter, so it can give results using page language rather than user language – that should be easy, unless there are problems passing through language to {{int:}}. @Dalba: is that something you could help with?
A translation unit comment can tell translators how to report sequence problems with the list in their language, maybe on a noinclude unit called "Sequence problems".
As for "The Federated States of Micronesia", the "the" is inconsistent with, e.g. "Netherlands", "United States", "United Kingdom" etc. A nitpick.
Where Module:Countries renders a list of links like [[&prefix;&country;&suffix;]], it would be very useful to have a variant that would render an unformatted list of entries like &prefix;&country;&suffix; that could be used to generated language-sorted lists with entries like {{Translatable template|FOP Country|Antigua and Barbuda}}. @Dalba: would that be something you could help with?
In this change I've added a language parameter. You may test it by {{#invoke:Sandbox|main|Asia|lang=<language-code>}}. Check to see if it's doing what you had in mind.
Regarding the "unformatted list of entries like &prefix;&country;&suffix;", I'm not sure if I correctly understand the expected format. Do you mean a new function like plaintext that when used like {{#invoke:Countries|plaintext|Europe|lang=en}} will return Albania Andorra Armenia Austria Azerbaijan Belarus Belgium [...] in plain text?
{{#invoke:Countries|template|Eastern Africa|template=Copyright rules by territory/Country|lang={{PAGELANGUAGE}}} }}
This would render a list of entries like {{Copyright rules by territory/Country|Burundi}}, sorted into the appropriate sequence for the language. It would not have to check for presence of the country, which could be handled by the template.
There two more complicated lists:
Commons:Stamps/Public domain should have a list entry for each country that has a category like Category:Stamps of country
Commons:TOO should have a list entry for each country where Commons:CRT/country has a section named "Threshold of originality"
I would see Stamps as low priority and TOO as very low priority.
A separate question: I think Aruba, Curaçao, and Sint Maarten should be in the Caribbean / Americas lists as "other areas", and Faroe Islands should be in the Northern Europe / Europe lists as "other areas". Thanks, Aymatth2 (talk) 15:29, 7 March 2019 (UTC)[reply]
Thanks. I didn't know anything about this controversy. Still I believe we should stick to Myanmar because 1) Commons should remain a politics-free zone; 2) Commons had better use International English rather than British or American English. 4nn1l2 (talk) 16:21, 7 March 2019 (UTC)[reply]
@Dalba: Please see Translations:Commons:Currency/Asia/3/fa as an example. I just sorted the list of countries manually according to their Persian names and it was laborious (considering the fact that it should be repeated for every list in every page). We are trying to find a smarter way to create such lists. Thanks for your help. 4nn1l2 (talk) 11:34, 7 March 2019 (UTC)[reply]
I've create Module:TNTExpandByCountries that when called as {{#invoke:TNTExpandByCountries|main|Asia|lang=fa|template=CUR Country}} should create the same output as Translations:Commons:Currency/Asia/3/fa. I've used an inefficient algorithm in TNTExpandByCountries and therefore decided not to add it to Module:Countries. It is possible to rewrite TNTExpandByCountries using a more efficient and robust algorithm, but that would require rewriting large parts of Module:Countries that unfortunately I don't have time for.
There seems to be a conflict between Translatable template and Module:Countries. {{translatable template|CRT list}} renders each list followed by the message: Error: invalid parameter "|uselang=|noshift=|template=Template:CRT list"Aymatth2 (talk) 16:53, 7 March 2019 (UTC)[reply]
The Americas list is not picking up Aruba, Cayman Islands, and the Asia list is not picking up Hong Kong, Macao.
There is still a lot of mark-up to do, and a whole lot of translation, but I think a very solid structure is being established. I made an attempt at documenting it at Commons:Copyright rules by territory/Structure. Any improvements to that page would be welcome.
I am working through redlinks in the currency list making stubs, which I may expand. Even if a breakaway state has no international recognition, a page discussing copyright for images from that state should have value.
By removing 'simple' argument from Module:TNTExpandByCountries[6], Macau, Hong Kong, Aruba, etc will appear. However, many lesser-known territories or partially recognized countries in the Caribbean will also appear. The problem is that I assume we cannot give Hong Kong and Macao special status in the main general module, but we can do so in our own modules if created. The drawback of creation of special modules is that CRT templates will not benefit from sequence updates. Please see Commons:Currency/Americas and let me know your opinion. 4nn1l2 (talk) 19:31, 9 March 2019 (UTC)[reply]
I don't see a problem with dropping "simple", and think it would be an improvement. It only adds about 30 pages. People will ask about places like Bermuda or Réunion, and short articles will be useful. I can start stubs for them. Some, like Florida Keys or Azawad, may not be much more than redirects. Others may have a bit more substance. I vote to keep the full lists and volunteer to turn all the redlinks blue. Aymatth2 (talk) 01:15, 10 March 2019 (UTC)[reply]
By dropping simple, the sorting order is only kept for each group of countries, e.g. in European countries Akrotiri and Dhekelia will come after Vatican City:
It is possible. You mean hard-coding the module to generate level 3 group titles or adding a level parameter to the module? Do you have use case in mind? Dalba14:33, 10 March 2019 (UTC)[reply]
@Dalba: I would like a parameter, like {{#invoke:TNTExpandByCountries|main|Americas|lang={{PAGELANGUAGE}}|template=CUR Country|hlevel=2}}. The |hlevel= parameter would default to 2 but could be overwritten. Examples:
Commons:Currency/Americas The present heading ==List of countries== would be replaced by the new level 2 headings.
Commons:Copyright tags |hlevel=3. The present heading ===Country-specific tags=== would be replaced by the new level 3 headings
@Aymatth2: |hlevel= is now available. Note that since {{CUR Country}} uses h3 headings by default and there is no way to pass any parameters to {{CUR Country}} from module:TNTExpandByCountries, you'll need to create another template, say Template:CUR-Country-with-level4-headings and use that when invoking TNTExpandByCountries, otherwise group headings and country titles will have the same level when |hlevel=3 is used. I couldn't think of any simple and clean way to address this issue on the module side.
@Dalba: That looks great. There is no problem with the levels. {{CUR Country}} is only used in areas where headings levels are 2, and {{TagsCountry}} is only used where headings levels are 3. Both use the same underlying template {{CRT section}}, which takes a level= parameter. See Commons:Copyright rules by territory/Structure for more on the way these lists and pages fit together.
Would something like {{CRT format East Africa}} be useful in getting sequences for different languages? The idea is that a set of English country/territory names are hardcoded in a template. You pass it a language code and it returns a table that can be sorted for that language. {{CRT format East Africa2|lang=en}} sorted gives BI KM DJ ER ET KE MG MW MU MZ RW SC SO SS TZ UG ZM ZW, while {{CRT format East Africa2|lang=fa}} sorted gives ET ER UG BI TZ DJ RW ZM ZW SS SO SC MG MW KM MU MZ KE. Aymatth2 (talk) 16:33, 10 March 2019 (UTC)[reply]
I do not know the programming language, but towards the end of Module:Countries I see "List of countries in an order suitable for display in the specified language", which gives sequence lists for en, de, fr, mk, uk and no other languages. So I get the feeling that sort sequences are missing for other languages. Something like {{CRT format East Africa2}} could not be directly incorporated in the module, but could make it easier to build sequence lists to be added to the module. I think. A maintenance tool. Aymatth2 (talk) 21:05, 10 March 2019 (UTC)[reply]
Hello 4nn1l2, I wanted to ask if you can take a look at my request for becoming a file mover on Wikimedia Commons. The request can be found here: Commons:Requests for rights. Can you already give me the rights for file moving? Or do I have to wait several more days? Hope for a short answer! Best regards, Chem Sim 2001 (talk) 17:48, 12 March 2019 (UTC)[reply]
I have marked for translation the CRT pages in Africa, Americas, Oceania and some Others. I expect to keep going through Asia and Europe. I have a sort of mental checklist now of all the changes needed, so may as well complete the job. Some of the pages need editing to prepare them for translation. E.g. text like
See [http:www.long_gone/404/deadlink.htm this site] for details
should be converted to a properly formatted live link like
The Ruritanian Law Society provides details.</translate><ref>{{cite web|accessdate=2019-03-21|url=...}}</ref><translate>
This is going to take time with the larger pages.
Three questions. Most pages at the end have sections like:
==See also==
* [[Guadeloupe]]
* [[Commons:Copyright rules by territory/Overseas France]]
==References==
</translate>
{{reflist}}
I would like to move this stuff out of translation with something like:
</translate>
=={{trSee also}}==
* [[Guadeloupe]]
* [[Commons:Copyright rules by territory/Overseas France]]
Honestly, I don't think that is a good idea, because it kind of complicates the source text. Translating simple words such as "references" and "see also" is virtually effortless, especially considering the fact that the Translate extension remembers the content of translation units and suggests repeated expressions to translators, and they only need to select the appropriate option by clicking on it (i.e. they don't even need to type anything). 4nn1l2 (talk) 16:41, 26 March 2019 (UTC)[reply]
That links to the page for my preferred language, but I think it should try in turn to link to
The language of the page I am reading, if non-English
My preferred language
English
So if my preferred language is Catalan but I am reading Colombia/Spanish, then click on Panama, I would want to go to Panama/Spanish, not to Panama/English because Panama/Catalan does not exist. My guess is that it is common for a user to have a poorly supported preferred language, and a better supported fallback language other than English. I seem to recall that Babel supports a fallback language sequence, but I do not see that in preferences. Aymatth2 (talk) 17:46, 26 March 2019 (UTC)[reply]
But I would rather show the translated title, e.g.
* {{trlink|Commons:Copyright rules by territory/Overseas France}}
would render, for page language=fr where the target has a French version:
* [[Commons:Copyright rules by territory/Overseas France/fr|Commons:Droit d'auteur par territoire/France d'outre-mer]]
The idea is that once a Catalan user has chosen to view Spanish versions of pages, as they browse from link to link they will keep getting Spanish versions where available. They will not get bumped down to English because the linked page is not available in Catalan. But if they click on a link that is not available in Spanish, they will get a version in Catalan if available, or in English as a last resort.
Seems reasonable to me ... but there really should be a discussion / guideline somewhere. I am not going to rush to implement it. Aymatth2 (talk) 15:05, 27 March 2019 (UTC)[reply]
If you would care to add {{CRT editnotice}} to the COM:CRT/Country pages, that would be useful. I worry that regular editors will decide to delete all the meaningless comments like <--T:13-->Thanks, Aymatth2 (talk) 17:53, 30 March 2019 (UTC)[reply]
سلام. این وبسایت یک سری عکسهای تاریخی و مهم دارد (مثل این) به نظر شما میشود فرض کرد که مالک عکسها خودشان باشند و در انبار بارگذاریشان کرد؟ Hanooz14:24, 31 March 2019 (UTC)[reply]
سلام. بعید میدانم این تصاویر ربطی به سید علی خامنهای داشته باشد. تصاویر قدیمی از خود آقای خامنهای یا اتفاقات مرتبط به ایشان را میتوان با حسن نیت پذیرفت (چون عنوان سایت هست «دفتر حفظ و نشر آثار حضرت آیتالله العظمی خامنهای») ولی سایر تصاویر تاریخی که مستقیما مربوط به ایشان نیستند (و تا حدی جنبه ملی دارند) را به نظرم نمیتوان. --4nn1l2 (talk) 17:52, 31 March 2019 (UTC)[reply]
4nn1l2 First of all, Thank you for everything you do. I think the picture is related to the previous leader of Hezbollah "Subhi al-Tufayli" in Lebanon, while the name is related to a leader of Muslim Brotherhood organization in Jordan "عبد اللطيف عربيات", who was the head of House of Representatives of the country .--الرشيد (talk) 08:50, 4 April 2019 (UTC)[reply]
The country of Origin is Colombia for the El Heraldo article. Uploaded be me this morning. I di not believe it to be copyrighted for time period I am gathering additional info.thank you for your help--Deanna Coakley (talk) 17:29, 4 April 2019 (UTC)[reply]
I cobbled together a solution with {{CRT list2}}, using {{Pg}} to make the country page links. See Template:pg#See also for the rationale. It is on COM:CRT/Peru for test purposes. It works as it should, pointing to English targets from Peru/en, mostly to Special:Mylanguage targets from Peru/es and mostly to French targets from Peru/fr. But on the /es and /fr versions it gives "Lua error: too many expensive function calls" when it gets to Oceania. It probably hits the limit of 500 on #ifexist calls (does the translated page exist? Does it have a translated title?). Three possible solutions:
Break up the template so countries in the Americas use Template/CRT list/Americas, in Asia use Template/CRT list/Asia and so on, with maybe some way to toggle between the continental list templates.
Find a way to periodically regenerate language versions of the lists, so some time after a new COM:CRT/country/fa is created, Template:CRT list/fa would be updated by a bot to point to the new page.
Get something built in the wiki software similar to Special:Mylanguage that would check for a version first in page language, then in preferred language and finally in English.
The first seems most practical, but would not work for the main COM:CRT page.
I tried https://tools.wmflabs.org/commonshelper link to copy the image but it didn't work (Why?). Sometimes I find in public domain photos in Persian Wikipedia. Like: Newspaper-rezakhan.JPG, and Khalkhali2.jpg. Is there any way for me to copy these photos to Wikimedia Commons?
wikimedia.org تماس بگیرد و اجازهنامه را برای بنیاد ویکیمدیا ایمیلی ارسال کند. خواندن COM:OTRS/fa نیز توصیه میشود. 4nn1l2 (talk) 07:21, 10 February 2019 (UTC)
Comment: The video files in Chunks 1, 2, 3, 4 and 5 in User:Alexis Jazz/DWDD archief that have NOT been reviewed or passed should be speedily deleted sadly. GRuban, I, RoyH and you saved what we could. Best, --Leoboudv (talk) 23:36, 6 February 2019 (UTC)
Delete vote. 4nn1l2 (talk) 05:18, 7 February 2019 (UTC)
Translated. Thanks 4nn1l2 (talk) 16:55, 5 March 2019 (UTC)
