text:
Wiktionary:Bots

A “bot” is a computer-controlled process that interacts with and edits the wiki, much like human users do, but in an automated fashion, typically in order to perform repetitive editing tasks. A bot’s editing happens much faster, and can easily flood the Special:Recentchanges page. A bot that runs amok could badly damage the wiki. For these reasons, bot usage is regulated. A new bot must be approved by the community, and should be run under a separate account, which should have the “bot flag” set. This flag enables users to hide the bot’s edits from Recent Changes.

In the past, bot usage on the English Wiktionary has been somewhat discouraged. Acceptance for their use is growing, but their usage here remains somewhat different from on the other Wikimedia projects. Even if you already understand the Wikipedia bot policy, please read the rest of this page to understand how bot usage differs here.

Policy
Wiktionary’s bot policy is based on, but is somewhat different from, the Wikipedia bot policy. If you have not already read Wikipedia’s bot policy, please do so now.

Like Wikipedia, Wiktionary requires that bots be approved in advance. This approval is for two reasons:

 * 1) To ensure that the bot software is properly written; to give interested bystanders an opportunity to review the code if necessary.
 * 2) To ensure that the bot owner is someone who can be expected to run the bot responsibly.

There are several facets of point 2. We expect that a bot owner will run a bot carefully so that it does not run amok. We expect that a bot owner will clean up after the bot if it does run amok or if it has made edits which the community decides in retrospect were unwarranted. Most importantly, we expect that a bot owner will use a bot to perform only those edits which there certainly is or would be good consensus for.

Because a bot can make so many difficult-to-undo changes in such a short time, it is important to be far more cautious when running a bot to perform edits than it is when performing ordinary edits manually. When you request permission to run a bot, you are effectively making several promises:

 * 1) I will use the bot to perform only such edits as I would, in good conscience, perform manually myself, except that
 * 2) I will not “be bold” with the bot, and specifically, before giving the bot a task to do,
 * 3) I will ask around for consensus, perhaps at the Beer parlour, or
 * 4) I will make sure that the task is so innocuous that no one could possibly object. Finally, if I or the bot should happen to make a mistake,
 * 5) I will stop the bot at once if any objections are raised to a task it’s performing, and not restart it until there’s positive consensus, and
 * 6) I will undo (perhaps with the same or another bot) any and all damage inadvertently caused by my bot, and any edits which consensus decides were unwanted.

Please be sure you are willing to work in this consensus-building mode, and to undo changes performed by your bot if necessary, before embarking on a plan to set up a new bot.

Process
If you think you have a task likely to be done much more easily by a bot, try using Pywikibot under your own account and see if it helps. Only if you’ve made sure that it will significantly help getting the task done, create an additional account for your bot tasks. The bot account’s name should contain your own username, and an indication of the kind of tasks the bot will be performing. Create links from the bot account’s user page to your own user page, and preferably vice versa as well.

Then, do a test run (under the bot account) on some 10–50 entries until you’re certain everything goes well (bots with a single function, like interwiki, should not run more than 25 edits). If the edits are minor (as most bot-performed tasks should be), please mark the edits as minor so that they do not swamp the Recent Changes list.

If all goes well, post a request for bot status at the votes page. Clearly state:
 * 1) Your user name,
 * 2) The proposed bot user name,
 * 3) The bot software you’ll be using, with pointers to its source and documentation if it’s not standard, and
 * 4) An indication of the task or tasks you’ll be performing with the bot.

It is important to note that bot accounts are not approved in isolation; the community is really approving the combination of all four of the above elements. This is a trust-building exercise: the community needs to be assured that the new bot will be used only for good, and that someone else will not ever be stuck cleaning up huge amounts of damage caused by a carelessly-run bot.

Please be as specific as possible in your indication of the task(s) which the bot will be performing. In the past Wiktionary has had a strict policy of one task per bot. That policy is being relaxed, but it is still important to have a clear idea of what sorts of thing a new bot will be doing. A task statement of “any sweeping bulk edit I feel like” is unlikely to be approved.

Also, make sure you understand the ways in which Wiktionary editing differs from, say, Wikipedia’s. Wiktionary pages are more structured than Wikipedia’s, and your bot must respect this. (Indeed, bots are one tool Wiktionary uses in an attempt to achieve and unify its structure.) You can’t necessarily expect to make some change to just a small subset of Wiktionary’s pages—if it’s to an aspect which ought to be consistent across the project, you and your bot must be prepared to edit some significant fraction of the pages in the project, and to convince the community that such a sweeping change is justified.

If and when consensus in the Beer parlour discussion about your new bot account is reached, you can ask a Wiktionary Bureaucrat to set the bot flag. Then, you’re free to use the bot to perform all of its approved tasks. Remember, however, to limit the rate at which it makes changes, to avoid placing undue load on the Wikimedia servers. (See Wikipedia:Bots for more information on the logistical aspects of running a bot.) Also, if you think of new tasks for your bot to do, remember to engage the community first in discussion to make sure there’s consensus, before making any sweeping new changes with your bot.

Technical advice
Commonly accepted bot functions from pywikipediabot:
 * pagefromfile.py
 * redirect.py
 * replace.py
 * template.py
 * category.py

Sample user-config.py file: Remember that a well-run bot is careful to:
 * limit its edits to a rate of one or just a few per minute
 * possibly limit its rate of editing further during peak periods
 * slow or stop its editing if it receives a Wikimedia server overload page
 * stop its editing if it is blocked by an administrator
 * (optionally) stop its editing if it receives a message on its talk page

title: Wiktionary:Bots


text:
ice bucket

Noun

 * 1) An often insulated container for holding ice cubes.
 * 2)  A pod or similar device containing a person in cryosleep.

Derived terms

 * ice bucket challenge

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: ice bucket


text:
ice bag

Etymology
. The second sense is possibly a calque of a Philippine language.

Noun

 * 1) A waterproof bag with a wide-mouthed stopper designed to hold ice, for service as an ice pack.
 * 2)  A thin plastic bag, of varying sizes, used primarily for freezing water to be sold as ice.

Alternative forms

 * icebag

title: ice bag


text:
nasciturus rule

Etymology
From Roman law (Digest 1.5.7): "nasciturus pro iam nato habetur quotiens de commodo eius agitur".

Proper noun

 * 1)  The rule stating that an unborn child, if subsequently born alive, is considered as already in existence whenever it is to its own advantage.
 * 2) * ROAD ACCIDENT FUND v MTATI 2005 (6) SA 215 (SCA)
 * The right of a child to sue for prenatal injuries is recognised in law, but the more difficult question is whether such an action should be allowed by using the nasciturus rule or by using the ordinary principles of the law of delict. The contention that the recognition of an action for prenatal injuries is logically impossible without the conferment of legal rights, and hence legal personality, upon the unborn child, as achieved by the nasciturus rule, is to be rejected.

title: nasciturus rule


text:
۱۰

Numeral

 * 1) 10 (ten),
 * previous:
 * next:

Numeral

 * 1) 10 (ten),
 * previous:
 * next:

title: ۱۰


text:
monitorial

Adjective

 * Of, or relating to monitors.
 * Of, or relating to an admonition; monitory.
 * 1)  Not secret and therefore printed in the Monitor.

Etymology
or.

title: monitorial


text:
iceberg lettuce

Etymology
Apparently originally a trade name.

Noun

 * 1) A lettuce cultivar  noted for its crunchiness; the most familiar of all lettuces sold in the United States.

Translations

 * Chinese:
 * Mandarin: 卷心萵苣
 * Dutch:
 * Esperanto: glacilaktuko
 * Finnish:
 * French: laitue iceberg
 * German:
 * Hungarian:
 * Italian: lattuga iceberg
 * Polish:
 * Portuguese: alface americana
 * Russian:
 * Spanish: lechuga iceberg
 * Swedish: isbergssallad
 * Turkish: göbek marul
 * Yiddish: אײַזבאַרג־שאַלאַטן

title: iceberg lettuce


text:
Talk:sigmoid

I'm confused. The greek letter given in the following line from this page:

(geometry) Curved in two directions, like the letter “S”, or the Greek “ς” (sigma).

looks more like a zeta to me. Can someone clarify?

 * Um.. zeta is ζ. ς is a sigma (specifically, the final sigma). —Muke Tever 22:21, 13 July 2006 (UTC)

title: Talk:sigmoid


text: 超级市场

title: 超级市场


text:
User:Robert Ullmann

My name is really Robert Ullmann. I am best known on the net as the author of a number of Internet RFCs. I live in Nairobi, Kenya.

I am a contributor to (and sysop on) Wiktionary and sometimes to Wikipedia (See w:User:Robert Ullmann)

I am the sysop for Wikamusi ya Kiswahili, the Swahili wikt, where I run a 'bot to add entries for other languages (called "Kompyuta" of course.)

Things I am working on:
 * Running User:AutoFormat
 * Also Interwicket and Tbot
 * Format of Han character entries
 * Learning Kiswahili and possibly some Kinyarwanda

Note that there is an "E-mail this user" link to the left.

Useful pages: I have various bits of Python code that analyze the wikt database in various ways.

 * (all subpages from here) (this is not complete because MW broke Special:PrefixIndex)

lists of things to be fixed or cleaned up in some way

 * Mismatched wikisyntax — entries with, [], and {} not matched correctly
 * Pronunciation exceptions — entries with pronunciations in variant formats
 * Han problems — list of format problems in the entries for individual Han characters
 * Not counted — list of pages with no wikilinks, so not counted in statistics

other useful reports

 * L2 — analysis of level 2 (language) headers
 * L3 — analysis of level 3 (POS) headers
 * L4-5 — analysis of headers at level 4 and 5
 * Language templates — analysis of the language code templates
 * Trans language — analysis of language names used in Translations sections
 * Contexts — analysis of context labels written with 's
 * Context labels — analysis of context label templates
 * Oldest redlinks — the "red links" from the oldest entries in the wikt
 * Missing — words used in definitions in the wikt that are not themselves headwords
 * Han — report on all of the entries for individual Han characters, with remaining format problems
 * Mandarin Pinyin — report on the pinyin references from the Han characters and updates to the pinyin syllable entries
 * Korean Yale — one time report by the bot when fixing 1000 or so errors in the Yale romanization in the Han entries
 * Chinese indexes — report of moving and re-checking the moves to the Index: namespace
 * Radicals — analysis of problems and report on 'bot adding radical numbers

These are run after XML dumps, and are current as of the dates shown in the reports. I don't try to run all of them each time (and the Korean Yale is a one-off). If something you want is out of date feel free to prod me.

It is fine to section edit the reports of problems in some lists (Missing, Oldest redlinks), but note the 'bot is going to overwrite your work at some point, which will of course incorporate what you fixed.

de:Benutzer:Robert Ullmann et:Kasutaja:Robert Ullmann el:Χρήστης:Robert Ullmann es:Usuario:Robert Ullmann it:Utente:Robert Ullmann rw:User:Robert Ullmann sw:Mtumiaji:Robert Ullmann lo:ຜູ້ໃຊ້:Robert Ullmann li:Gebroeker:Robert Ullmann pl:Wikipedysta:Robert Ullmann pt:Usuário:Robert Ullmann st:User:Robert Ullmann simple:User:Robert Ullmann ts:User:Robert Ullmann zh:User:Robert Ullmann

title: User:Robert Ullmann


text:
超級市場

Etymology
.

Noun

 * 1) supermarket

Usage notes
On the Chinese mainland, often refers to what would be considered a grocery or corner store in English-speaking countries.

title: 超級市場