Thanks for mixing fixing the mess that I sometimes leave behind. You are a good wik-friend. I have had to submit a number of reports here and I have to appear in my semester exams from 18. That's why perhaps I couldn't check for these things. ─ The Aafī (talk) 17:53, 15 January 2023 (UTC)Reply[reply]

Don’t worry, typos may arrive for everybody. And Translate markup is really painful. 🙂 -- Pols12 (talk) 18:58, 15 January 2023 (UTC)Reply[reply]
Thanks. Anyways, do you have any idea about how can I fix this? The translation for "this image" and if I am not able to do it locally. ─ The Aafī (talk) 16:56, 16 January 2023 (UTC)Reply[reply]
It is hard to investigate for me, as I can’t read Urdu, but I think most English text come from ur:سانچہ:Deletable_file. --Pols12 (talk) 20:43, 16 January 2023 (UTC)Reply[reply]
and similarly the Urdu translation of "Shortcut" like here. ─ The Aafī (talk) 16:57, 16 January 2023 (UTC)Reply[reply]
That comes from Template:Shortcut caption. --Pols12 (talk) 20:43, 16 January 2023 (UTC)Reply[reply]

Translation requestEdit

Hello! Any change you might be willing to translate en:Wiki Loves Pride into French? I saw you made an edit to a Queering Wikipedia page, and your profile says you do translation work. Figured I'd ask. Either way, happy editing! -Another Believer (talk) 05:32, 7 February 2023 (UTC)Reply[reply]

I’m sorry to decline your request, because I’m not inclined to translate Wikipedia articles, especially because it speaks about Wikimedia movement itself. Yet, I would be glad to help translate some content on Meta-Wiki, if needed. I hope you understand. 🙂 -- Pols12 (talk) 13:12, 8 February 2023 (UTC)Reply[reply]
No worries at all! -Another Believer (talk) 05:01, 9 February 2023 (UTC)Reply[reply]

Iberoconf pagesEdit

Hello @Pols12 Thank you for the changes you are making to the Iberoconf 2023 pages[1][2], however, we appreciate your input for it is already pre-designed so please do not make changes and/or configurations to them. Thank you very much, Monica. [1] [2] Monica Bonilla (WMCO) (talk) 15:52, 8 February 2023 (UTC)Reply[reply]

@Monica Bonilla (WMCO), I understand. However, while editing the pages, please keep them accessible. Please also note, if you expect them to be translatable, we’ll need to mark them for translation, so they will need to comply with Internationalization guidelines. Please ping me if you need further help, especially for internationalization. Regards, -- Pols12 (talk) 16:02, 8 February 2023 (UTC)Reply[reply]


Hi @Pols12, I hope you are doing well. Could you please help me here? I marked the template for translation after adding tvar tags but since it uses some more templates inside it, I'm not getting how do I prepare these three things for translation there: Project In Search of the Roots, NDEC Wikipedia Editorial & Research Team and Notre Dame College, Dhaka. The problem is that it is wrapped in color templates and I don't really feel okay in bring the color stuff into translation. I would appreciate your help. Thank you! ─ The Aafī (talk) 05:21, 23 February 2023 (UTC)Reply[reply]

With templates and complex formatting, we can’t do wonders. We should only try to mask template names and parameters which could be wrongly “translated” by translators. So I would use
[[<tvar name=1>:m:NDEC/Project Roots</tvar>|{{<tvar name=2>color|white</tvar>|Project Roots}}]]
to provide
[[$1|{{$2|Project In Search of the Roots}}]]
However, in many cases, and in that specific case, we can improve the wikifying to better separate formatting and content. I have just edited the template to color links through templateStyles rather than through {{color}} template. -- Pols12 (talk) 17:32, 23 February 2023 (UTC)Reply[reply]
Thanks @Pols12, I just fixed the tvars and marked the template for translation. Thanks for your kind support. we can’t do wonders but you always do wonders for me. Thanks a lot. ─ The Aafī (talk) 03:01, 24 February 2023 (UTC)Reply[reply]

CIS-A2k and stuffEdit

Is there any way to keep CIS-A2K/Requests/Projects out of translation because it is just a header that's already in translation but at the same time keep the page in such a position that people find the header included on that page in translation (available to be read in another language). Do you think removing this page from translation, and subsequently removing noinclude stuff from CIS-A2K/Requests/header/Project solves this problem? Regards, ─ The Aafī (talk) 10:50, 24 February 2023 (UTC)Reply[reply]

The problem being that the pages such condition or using the tvars don't help the translation of that page get transcluded such as on CIS-A2K/Requests/ur and others. ─ The Aafī (talk) 10:53, 24 February 2023 (UTC)Reply[reply]
Unless one adds a language code. See this. ─ The Aafī (talk) 10:53, 24 February 2023 (UTC)Reply[reply]
Pinging @Jayantanth from the CIS-A2K who happens to be a translation admin himself. My suggestion is that we just mark the header for translation and since we need its translated versions on several base pages, we remove no-include wrapper from "languages" tag. ─ The Aafī (talk) 10:58, 24 February 2023 (UTC)Reply[reply]
The background is that pages like CIS-A2K/Requests/Projects are really not okay for being in translation. There are just requests that could be posted in any Indic languages. If we discourage the page from translation, people can't get through the translated header, given the pages current setup. ─ The Aafī (talk) 11:02, 24 February 2023 (UTC)Reply[reply]
Here, we have two possibilities:
  1. Keep the page in Translate system, with this hack: using an empty <translate></translate> pair. Only the page title will be translatable. The main issue is: translation pages are not editable and each change in source page must be marked for translation to be visible on translation pages, which is confusing for discussion participants.
  2. Transclude the header in user interface language: we use {{TNT|uselang={{int:lang}}}} (or {{dynamite}}) but we remove the page from Translate system, i.e. we don’t add any translate tag. To see the header in another language, the editors must change the MediaWiki language in their preferences.
For discussion pages, I recommend to use the second solution: it ensures the page is ever editable and up-to-date. So I’m applying it; if you would like the first one instead, please add an empty translate tag pair in the page. 🙂 --Pols12 (talk) 13:25, 24 February 2023 (UTC)Reply[reply]
I'm happy with it. Thanks once again. ─ The Aafī (talk) 13:39, 24 February 2023 (UTC)Reply[reply]

Preparing for translationEdit

Hello! I was working on migrating Wikipediholic to the translate extension. I wanted to split the bullet and numbered lists as per the i18n guidelines, but the extension keeps complaining about nested translate tags. Before marking it for translation and start porting old ones via Special:PageMigration, could you please take a look and let me know what I'm missing? Feel free to do the changes you feel are necessary. Thank you. Best regards, —MarcoAurelio (talk) 15:10, 26 March 2023 (UTC)Reply[reply]

Note: I tried to keep the number of "translate" tags low so I only added them on top and bottom of the page. Maybe I should further split the source to avoid those so-called "nested" translating tags... —MarcoAurelio (talk) 15:15, 26 March 2023 (UTC)Reply[reply]
@MarcoAurelio, I see you finally achieved to split the units. Indeed, we must close the “global” translate tag before opening a new one for a list item or other short item.
The segmentation was fine (good job!); I only changed tvar names, since they must be unique only per unit, not in the whole page.
I let you mark the page for translation. -- Pols12 (talk) 16:16, 26 March 2023 (UTC)Reply[reply]
Hello. Thanks for taking a look and fixing that. I wasn't sure the tvar names had to be per-unit or per-page :-) I also tried to keep out of the translate tags the <poem></poem> ones, but the extension doesn't like it. I was wondering if we could use the translate nowrap with these? —MarcoAurelio (talk) 16:22, 26 March 2023 (UTC)Reply[reply]
We could exclude poem tags with the following syntax:
<poem style="font-style: italic">
But translators would not know they are translating a poem. Also, some languages avoid italic formatting, so translator should be able to remove it.
I think the nowrap attribute is useless here, as long as there are no empty line inside the poem: if it is not translated, the whole poem will be wrapped inside <div lang="en">, that should not cause any issue.
-- Pols12 (talk) 16:35, 26 March 2023 (UTC)Reply[reply]
Thank you. I'll wait a bit before marking it for translation just in case. Many thanks for your help. —MarcoAurelio (talk) 18:22, 26 March 2023 (UTC)Reply[reply]
So... this is not going as expected. See Wikipediholic/de. Importing these pre-Translate translations is breaking some stuff. I think I'll revert and leave things as they were :-( —MarcoAurelio (talk) 21:26, 26 March 2023 (UTC)Reply[reply]
I’m sorry, but I don’t understand what you expect with PageMigration. The pages had not the same structure, so they cannot be aligned automatically. Actually they even seem to not being translations. PageMigration can help to restore some contents which are actual translations, but we cannot keep distinct contents through translation pages using Translate. -- Pols12 (talk) 21:49, 26 March 2023 (UTC)Reply[reply]
I was working under the assumption (it's been a while I last used PageMigration) that I could restore the old text before enabling page translation swapping and deleting translation units using that special page. I've restored everything as it was before, except for the page moves which I'll leave since it allows me to use the {{languages}} template and get rid of {{wikipediholic}}. Apologies for the inconvenience. —MarcoAurelio (talk) 22:04, 26 March 2023 (UTC)Reply[reply]
I think that may be possible, but that would create fake translations for the units. If we expect the page to be synced, the English text is better than previous “custom” text, in my opinion.
No inconvenience at all for me, don’t worry. 🙂 -- Pols12 (talk) 22:14, 26 March 2023 (UTC)Reply[reply]