Difference between revisions of "ArchWiki:Requests"

From ArchWiki
Jump to: navigation, search
(AUR went https: re)
(New Official ISO: re: tried to fix Beginners'_Guide#Select_packages i686/x86_64 balance issue.)
Line 81: Line 81:
 
::-- [[User:Kynikos|Kynikos]] 14:22, 20 October 2011 (EDT)
 
::-- [[User:Kynikos|Kynikos]] 14:22, 20 October 2011 (EDT)
 
:::I agree about the i686 centric-ness (I am an x86_64 user after all!). I do like having those links since it clearly and reliably shows what the user is getting into. I guess I picked i686 since for many people it is still "standard", while x86_64 is a sort of optional thing. I'll try thinking of a decent way of making it more neutral without cluttering things up. [[User:Emiralle|Emiralle]] 15:28, 20 October 2011 (EDT)
 
:::I agree about the i686 centric-ness (I am an x86_64 user after all!). I do like having those links since it clearly and reliably shows what the user is getting into. I guess I picked i686 since for many people it is still "standard", while x86_64 is a sort of optional thing. I'll try thinking of a decent way of making it more neutral without cluttering things up. [[User:Emiralle|Emiralle]] 15:28, 20 October 2011 (EDT)
 +
::::I took a first stab at cleaning up the i686/x86_64 balance issue in [[Beginners'_Guide#Select_packages]]. I added a link to [[Official Repositories]] core section, which might be useful and gets rid of the duplicate link. Then I modified the package database and group links to show both i686 and x86_64. I just realized I have no idea how easy this stuff is to follow for people using the Dual Architecture ISO since I've never tried it. [[User:Emiralle|Emiralle]] 19:22, 20 October 2011 (EDT)
  
 
===[https://wiki.archlinux.org/index.php/Openbox#Upgrading_to_Openbox_3.5 Openbox 3.5]===
 
===[https://wiki.archlinux.org/index.php/Openbox#Upgrading_to_Openbox_3.5 Openbox 3.5]===

Revision as of 23:22, 20 October 2011

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Is the wiki missing documentation for a popular software package or coverage of an important topic? Or, is existing content in need of correction, updating, or expansion? Write your requests below and share your ideas...

See ArchWiki:Reports to report questionable contributions. Please sign your edits and feel free to comment on others' requests.

General requests

Category:Request:Correction
Pages flagged with Template:Accuracy or Template:Out of date, indicating inaccurate or outdated content.
Category:Request:Deletion
Pages flagged with Template:Deletion, indicating irrelevant or unhelpful content.
Category:Request:Expansion
Pages flagged with Template:Expansion or Template:Poor writing, indicating incomplete or poorly-written content.
Category:Request:Merge
Pages flagged with Template:Merge, suggesting duplicate effort or overlapping scope.
Category:Request:Move
Pages flagged with Template:Moveto, suggesting misleading names.
Category:Request:Translation
Pages flagged with Template:Bad translation or Template:Translateme, indicating poor or incomplete translations.
Category:Stub
Pages flagged with Template:Stub, indicating incomplete content.
Category:Linkrot
Pages with dead or broken links. They should be replaced or repaired rather than removed unless they are unhelpful. ArchWiki:Linkrot has an automatically generated list of links that have been dead for over a week.

Fix problems with redirects

Note: Redirects shouldn't really point to other sites and ones that do sometimes erroneously show up on these pages.

Creation requests

Here, list requests for topics that you think should be covered on ArchWiki. If not obvious, explain why ArchWiki coverage is justified (rather than existing Wikipedia articles or other documentation). Furthermore, please consider researching and creating the initial article yourself (see Help:Editing for content creation help).

HOWTO: SAMBA PDC + LDAP

How to configure SAMBA PDC + LDAP in Arch Linux? (Moved from another page. Hokstein 19:57, 16 September 2007 (EDT))

Tripwire

Finding information on the install of this program already requires a bit of searching around the net, and then a variety of modifications to get it running correctly. It would be nice to have a good HowTo about the install and setup of Tripwire on Arch. The package is availabe in community.

It has since been removed from [community], it's in the AUR now. -- Karol 21:52, 29 August 2011 (EDT)

Modification requests

Here, list requests for correction or other modification of existing articles. Only systemic modifications that affect multiple articles should be included here. If a specific page needs modification, use that page's discussion or talk page instead and one of the #General requests templates.

module blacklisting

Blacklisting modules in rc.conf has been obsoleted and no longer works in initscripts 2011.06.1-1. All blacklisting instructions need to be changed to the following:

Template:File
Currently which is the main article the explains in general how to blacklist modules the modprobe way? I found Modprobe.conf, but it's less than a stub: what about adding the blacklist method there and linking it from the Beginners' Guide and from rc.conf? -- Kynikos 05:37, 2 June 2011 (EDT)
Sort of done. We can remove this tip in a while. Let's not cram too many things in the Beginners' Guide I think that a link to the modprobe.conf article is enough. -- Karol 07:29, 2 June 2011 (EDT)
Maybe we can also use Blacklisting as guide to balcklist modules(this page is linked to Udev), and put there a list of known modules that are used to be balcklisted, eg. net-pf-10 and pcspkr, so in this way we can also merge the relative guides(Disabling_IPv6, Disable_PC_Speaker_Beep) or in the Blacklisting or in the Modprobe.conf page.Those page are small so we can have a unique page, I think this could be better for the manteinment.(sorry for my bad english). Maveloth 07:55, 2 June 2011 (EDT)
Good idea for merging Blacklisting. About the other two articles I don't know, Disable_PC_Speaker_Beep has alternative methods that don't involve modprobe, so I wouldn't merge it, and for coherence I'd leave also Disabling_IPv6 alone. Of course all these articles should be linked to each other. -- Kynikos 16:47, 2 June 2011 (EDT)
Done merging it, it could use a bit of rewording though. thestinger 12:03, 3 June 2011 (EDT)
This request should be obsoleted by Help:Style, right? Closing. -- Kynikos 14:06, 20 October 2011 (EDT)

aur package installation

Installing packages from the AUR should be changed from specific AUR helper instructions to:

Install Template:Package AUR from the AUR.

What to do with such requests? Do we remove instructions how to wget, untar and makepkg -s? -- Karol 11:31, 1 June 2011 (EDT)
There are many ways of installing packages from the AUR (cower/curl/wget + makepkg, full AUR/pacman wrappers, etc.) and I don't think we should prefer one over the other. Even if there was an official AUR downloader (something like cower), people need to learn about the AUR before using it, such as the security implications. I maintain a nessus package, and the "source" can't be included via a link, so for cases like that it makes sense to give step-by-step instructions.
You only need to read the AUR page one time, so even for a new user giving step-by-step instructions isn't helpful beyond the first package they install. thestinger 11:57, 1 June 2011 (EDT)
That's what I wanted to hear <evil grin> -- Karol 12:28, 1 June 2011 (EDT)
Will be fulfilled by Help:Style, closing. -- Kynikos 14:09, 20 October 2011 (EDT)

net-tools -> iproute2

It's not really a big deal, but we should start changing commands like Template:Codeline and Template:Codeline to the equivalent iproute2 command. net-tools is dead upstream, and Arch has switched to using iproute2 for initscripts. net-tools isn't a dependency of anything in base, and isn't in the base group itself - we shouldn't assume it is installed anymore.

The new networking syntax in initscripts also only allows you to configure 1 interface. People have to use netcfg or another solution for complex situations, which might require further changes on the wiki.

thestinger 11:32, 8 June 2011 (EDT)

New Official ISO

Coming soon. We need some brave souls that will edit the Beginner's Guide etc. according to what will be on the ISO. -- Karol 11:28, 19 August 2011 (EDT)

A bit overdue, but I've gone through the installer in qemu and made a fair number of changes to the preface and installation sections, and just started out on post-installation. I started a couple of discussions on Talk:Beginners' Guide and Talk:Beginners' Guide/Post-Installation.
My review wasn't exhaustive because I didn't have the necessary manpower to follow and document all paths through the installer, and I'm far from infallible, so it would still be good for anyone to give it a quick glance for obvious blunders. | Emiralle 10:36, 13 October 2011 (EDT)
I've finally found the time to go through your changes, it looks a very good job ;)
Just to do some nitpicking, this edit is maybe too i686-centric, and the first link duplicates the one the was already there: does somebody have a good idea on rewording that text to include x86_64 references and remove the duplicate link?
About your discussions, I've replied to those in Talk:Beginners' Guide, but I still have to think of something for Talk:Beginners' Guide/Post-Installation#/etc/pacman.conf.
-- Kynikos 14:22, 20 October 2011 (EDT)
I agree about the i686 centric-ness (I am an x86_64 user after all!). I do like having those links since it clearly and reliably shows what the user is getting into. I guess I picked i686 since for many people it is still "standard", while x86_64 is a sort of optional thing. I'll try thinking of a decent way of making it more neutral without cluttering things up. Emiralle 15:28, 20 October 2011 (EDT)
I took a first stab at cleaning up the i686/x86_64 balance issue in Beginners'_Guide#Select_packages. I added a link to Official Repositories core section, which might be useful and gets rid of the duplicate link. Then I modified the package database and group links to show both i686 and x86_64. I just realized I have no idea how easy this stuff is to follow for people using the Dual Architecture ISO since I've never tried it. Emiralle 19:22, 20 October 2011 (EDT)

Openbox 3.5

There are some leftovers that e.g. refer to Template:Filename, instead of Template:Filename. -- Karol 04:08, 21 August 2011 (EDT)

Polish wiki

This is actually not a 'request', more like a question about mass-deleting.

The Polish wiki disappeared along with the forum etc. about a month ago and nobody knows wtf happened. The guy who was hosting and maintaining it disappeared as well w/o a word. A similar thing happened a couple years ago with another guy ... who months later reappeared in Germany or something - weird stuff.

Should I mark all Polish articles and categories for deletion? Some are already marked, others are empty or have a bunch of links to nonexistent wiki pages that were hosted on the external wiki. -- Karol 14:56, 29 August 2011 (EDT)

Sad news for the Polish wiki, if it somehow comes back online, somebody should consider asking the maintainers to allow users to download the whole database in order to make periodical backups.
If there are really no more useful Polish articles here, they could be deleted, unless you or somebody else want to re-enable the _(Polski) suffix in Template:i18n and re-translate at least the most important pages from scratch.
-- Kynikos 05:40, 31 August 2011 (EDT)
You can get some of it back from here, but of course just the content and not the markup. -- thestinger 15:44, 8 September 2011 (EDT)
Thanks, Thestinger, but this is the old ex-wiki, the new Archlinux site didn't have a hyphen in the name: http://wiki.archlinux.pl. The old wiki is too outdated to be of much use, it says 2009.08 is the latest official release etc.
We got some pages off the Google cache but somebody has to maintain and update the wiki and nobody stepped up. -- Karol 16:45, 8 September 2011 (EDT)

AUR went https

The 'Package AUR' template is already using https, but there are tons of links that need to be fixed. -- Karol 22:36, 29 August 2011 (EDT)

This bug got fixed so it's a lot better now. -- Karol 13:53, 7 September 2011 (EDT)
Help:Style will deprecate direct links to aur packages in favour of Template:AUR, do we keep this request open? -- Kynikos 14:28, 20 October 2011 (EDT)
I think we should close requests when they're done i.e. when all the links to the AUR use https. Will there be some kind of automagick conversion from direct links to the new template? -- Karol 14:48, 20 October 2011 (EDT)
A bot and regexp substitutions may be able to do the trick.
Do you want to reopen also the other discussions I've just closed on this page for more or less the same reason? (Just look at the history for reference, I'm too lazy to link them here).
-- Kynikos 16:06, 20 October 2011 (EDT)

<tt> is deprecated in HTML 5

See this page. It has been suggested we remove this tag and use Template:Codeline instead. -- Karol 00:08, 1 September 2011 (EDT)

If only there was somebody who could configure a bot for these kind of jobs... This wiki is all about computers, and programming, and many more abstruse things, and we're still performing these jobs by hand, like our fathers used to do in the old days? XD (EDIT: see Wikipedia:Wikipedia:Bot_requests and related) -- Kynikos 06:14, 3 September 2011 (EDT)
A bot would be godsend. Let me see: "Dear Santa ..."
In the past you had to retype the whole thing on the typewriter, you couldn't just do hundreds small changes every now and then ;P -- Karol 11:22, 3 September 2011 (EDT)
Eheh, but, more seriously (and I don't know if it's worth to start a separate discussion for this), what if we really made a proper section (or an article) where users can request bot operations, and where other users can provide PHP, Python... scripts (I don't know what language wiki bots speak) so that wiki admins just have to feed the bot with it and let it go? For example, in this situation we could write a PHP function that takes a multiline text, replaces <tt> with Codeline using regexp substitutions, and returns the new text: I'm quite sure that what would remain to do would be calling that function from the bot, which of course has the ability of getting every article text and writing it back. -- Kynikos 12:28, 3 September 2011 (EDT)
EDIT: Bot info now at User:Strcat.
I'm going to try out a few things on my user page like tagging dead links with a template, replacing <tt> with codeline, etc.
thestinger 22:04, 3 September 2011 (EDT)
Ran it on a few articles and it works fine (tt -> codeline), going to ask for a bot tag before doing more though. thestinger 23:01, 3 September 2011 (EDT)
It needs to be smart enough to escape strings containing = or | with <nowiki></nowiki> tags. See PHP James Eder 23:23, 3 September 2011 (EDT)
Escaping those will work most of the time but there are a bunch of cases where templates or markup like [[link|text]] are used inside <tt>. The bot can show a diff and ask for confirmation each time, so I'll just check for stuff like that each time and fix the few articles doing crazy stuff like this manually (rather than trying to use regex to parse Wiki markup :P). thestinger 23:46, 3 September 2011 (EDT)
Another alternative is using {{Subst:Codeline|text}} when = or | appear in the text, but that's not ideal. thestinger 23:58, 3 September 2011 (EDT)
Perhaps you can make it automatic at least for for the trivial cases that lack craziness. Anyway, keep up the good work. James Eder 00:58, 4 September 2011 (EDT)
Good job Thestinger, you could also consider using {{Codeline|1=text}} to escape = and | (EDIT: works only with =, but I think pipes are less frequent than equals; another alternative is replacing them with html entities). -- Kynikos 07:40, 4 September 2011 (EDT)
Template:Codeline turns out to be the only viable solution in some situations. For example, it seems to be the only way to have the following template usage parsed correctly by the wiki software:
Note: A note with a URL containing an equal sign: http://example.com?url_has_equal_sign=true
You cannot use <nowiki> tags without also breaking the link behavior. We should probably document this in our Wiki help pages somewhere. It is easy enough to run into but not necessarily obvious to fix. James Eder 14:54, 6 September 2011 (EDT)
Found it documented here: Help:Template. I wonder if it should be mentioned in other pages as well. James Eder 15:28, 6 September 2011 (EDT)
1= works great! I just have the bot recheck the pages for '{{{' now after changing them for so I can manually fix any breakage. thestinger 16:34, 6 September 2011 (EDT)

This is now finished for every category on this page (should be all the english content categories). thestinger 17:30, 6 September 2011 (EDT)

Are you going to periodically unleash the bot to fix e.g. this or should we fix such edits manually as they appear? -- Karol 11:11, 1 October 2011 (EDT)
The bot can watch the recent changes list, so I'll set that up at some point. I ran it recursively over Category:English, and there were a lot of uncategorized pages/categories (mostly fixed now) so some pages were missed on that run anyway. -- thestinger 22:12, 1 October 2011 (EDT)

CLI template usage

I apologize if this has been covered, but I recently noticed that Emiralle added the CLI template to the During Arch Linux installation section of the GRUB2 article. Although this introduced an inconsistency to the article, I'm more concerned about whether it should be used at all. Personally, it seems like excessive style that isn't functional. I realize most users (including myself) use a dark terminal scene, but that doesn't mean it's appropriate for the Wiki. The constant switching between normal text (black/white) and the CLI template (white/black) is difficult to read and, at least for me, strains the eyes. Also, for the sake of consistency, only one standard should be used. ~ Filam 10:47, 8 September 2011 (EDT)

Pointone and Kynikos have some ideas about templates. I agree that the light - dark switching is bad. It would be cool if you could apply user styles (e.g. through user.css) to our wiki -- Karol 11:05, 8 September 2011 (EDT)
Regarding the inconsistency: my intent was to complete the rest of the article, but I didn't get to it last night. As for the style itself, what I like about it is how it more clearly distinguishes between console input and other boxes such as code or file manipulations. I think some of the slightly darker cyan options on Pointone and Kynikos's user pages linked above would be a good compromise. --Emiralle 12:30, 8 September 2011 (EDT)
We once had a discussion about the Cli template. -- Karol 12:53, 8 September 2011 (EDT)
I didn't mean to pick on your contribution Emiralle, formating is really a thankless endeavor and I'm glad you're contributing. Unfortunately, there are other articles like CUPS that aren't consistent. I agree that it's important to distinguish CLI text, but I'd prefer a more basic color scheme, and hopefully let users define there own scheme as Karol mentioned. I'd certainly prefer the darker cyan on Pointone and Kynikos's pages. Although, discussion of the color scheme should continue here. Also, thanks for the links Karol, I'll have to check them out later. ~ Filam 15:27, 8 September 2011 (EDT)
Well, Firefox and Chrome users who want to apply permanently a custom css to 3rd party websites can consider using the Stylish add-on. -- Kynikos 05:05, 9 September 2011 (EDT)
This request will be solved by the enforcement of Help:Style, closing. -- Kynikos 14:33, 20 October 2011 (EDT)

Category Virtualization and Category Emulators (English)

As you can see by my last edited page I'm tryng to allign the Italian category to the new English categorization, so I was going to change some peges and I notice that Category:Virtualization isn't localized as the others (for example: Category:Emulators (English)), do you think to localize this category or it will be removed an moved the pages to Category:Emulators (English)? Maveloth 08:34, 25 September 2011 (EDT)

A related discussion was started in ArchWiki:Reports#Category:Virtualization, my opinion on those categories is expressed there. For the purpose of reorganizing Italian categories you could just create a (temporary) Category:Virtualization (Italiano) until a decision on its fate is made. -- Kynikos 09:45, 25 September 2011 (EDT)
Ok, I'll create the category as you suggest. And I also think that the two categories could be merged into one due to similar(not same) subject.Maveloth 10:08, 25 September 2011 (EDT)
About the move to Category:Virtualization and Emulation (English) these should be all the i18n categories involved:

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

-- Kynikos 06:16, 16 October 2011 (EDT)
I like the idea of a combined Category:Virtualization and Emulation (English) so long as someone smart eventually writes a good overview to clarify the different types of software included. Emiralle 15:01, 16 October 2011 (EDT)

KVM categorized as Kernel (English)

This type of virtualization is strictly connected to kernel modules so I think this could also be in Category:Kernel (English). Maveloth 08:34, 25 September 2011 (EDT)

DeveloperWiki

Many pages are out of date and I can't even flag them out of date. Should users be warned that pages in this "category" may be really old and abandoned? -- Karol 09:19, 8 October 2011 (EDT)

Perhaps we can create a special template to be included at the top of every article in that category? -- Kynikos 13:41, 8 October 2011 (EDT)

LXDE

Installing the whole group with Template:Codeline doesn't install pcmanfm as it has been dropped to AUR. Should we post notes in English on non-English articles warning users that they need to perform an extra step and that pcmanfm is no longer in lxde group or do we just flag these articles out of date? -- Karol 17:51, 9 October 2011 (EDT)

One of the TUs (angvp) sent an email to aur-general with a list of packages they have orphaned which will move to the AUR if no one else wants to maintain them. It includes a few more lxde packages:
  • lxappearance
  • lxdm
  • lxlauncher
  • lxpanel
  • lxsession
  • lxtask
  • lxterminal
I think we should wait a few days to see what happens with these packages before making the changes. thestinger 18:04, 9 October 2011 (EDT)
You're of course right, I even bookmarked that thread to read it later, but haven't got to it before posting this request. Good catch ... as always :-) -- Karol 19:09, 9 October 2011 (EDT)
Barthalion became a TU and moved pcmanfm and libfm back to [community]. -- Karol 11:21, 17 October 2011 (EDT)

Remove -f short option for --force

It's not live yet [1] but will force some changes - is it bot-able or do we have to comb the wiki by hand? -- Karol 14:13, 19 October 2011 (EDT)

Uh I see, well, searching "pacman -Sf" and "pacman -Uf" doesn't give many results, however a regexp'd bot search with something like "pacman -[A-Za-z]*f" would catch more complex combinations and also possible existing mistakes. -- Kynikos 19:23, 19 October 2011 (EDT)

ck-launch-session dbus-launch and friends

Help:Style#Hypertext_metaphor taken to extreme: while searching for some hints on the exec ck-launch-session dbus-launch yourwm thing, I found myself tracking a piece of referenced info that has fallen victim to some daisy-chain mania.

Fluxbox tells you to check Xinitrc: "See Xinitrc for more details." Once there you learn that it has something to do with Policykit ... or Xfce, as you're told to "See also the notes of Xfce#Manually for more details.". Let's see what's on PolicyKit's page first. "Please note: to correct issues with automount and shutdown, please check the ConsoleKit page."" ConsoleKit was a disappointment for me, seems the princess is in another castle. Let's see that Xfce article mentioned earlier. Indeed, Xfce#Manually seems to have the most info about the issue, but not by much.

Unfortunately we don't have tools to see such "double-redirects" and lacking expertise in this particular issue is definitely a factor. Can someone please untangle this mess? -- Karol 16:37, 19 October 2011 (EDT)

AUR changing paths to PKGBUILDs

We recently hit the 32k subdirectories limit due to great number of packages in the AUR and it has been decided that the packages are going to be divided according to the first two letters of their name e.g. Xlayout goes to 'xl' subdirectory and the path to its PKGBUILD will change to https://aur.archlinux.org/packages/xl/xlayout/PKGBUILD. This move caused the old links to go 404 and now they appear on our ArchWiki:Linkrot page. I think instead of fixing the links we should generally remove sections like this one. -- Karol 15:43, 20 October 2011 (EDT)

Bot requests

Here, list requests for repetitive, systemic modifications to a series of existing articles to be performed by a wiki bot.

Moving pages

Can we have a bot that will move non-English pages and fix i18n links when the English page gets moved/renamed? SSH -> Secure Shell and Cpufrequtils -> CPU Frequency Scaling and the recent examples. -- Karol 10:47, 8 September 2011 (EDT)

Interlanguage links

[moved from Help talk:Style#i18n links -- Kynikos 18:35, 22 September 2011 (EDT)]

Should we add links to external wikis just to the English article or to every one: Arch_User_Repository_(Српски) has the link to the French wiki, Thestinger also started adding such links to non-English articles. -- Karol 19:25, 1 September 2011 (EDT)

Of course adding external links to all articles would be the ideal situation, but it would take quite a lot of bravery, to check every translation of every article... Maybe it would be the perfect work for a learned bot. -- Kynikos 04:48, 2 September 2011 (EDT)
Adding the interwiki links to articles on other wikis is easy and there's already a script for it (for example, if the English wiki has links to German and French and neither of those wikis have interlanguage links, it can add English and German links to the French article, etc.). Dealing with i18n pages here seems like it should be easy (just need to add all the potential language tags to the end of the English article title to look for the pages) so I'll try editing the script later to get it to work with our i18n conventions. thestinger 18:45, 3 October 2011 (EDT)
How does it handle the (very rare) cases where, for example, the article "A (aa)" (title is "A", language is "aa") has an interlanguage link "[[cc:title1]]", and the article "A (bb)" has an interlanguage link "[[cc:title2]]" (same language but different article)? An experiment could be interesting :) -- Kynikos 05:14, 4 October 2011 (EDT)

Contractions

Can the bot change e.g. 'don't' to 'do not'? You can try on GTK article. -- Karol 06:22, 3 October 2011 (EDT)

I think a simple replacement of " don't " with " do not " and " Don't " with " Do not " would work (note the spaces before and after). The same thing could be done with other contractions. This would also replace it in command outputs, quotes, etc. (not really a big deal I guess...), so I could either ignore that problem or run it in the semi-automated mode where it shows a diff and asks for confirmation each time (for now, I'll do this). thestinger 18:27, 3 October 2011 (EDT)
Unfortunately I think that it will never be possible to fully automate the conversion of "*'s" contractions. In particular, "it's" could also be a misspelled "its". -- Kynikos 05:21, 4 October 2011 (EDT)