From ArchWiki
Jump to navigation Jump to search

Auto update i18n pages

One idea come into my mind, it should be easy for your bot. Please check if you have time to implement.

For Chinese pages, there are many links to English pages and I think it should be linked to i18n page.

  1. If Page is end with (简体中文)
  2. Find all English page links in the page.
  3. For each English name, check if English name (简体中文) exist and make sure it is not flagged by Template:Translateme and Template:Translateme (简体中文).

Then: Change [[English name]] to [[English name (简体中文)|English name]].

Maybe not all translation teams want this feature, so it should be enable/disable by languages.

Hope I describe my thought clearly. Waiting for your feedback. --Fengchao (talk) 03:04, 16 March 2016 (UTC)

That sounds like a nice idea. I was actually thinking about some other things that could be done automatically on i18n pages, e.g. renaming if the English page has been recently renamed, adding the same categories etc. so I'll add your idea to the list of new features. -- Lahwaacz (talk) 21:18, 16 March 2016 (UTC)
Great, I will wating for those new features. --Fengchao (talk) 05:49, 17 March 2016 (UTC)

marking AUR links to pkgbase as broken link

hi, your bot marked a policydAUR link as broken (on the pkgbase policyd exists, but packages derived from it have different names. can you fix this please? thank you! Fordprefect (talk) 18:05, 24 April 2016 (UTC)

Hi, that's a general problem of the Template:AUR, which works only for packages and not pkgbases. For policydAUR the link does not work, it leads to a 404 page. I think that this behaviour is fine because users can install only packages and not pkgbases. -- Lahwaacz (talk) 18:53, 24 April 2016 (UTC)
Hm, I see the problem here. How could i implement a link to with the AUR annotation? Fordprefect (talk) 18:59, 24 April 2016 (UTC)
Ok fixed it: policydAUR Fordprefect (talk) 19:03, 24 April 2016 (UTC)
Hmm, that's not perfect either, because users expect such links to be packages that can be installed—on the other hand, pkgbases can't be installed. -- Lahwaacz (talk) 16:30, 16 July 2016 (UTC)

Removes title case, is this desired?

I noticed this bot just swept through and some links from title case to quasi-sentence case. This seems like incorrect behavior to me. In English writing, proper nouns are supposed to be capitalized, and technical writing has a lot of proper nouns. A bot can't possibly tell the difference between a proper noun like "[EFI System Partition]" and the same words as common nouns in "your [system partition]". Should we respond to edits we disagree with using "undo", or will the bot just make the same change on a second pass?

—This unsigned comment is by Bobpaul (talk) 15:17, 3 July 2018‎. Please sign your posts with ~~~~!

The ArchWiki does not use title case even in page titles, see the rule in Help:Style#Title. For links to pages, using the same capitalization as the target page is preferable (see also Help:Style#Hypertext metaphor). So, generally, the edits were correct, though if you have a specific controversial case we can debate it further. Also, the "(interactive)" suffix in the edit summaries means that a human sat behind a keyboard and pressed "yes" to confirm each change. -- Lahwaacz (talk) 15:31, 3 July 2018 (UTC)

Bot marking packages in test repo as not found.

The bot marked plasma-thunderbolt as not found on page Thunderbolt#Graphical_front-ends

But the package does exist in the kde-unstable repo. Is there anyway to workaround this?

Gnattu (talk) 08:05, 22 September 2019 (UTC)

How long does it usually take until they become stable packages? It is not often that new packages appear in the unstable repositories. -- Lahwaacz (talk) 18:58, 22 September 2019 (UTC)
It depends. For this package, I think it will become stable when the next major update for plasma lands(5.17) because it is required by the plasma-meta version 5.17. Gnattu (talk) 23:31, 22 September 2019 (UTC)