I just checked and noticed that Wikifunctions now renders HTML/wikitable tables beautifully. It looks like this task has somehow been resolved.

@Dumbledore and @Xqt Abandoned, after all this?!

@Dumbledore, yes, just replace the current master file with the attached file here. Plus, change that comment line. And if i noticed something wrong, I will tell you. Thanks!

@Dumbledore Based on my tests , the attached file is the correct final version.
Just please change # This safely removes entries in <gallery> tags, lists, and templates. with # This safely removes entries in <gallery> tags.

Hi @Xqt and @Dumbledore, I have fixed and verified the fixes locally. I believe this task is now resolved and ready for final review.

@Dumbledore, unfortunately, this update introduced regressions.

Thank you for working on this. I updated delinker.py with your patch and tested it locally. The results are mixed:

Thanks, @Jdforrester-WMF. Your advice was spot on, and this is now fixed.

@matmarex, it is okay. I confirm the change is live now. Thank you, everyone!

@matmarex I had assumed resolved tasks were already live. That link you provided shows: Error: Our servers are currently under maintenance or experiencing a technical issue, but I'm accepting it. I’ll wait until next week. Thanks, and also thanks to Ebrahim for resolving this issue.

@TheDJ, The issue is still present. Please click the link I added in the description, then try inserting a table, link, or file—you’ll see that the box remains stuck on the right side for RTL languages.

@Xqt, Is this what you meant?
Command: python pwb.py "movepages" "-family:wikipedia" "-lang:test" "-noredirect" "-from:Wikipedia:Movepages test" "-to:Wikipedia:Movepages test2" -log -debug:comm
And here is the log file:

@Xover, thanks for the explanation. Looks like the restrictions on testwiki don't let me to give it a good try. I have all permissions on my home wiki, but there is no task to do.

@JJMC89 You closed this as invalid but didn’t provide any explanation. Could you clarify the reason?

Hi @Xover, looks like I mistakenly used -movesubpages instead of -nosubpages (not sure where I got that from). By default, subpages should move unless -nosubpages is specified.

In T394655#10873878, @JAnD wrote:

Why? Where it was discussed? Why was not announced to local communities (e.g. via tech news)? there was only that link will be moved, not removed.

Exactly—that's what I wanted to say. This was a poor decision made without informing communities. If it was done without a solid reason, then it's clearly a mistake—and they should expect more phab tasks like these in the future.

Just ignore it.

@Kaleem_Bhatti Done per your request. However, the final result will be visible in the upcoming updates.

@Bawolff, I believe everything is ready, and we're just waiting for the update. As for ckb.wiktionary, I don't think it needs this configuration, as it’s more sensitive to individual letters/characters. Regarding number sorting, I’m not entirely sure, but I don’t think we need it either for now.

Just to clarify, with putting vowels under their own header now, are we including وو in a separate header?

No, please. وو should be under و.

With the new changes, the only pairs of characters that are equal weight are: ک & ك and ھ & ه

Exactly!

Its tied to number sorting. If we sort numbers in numerical order, then we have to put them under one header. We can change what the header is, but all the numbers have to go together when using number sorting. The only way to have separate headings for each number is to disable number sorting and use lexicographic order for numbers.

I think we’re good with number sorting and the ٠-٩ header for all numbers.

We can move specific letters later, but any letters that are left to their default ordering come before customized letters (So we can move the normal latin letters later, but variants like Á would likely still come first).
This is one of the downsides that the "custom" collations have that the UCA collations don't.

For now, we don’t have better options for sorting non-ckb letters, so let’s keep the default behavior as it is without rearranging any letters.

We can make these letters be part of their own section or as part of a different section (as is done in the demo).
I think making the vowels their own section probably makes the most sense. The only time it would come up would be for articles about them since they otherwise never start a word. However we can do whichever is preferred.

Thanks for your input on vowels. Since we've decided to give them their own headers, let's move ێ into its own section.

Right now we mark them as being the same. So if there are no other letters in the word to break the tie, then the order they come in is random (Its probably whichever article was created first comes first, but I'm not 100% sure).

I initially thought the indexes determined the priority of letter order, but it seems they don’t affect the order within the same array. Since it's not about priority, we’ll leave them as they are.

@Bawolff Thanks for creating the demo and for all your explanations. I tested the demo and noticed the following:

@Bawolff, sorry for the late reply.

I thought no one cared about this—thank you, everyone! While ckb and fa are somewhat similar, there are still differences. By the way, ckb has the same issue with the letter Heh. For example, the word «ھەور» (cloud) begins with the letter «ھ» but is classified under the letter «ه».

@Nemoralis, ah, so we don’t need to specify the site if we're on a different language version of the same project! However, it's odd that the shortcuts work perfectly everywhere, while the long form doesn't when the target is the same site.

@Xqt, thanks for looking into this. The -type: option would be a fantastic feature if it could be implemented, but if it's too complex, feel free to skip it. What are your thoughts on the first two points?

Apologies for the comment; I just wanted to ask if someone could address this issue. It has been two years now!

I have an issue related to this. See here.

@Xqt, WMF, and communities must be proud of you. I'm speechless—you made it! Just for the record, here are the statistics:
Command: python pwb.py delinker.py -family:wikipedia -lang:ckb -localonly -category
Results:

@Xqt, Thanks for taking care of this!

@Xqt, @Enag2000 has been inactive for six months and this task is important to address. Can you please do something about it? Thanks.

@Ebrahim, Thank you for commenting and using this task information. I'm really disappointed that I still see this issue as it is.

@Umherirrender Thank you for your explanation! Well, I got it, but it still seems weird to me. Why is the local redirect page somehow related to Wikimedia Commons? And why did the local and Commons uploaders, which are two different uploaders, both uploaded a file under the title File:ImageHandler.png? There could be a link somewhere that will create/upload a file under that title. By the way, I found another file on Commons but with another extension. Here: File:ImageHandler.jpg. Perhaps there is a problem somewhere that needs to be addressed.

@Xqt, That's the question I expected! This is just my answer and it may be better to get the experience of experts. If we’re just talking about adding a welcome message, yes, the extension defeats the script leaving it no chance to welcome users, but the script can still check for bad names, has many features and fully customizable. The extension usually don't let welcom.py script from adding welcome messages because once an account is attached to the project, the extension immediately sends a welcome message. I don't know about the extension configurations, but take a look at User:New user message contributions on ckbwiki; all of them are just sending a welcome message.

@Xqt, I don't know how you found out I was using PS, but I must say you're really smart. Now, I got what you got using "" in cmd and escaping using backtick

`"`"

in PS. And thanks for suggesting template script, but I was just wanted to use replace, found that error and we are here. I have nothing left to say but thank you! If you want, please change the title to something with PS.

Without escaping:

@Xqt, I have updated python to the latest version 3.12.3 and tried -3.12-64 and -3.10-64 launchers. Both launchers were the same. This is escaping one:

Edition: Windows 10 Pro
Version: 1909
OS Build: 18363.900

@Xqt, Sure, I just updated to the latest version:

The same thing:

@Xqt, Sorry for reopening it. I couldn't reply; I went offline for about one week. However, It looks like you haven't got that error message and it's working for you. But for me, after reseting my Pywikibot, I'm still getting that error message and I don't know why our results are different.

To avoid wasting your time, there is an alternative.

@Xqt, Sorry, I was stupid; at first I added:
usernames['test']['wikidata'] = 'AramBot' in user-config.py file, but I just realized that the format should be like: usernames['wikidata']['test'] = 'AramBot'. I made test edit such as this one. Now, I am happy that pywikibot already supported "test.wikidata.org". A huge thank you!

Is there an invisible characater within your text file?

Just answering your question. These days I generate my lists using AWB. I checked the list (especially the first title) and no, there wasn't any invisible characters. I don't know why I have the problem, but you don't.

Created one year ago on March 29, 2023. I don't know if this is configuration or bug related.

In T345033#9571673, @Xqt wrote:

Hi @Aram: I removed the -up option and made it default as suggested. I didn't found the immage → image for replacemet within the code. The -nouserwarning is right as it it because this is just a but to be set instead of additional input requirements for that option.

No, -up is still not the default and I have to use it to see the template at top. You can see immage in patchset 2 and looks like you've replaced it to image in patchset 3. But if we make the up as default, we don't need -up anymore, but we need -down instead. Am I right?

Sorry, I just found a new problem. I used -always. First warning was good, but second warning was just changing the file title of the first warning instead of adding a new message. I checked the diff changes and they were okay, but that second edit says something else. This time, I tried to manually save edits by pressing y and I didn't find the same case. So, there is something wrong with -always parameter.

@Xqt, Special thanks! Technically, it is now working for me as I wanted. But I think we didn't want to create -up because almost all these kind of templates should be placed above. However, if you still consider it necessary, then we may need to make "-up" the default. If you don't want to do so, I'm still good with your update now.
Please do these replacements:
immage → image.
maximum number of articles → maximum number of pages|images|files (I don't know which one is the best).
-nouserwarning → -nouserwarning: (Just a colon).
I'll vote in the next edit. Thanks!

@Xqt, Can you please care about this please? This is not difficult.

In T356782#9525790, @Xqt wrote:

Hm, there are several sites in langlinks but it should not have to logged in there.
For a work-around you could use
usernames['wikipedia']['*'] = 'AramBot'

@Xqt, This time it worked without any errors! I don’t really know why we have to specify all the projects. For me to use "commonscat.py" script with OAuth, I have to enter these two lines.

@Xqt, No. Every time it asks to add a new project.

usernames['wikipedia']['en'] = 'AramBot'
usernames['wikipedia']['fa']= 'AramBot'
usernames['wikipedia']['id']= 'AramBot'
usernames['wikipedia']['am']= 'AramBot'
...

Sorry for reopening. You were right. My bot wasn't attached to Commons, but after attaching, I still faces these errors. Even I can't understand it; it's weird!

@JJMC89 Great! And huge thanks to you!

Done, all jobs migrated! Just three questions:

In T351951#9400287, @Xqt wrote:

I haven't found any → in the code but in the i18n at translatewiki and this should be changed there.

No, the symbol → is in the category_redirect.py and not related to translatewiki.net. It is in self.newredirs.append('*# {} → {}'.format(.

This is intentional because you pressed Ctrl-C instead of choosing N for the question Continue with soft category redirects ([y]es, [n]o)

But in case of working on hard redirects and Ctrl-C for soft redirects, we need to print the execution, read, write and skip statistics rather than just quitting the script.

This is a good catch and I am working on it.

Thanks! This is now solved.

We currently have no other implementation except change_category. Maybe it it a feature request but it is not trivial to implement it.

If we collect all modifications and publish all in just one edit per page, we save the history pages from expanding.

With -always option hard and soft category checks are processed without any questions. If hard category check is interrupted (Ctrl-C) the following soft redirect check is not done.

I'm not sure about this, but I think we have to let the operator to just work on the soft redirects only and skip the hard redirects if they wanted.

@Xqt, Thank you! Much closer to perfect this time. The bot has made some good edits and this is the log revision, but in the code/log we have symbol →, but this is for LTR languages and it is better if we print ← for RTL languages (if applicable).

@Aklapper, I would like to confirm that the sitenotice alignment issue has been observed. Specifically, on both ckbwiki and kuwiki, we currently have an identical sitenotice.

@Xqt, After updating scripts/category_redirect.py with your last edit and running the script, looks like it is now modifying the old categories to new ones as you can see in this edit. The diff, edit summary and prompt were showed. But the script firstly, Checking hard-redirect category pages and after interrupting the script, it says:

User quit CategoryRedirectBot bot run...
Continue with soft category redirects ([y]es, [n]o):

I said yes, and this is the next lines:

In T351951#9387697, @Xqt wrote:

In T351951#9384705, @Aram wrote:

@Xqt, The code you showed me is correct. I tried updating my Pywikibot directory (which is stable version) via git and it was successful, but the i18n submodule wouldn't update, anyway, I updated it manually and here's an example.

I think submodule has to be updated additional to the Pywikibot branch or in one command like git pull --recurse-submodules. But I am not familiar enough with git, sorry.

In T351951#9380567, @Xqt wrote:

@Aram: Cannot reproduce the i18n issue. After adding print statements I get:

D:\pwb\GIT\core>pwb -simulate category_redirect -lang:ckb
Checking hard-redirect category pages.
بۆت: زیادکردنی داڕێژەی ڕەوانەکەری پۆل بۆ چاکسازی
@@ -1 +1 @@
- #ڕەوانەکەر [[:پۆل:ئابووریی بەرھەمھێنان]]
+ {{ڕەوانەکەری پۆل|ئابووریی بەرھەمھێنان}}

SIMULATION: edit action blocked.
Page [[پۆل:ئابووریی بەرهەمهێنان]] saved

Please ensure that you updated submodule if you are using git or svn repository.

@Aram: Could you please give an example.

Sure. If you mean an edit summary sample, I provided this one already here. And If you mean the translations, see here; actually, all messages are translated.