Jump to content

OKA/Instructions for editors

From Meta, a Wikimedia project coordination wiki
< OKA

This page contains the instructions provided to OKA grant recipients for translating Wikipedia (WP) articles. For transparency, it is publicly available. OKA editors are usually new, with no prior experience in editing Wikipedia.

Disclaimer to OKA editors: OKA is not affiliated with Wikimedia. This information is advice only—Wikipedia policies always take precedence. If any guidance here contradicts Wikimedia guidelines, flag it to your manager immediately.

Terminology

[edit]

In this document, the following terms are used:

  • Source language: The language you are translating from (e.g., Spanish).
  • Target language: The language you are translating into (e.g., English).
  • Translators Center: OKA's internal tool at https://translators.oka.wiki, where you claim articles, log your hours and submit your bills (see below).

These instructions focus on the English Wikipedia. For translations into other languages, refer to this page.

Overall guidelines

[edit]

Leverage LLM as a starting point

[edit]

Even for technical articles, LLMs such as Claude, DeepSeek, ChatGPT and Grok correctly translate >90% of text and handles most formatting. Your time should be focused on proofreading (especially specialized terms), finalizing formatting, adding internal links, and verifying sources.

Important:
Using Wikipedia's built-in translation tool is not recommended; it often breaks templates and requires significant rework.

Perfect is the enemy of good

[edit]

With millions of articles to translate, we prioritize impact. We may skip niche topics or publish articles that meet quality standards even if they aren't "perfect," provided the information is accurate. Wikipedia is collaborative; readers and other editors (or bots) will help flag or directly fix typos or minor errors over time.

Don’t wait until you know all the rules

[edit]

Wikipedia guidelines are vast, but the instructions here are sufficient for your first article. Standards vary between languages; always follow the rules of your target language (e.g., if translating into English, use English Wikipedia rules). While consistency with similar articles is ideal, 100% standardization is not required.

Don't always translate the whole article

[edit]

You are not required to replicate a source article's entire structure. Omit unsourced or poorly written sections. It is better to have a high-quality "stub" (very small article) than a long, unsourced one. You can also expand existing articles rather than creating new ones, or combine content from multiple languages.

Don't limit yourself to translations

[edit]

OKA values initiative. If you see errors or missing info on any page, fix it; if you'd like to write an article from scratch on a topic you're familiar with, go for it! Quality is more important than quantity; if improvements take extra time, simply be transparent with your manager (for example with a time note on the article in the Translators Center, see Notes, questions and flags).

Interact with the community

[edit]

Wikipedia is a collaborative encyclopedia where OKA represents only a small fraction of the community; you are encouraged to engage fully (e.g., through talk pages).

While interaction is generally optional, you must respond to messages on your talk page regarding your contributions by acknowledging legitimate concerns, taking corrective action, and explicitly stating that the issue will not be reproduced. Responding to automated or bot-generated messages remains at your discretion.

Your account is your own to use provided you follow Wikipedia guidelines and the law, but you must never imply that your posts represent the official position of OKA. Exercise caution in your communications, as personal opinions can easily be misinterpreted as the organization's formal stance.

Unsuccessful attempts to contact you, especially when linked to serious problems in your articles, can lead to permanent account suspension. If you have difficulty interpreting or responding to the message you received, contact your manager so they can advise you

Our prioritization principles

[edit]

We follow a value maximization principle based on 4 criteria:

  1. Quality: Prioritize well-written, comprehensive source articles.
  2. Gap: Prioritize articles that do not exist or are barely started in the target language.
  3. Value for society: Prioritize important topics or those likely to interest many readers.
  4. Personal interest: Writing about topics you enjoy is encouraged!
Note: Pageviews aren't the only indicator of value. Universal topics are preferred over those that are strictly regional (e.g., local celebrities).

Admins preselect articles and list them in the Find an article tab of the Translators Center (Priority 0 = highest). You may pick unlisted articles (add them with the Add articles tab, see Articles that are not on the list) or ignore priorities for topics of personal interest.

Do not translate priority 6+ articles without checking with a manager. These are often low priority because they may not meet the English WP requirements (e.g., may lack "notability" as per EN WP criteria, which differ from other languages). The Translators Center will not let you claim them until an admin has approved it: open the article and click Request admin approval.

Step-by-step guide

[edit]

Refer to the edit translations checklist for a summary. Before publishing your first article, ensure you have read the current chapter and the Tips and best practices section.

The ultimate reference for editing the English Wikipedia should be the Wikipedia:Manual of Style. It is very long, so we have summarized its key points in the Manual of style section at the bottom. You should read it once you have published your first articles, as it can take many hours to absorb. Learning continues even after the first month; it's okay to make mistakes.

Initial setup

[edit]

Configure your Wikipedia account

[edit]

Log in to Wikipedia. If you do not have an account yet, create one. This account belongs to you, not to OKA, so feel free to use any nickname or email address.

Before starting to edit, you should activate useful plugins.

  • Go to “Preferences” at the top right corner of the page.
  • Go to “Editing” and activate the following:
    • “Warn me when I leave an edit page with unsaved changes”
    • “Enable the editing toolbar”
  • Go to “Gadgets” and activate:
    • "HotCat"
    • "refToolbar"
Note
You can activate any other gadgets you want. These are simply the ones we recommend.

Disclose your affiliation with OKA

[edit]

To comply with Wikipedia's requirement to disclose paid contributions, you must add a sentence in your account mentioning that you receive financial grants from OKA.

To do that on the English Wikipedia, edit your user page by clicking here. In the edit box, paste the following:

{{paid|employer=OKA.wiki}}
I receive a small stipend from the Open Knowledge Association (OKA) to support my work on Wikipedia. However, the contributions I make are my own.

OKA is a non-profit organization that seeks to improve the coverage of content from non-anglophone countries, which is typically underrepresented in Wikipedia. More information about OKA can be found [[m:OKA|here]].

Then click “Publish changes”.

Important
You need to do this for each Wikipedia property you work on. For example, if you are translating articles from Spanish to English, you should add this disclosure to both the English and Spanish Wikipedia (with a disclosure in Spanish on Spanish Wikipedia).

Add yourself to the OKA impact dashboard

[edit]

Visit outreachdashboard.wmflabs.org - courses - OKA enroll and sign in with your Wikipedia account. We use this tool to track the impact of OKA grant recipients.

Become an autoconfirmed account

[edit]

To edit the English Wikipedia fully, you need to become an autoconfirmed account by meeting the following requirements:

  1. The account is at least 4 days old.
  2. You have made at least 10 edits on EN WP articles.
An easy way to reach the edits count is to use your personal sandbox to practice and publish changes as many times as necessary. You can also visit random Wikipedia articles, add links to related pages, and fix typos or add relevant categories at the bottom of the page.

Personalize your User Page

[edit]

In addition to adding the standard disclaimer, we encourage all editors to personalize their Wikipedia user pages. This helps humanize our presence in the community and shows that we are real people contributing with genuine interest and editorial freedom — not just anonymous "paid editors" or automatic robots.

You can include:

Note
This is optional and entirely up to you, but adding even a few lines can go a long way in improving how we’re perceived by others in the Wiki space.
Important
Please be mindful not to share any sensitive personal information, and never include content that could be harmful, discriminatory, or in violation of Wikipedia’s policies — including anything sexist, racist, homophobic, transphobic, or otherwise inappropriate.
Need inspiration? Check out Hellidy’s user page as an example.

Add yourself to the list of OKA editors

[edit]

Add your username to the list here in the “Active editors section” by pasting the following:

*[[:en:User:YOUR-USERNAME|YOUR-USERNAME]]

Then, click “Publish changes”.

Sign in to the Translators Center

[edit]

The OKA Translators Center is OKA's internal tool. You will use it to find and claim articles, log your hours, leave notes for your manager, record what you have published, and submit your monthly bill.

To start:

  1. Go to https://translators.oka.wiki. It opens on two lists anybody can see: the articles waiting to be translated, and the ones already published.
  2. Click Sign in at the top right and choose your @oka.wiki account (the one OKA created for you). A personal Gmail address will not work.
    The Translators Center's home page, with Sign in at the top right
  3. The first time you log in, the Translators Center will ask you to fill in your details (see below). Fill them in and click Save my details.
  4. You will arrive on the Find an article tab. Your name and OKA email address will display at the top of the page.
Reminder
You will stay signed in to that browser for 30 days after your last visit. If you share your computer, click Resources > Sign out when you're finished for the day.

Your details
[edit]

The first time you sign in to the Translators Center, your record is created.

You will be asked to provide your first and last name, your Wikipedia username (the account from the step above), a personal email address, your gender, date of birth, nationalities, country of residence, address and phone number.

Your name and Wikipedia username are shown to the team; everything else is seen only by you and OKA's finance team.

Tip
To change your details later, click Resources > My details.
  • Payment details

Your payment details will be requested separately, before your first bill. Complete this step before your first bill arrives to avoid any delays.

For more on how to fill out your payment details, go to the corresponding section (see below).

Translators Center structure and functions
[edit]
Tab What it is for
Find an article The list of articles OKA wants translated. Open one to read its notes and claim it.
My work The timer, manual time entries, the articles you hold, and your recent time entries.
Completed Every finished article (yours and everyone else's), with its published link and status.
Add articles Adding articles that are not on the list yet, such as red links.
Submitting bills Your monthly bill, how you want to be paid, and your past bills.
Translators The team directory. Click a name to see what that person holds and has published.
Analytics Charts of OKA's published work, and of your own hours and articles.
  • Notifications and resources

At the top right of the Translators Center:

- Notifications (the bell icon 🔔): These include notes on your articles, questions from a manager, and decisions or payments on your bills. You will also receive these messages via email.

- Resources: displays a list of useful links. These include links to this page, OKA instructions, a publication checklist, and OKA's compensation and billing document. You can also access your details and sign out from the platform.

Tip
Hover over a tab heading in the Translators Center to see what that tab is for.

Article selection

[edit]

Pick an article to translate

[edit]

In the Translators Center, open the Find an article tab.

  1. Narrow the list with the filters at the top: From language (your source language), Into language (your target language), Type, Priority and Category, or type part of a title in Filter as you type (see Finding articles in the Translators Center). By default the list shows priorities 0–3, and hides articles that someone has already taken and articles that need admin approval.
    The Find an article tab, filtered by source and target language
  2. If you don't have a preference for a specific article, you can pick the first one.
  3. Click the article's row to open its page. (Clicking the title itself opens the source article on Wikipedia.)
  4. Read the Before you start box, if there is one, and the Notes at the bottom of the page (see the tip below).
  5. Check the languages, the type and the title at the top of the page. If one of them is wrong (for example the target language), click it to correct it.
  6. Click Claim this article. If a warning asks you to confirm, first tick I have read the note above and am comfortable taking this on.
    An article's page in the Translators Center: warnings, the Claim this article button and the notes
  7. The article is now yours: its status becomes “In progress” and it appears in My work.

Before you start translating, do the checks below. If you change your mind about an article, open it and click Release to put it back on the list. An article that you have held for more than 30 days without finishing it is marked stalled: finish it, release it, or add a note saying why it is taking longer.

Always read and address the Notes on the article and the warnings under Before you start. They sometimes contain information such as:
  • Lack of sources - you should check and add more references
  • Red link from another article - you should check if the red link turned blue and fix if not
  • Technical terms warning - only pick this articles if you are familiar with the area
  • Controversial information - understand the situation, reference information and improve the writing as needed
A warning that says Needs admin approval before you start (for example on priority 6+ articles) means that you cannot claim the article yet: click Request admin approval and say why you want to take it on.
Some articles are bundled together because they are similar, therefore there may be synergies if they are all translated by the same person. Claiming one of them claims them all, and each one leaves the bundle when it is finished.

Notes, questions and flags

[edit]

Every article in the Translators Center has a Notes thread at the bottom of its page, shared by you, your manager and the admins.

To add a note:

  1. Open the article (from Find an article or My work).
  2. Under Add a note, choose the kind of note:
    • Note: anything worth recording about the article.
    • Time note (T/N): why the article is taking longer than expected (for example, many sources to find).
    • Source concern: a problem with the sources.
    • Quality concern: a problem with the quality of the article.
  3. Write the note and click Add note.

Whoever holds the article receives new notes by email and in their notifications. You can correct a typo in one of your own notes by clicking its text.

To raise something that needs a decision from a manager, click Flag to admin on the article's page, choose what the problem is (Similar article already exists, Poor quality source article, Priority looks wrong or Other), describe it under Details, and click Send flag. The Translators Center tells you who was notified, and the flag is kept in the article's notes.

For general questions about Wikipedia, use the Wiki questions and best practices chat space.

Check for similar articles in English

[edit]

You can do this through a Google search. If a similar article already exists in English Wikipedia, then the article should not be translated.

In that case, open the article in the Translators Center, click Flag to admin, choose Similar article already exists, paste the link to the existing English article under Details, and click Send flag. Then click Release if you had claimed it. A manager will review the article and take it off the list if needed. Do not click Mark published to report it: that counts the existing article as your work. If you already did, flag it the same way, and your manager will take it back off the list.

Sometimes, an equivalent article doesn't exist, but there could be similar ones with partial overlap. If the overlap is too great, the Wikipedia community will delete your article! If you have any doubt, please check with your manager or an admin.

If the article's “Type” is “Expand”, it means the article already exists in the target language but should be expanded with content from the source language. This is more complex, so not recommended for new translators with less experience in editing Wikipedia. Please refer to this section for more info about how to expand articles.

Check the quality of references

[edit]

Any fact or claim likely to be challenged must be supported by an inline citation to a reliable source. Consequently, you should avoid translating unsourced material unless it constitutes general common knowledge (e.g., 'the sky is blue') or undisputed foundational concepts within a specific field, such as basic quantum mechanics.

When you encounter an article with poor citations, you have 3 options:

  1. Translate only the sections or paragraphs with proper references
  2. Translate everything, but find additional sources for the unsourced parts
  3. Do not translate. In such cases, flag the article to your manager so that they can deprioritize it: click Flag to admin on the article's page, choose Poor quality source article, write "not enough sources" under Details, click Send flag, then click Release.

Check the quality of the writing

[edit]

If the article is poorly written, or too complex to translate (e.g., excessive use of localisms, overly flowery language), do not translate it. Flag the article to your manager so that they can deprioritize it: click Flag to admin, choose Poor quality source article, give the reason under Details (e.g., "poorly written"), click Send flag, then click Release.

Articles that are not on the list

[edit]

You may translate an article that is not on the list (see Our prioritization principles). Add it to the Translators Center first, so that your hours and your published article are recorded:

  1. Open the Add articles tab.
  2. Paste the address of the source article (for example https://es.wikipedia.org/wiki/...), one article per line. If you already know the title it should be published under, add it after a vertical bar: https://es.wikipedia.org/wiki/Gato | Cat.
  3. Choose the Type (Create for a new translation, Expand, Improve, or Write from scratch for an original article), and tick the language(s) under Translate into. Two languages means two separate articles on the list.
  4. Leave Claim these for me now ticked if you are going to work on the article yourself.
  5. Click Check and add.

The Translators Center checks every address against all the articles OKA has ever tracked, including published ones, and tells you which ones it added and which it skipped because they are already there. New articles get priority “TBD” until an admin reviews them. If the report says that an article was not claimed because there is a warning to read first, go to Find an article, set Priority to All, paste the article's address in Filter as you type, open it, read the warning and click Claim this article.

Articles you have already published: if you published an article without adding it first, tick I have already published these myself on the Add articles tab, then click Add as published by me. Each article goes on My work as published by you, so you can log your hours on it, and your manager reviews it as usual. Its published article is found from the source article’s links to other languages; if it is not found, add its published title after a vertical bar, as above. An article that is already on the Completed tab as yours is simply brought into My work.

Article setup

[edit]

Start time recording for your article

[edit]

You record your hours in the Translators Center, on the My work tab. Your hours are what your monthly bill is made of, so log all the time you work.

With the timer (recommended):

  1. Open My work. The Timer is at the top of the tab.
  2. Under Article, choose the article you are working on. Articles appear in this list once you have claimed them.
  3. Under Category, choose Translation (or Improvement for an Expand or Improve article). A short explanation of the category appears below it.
  4. Click Start. The time runs at the top of the Timer card.
    The timer running on an article, on the My work tab
  5. When you stop working, write a note if useful (e.g., Took longer than expected because…) and click Stop and save. Click Discard only if you started the timer by mistake.

By hand (if you forgot to start the timer, or worked offline):

  1. On My work, go to Manually enter time.
  2. Choose the Date, the Category and the Article (or type a description if there is no article).
  3. Type the Time in hours or in hours:minutes, for example 2.5, 0:40 or 40m. The line under the box shows how your entry was understood.
    Entering time by hand; the line under Time shows how the entry was read
  4. Click Save entry.
Notes
  • Log all your time on an article against that article: this is how admins see how long each article took. You don't need to type the article's name.
  • Minor edits that take less than an hour (such as Wikipedia site tasks) can be bundled together: click Minor edits instead on the timer, or enter them by hand in the Minor edits category.
  • Only one timer can run at a time. A timer that is left running is stopped automatically after 12 hours and saved as a 12-hour entry marked for review: correct it in Your time entries.
  • An entry of more than 10 hours entered by hand needs a note saying what it covered.
  • If you've spent a significantly larger amount of time on an article than expected, add a Time note (T/N) to the article (see Notes, questions and flags).

Correcting your time: at the bottom of My work, Your time entries lists your entries of the last three weeks, and older ones from the last three months that are not billed yet. Hours are shown as decimal hours, as in This week (0:07 entered by hand shows as 0.12); hover over a figure to see it in hours:minutes. Click any cell to correct it: the date, the article (move), the category, the hours or the note. Click delete to remove an entry. Once hours are on a submitted bill, you can still correct the note and which article they were for (until the bill is paid). To change their hours, date or category, or to delete them, withdraw the bill first (on Submitting bills, Withdraw it): you can do that until it is paid.

For time that is not spent on an article (training, onboarding, Wikimedia events, wellbeing), leave Article empty and describe it under Or describe it yourself. Choose the category that fits:

Category Use it for
Translation Translating: reading the source, writing the target, sourcing citations and fixing up the result, including proofreading your own article.
Improvement Working on an article that already exists in the target language (the Expand and Improve articles).
Review Reviewing somebody else's article (for example a second pair of eyes that another translator asked for). Your own proofreading is Translation.
Minor edits Wikipedia housekeeping of less than an hour, bundled into one entry.
Commons upload Finding, uploading and licensing images.
Management Managers only: prioritizing articles, reviewing other people's articles, onboarding.
Wikimedia event (editing) Editing at a Wikimedia event. Billed normally.
Wikimedia event (social/training) The non-editing parts of a Wikimedia event. Billed at 66% (see Wikimedia events).
Wellbeing Optional: a record of wellbeing time you took. To be paid for wellbeing hours, enter them on your bill instead (see Wellbeing hours).
Onboarding Your own onboarding and reading time. Keep it proportionate.
Other Anything else. Say what it was in the note.

Find the best fitting name in English

[edit]

In many cases, a literal translation might not be appropriate, so you need to check other sources to see if the same content exists under a different name in English.

In some cases, you may need to invest a bit of time before naming a page to find the right terminology. For example, “Edad Moderna” should be translated to “Early Modern Age” in English instead of “Modern Age”, because English historians have a different definition than Spanish historians of when the Modern Age ended.

The name of the page should be Anglicized, when an English name exists. For example, the English page of “Catedral de la Almudena” will be called “Almudena Cathedral”. If not possible, keep the local name.

Once you have decided on a title, record it in the Translators Center: on My work, click name it next to the article (or, on the article's page, click the dotted title after as:) and type the title. You can change it later if needed: the hours you have logged on the article, and a timer running on it, take the new title.

Tip
It's a good idea to check other language versions of the same article for inspiration. You may also want to check if a title has already been suggested for your target language. To do so, go to the "Tools" sidebar > Page information > Wikidata item ID, then click on the link to the right.
If you have any doubt about the title, check with other translators or your Manager or start a new question topic in Google Chats, as this a very important thing to get right.

Setting a page for your article

[edit]

The EN Wikipedia has a special set of rules for publishing articles, so, in order to set the space you’ll use to work on a new article and then submit it for review, follow these steps:

  • In your web browser, type the URL of the article you want to create, starting with “https://en.wikipedia.org/wiki/Draft:” followed by the name of the article you are working on (in the target language).
  • For example, if the article you picked is https://fr.wikipedia.org/wiki/Bataille_de_Smara_(1979) and the English name of the article you want to create is “Battle of Smara (1979)”, then you should type:
  • Click on “Create” or “Start the Draft:(...) page.” to open the “Visual editor” and start creating your article right under the title.
Tips
  • To save your progress, you can publish your draft even if its not finished. To access and edit your Draft’s page, simply type the URL you picked in the first step. You can check an alternative way to save your progress here.
  • If you would like to experiment, it’s also possible to work on a wikicode using the Sandbox environment. Publishing inside your Sandbox won’t have any effect on Wikipedia. It’s just a test environment.

Exception: first time creating an article

When you are a new Wikipedia user with a brand new account, you may see something slightly different from what was explained above. Go to "Article wizard" and click on "start creating", then follow the previous steps.

  • You should see something like the image below. Click “Start editing”.
  • It will lead you to the Source editor box with a few paragraphs of wikicode already written, which you can delete.

Exception: modify or delete redirects (when needed)

In some cases, when trying to access the page you want to create, you will get redirected to another article.

To access the page without being redirected, add "?redirect=no" at the end of the URL of the page with the redirect. For example:

https://en.wikipedia.org/wiki/usa?redirect=no

Redirects also have a page history. Click “View history” at the top right and check whether there was previously content that was deleted. Sometimes, redirects are remnants of deleted pages, so we should first try to understand why the previous page was deleted before recreating it.

Once you are certain it is okay to delete the redirect, you can start your draft as you would normally. The redirect will be deleted later once you publish your article.

Translate with LLMs

[edit]

At present, OKA uses Claude and ChatGPT (two "Large Language Models", i.e., LLMs) as our primary translation tools. The main benefit of LLMs is that, unlike traditional translation tools such as DeepL Translator, they work with wikicode. This allows it to handle most of the formatting, including finding corresponding wiki links, bolding, headers, etc.

From extensive testing we have found that Claude and ChatGPT generally produces better quality translations, so we recommend it as the primary tool. Grok used our preferred tool, and some editors prefer it because it tends to respond better to instructions and has a higher daily cap; however, it's writing style is poorer, so it's not recommended.

Gemini was also found to perform well, but often excessively summarizes results or omits content, instead of purely translating. DeepSeek performs well overall but has often issues with Wikipedia syntax.

We recommend you to experiment with various tools, and use what you feel most comfortable with.

Step by step

[edit]
Get your article's source code
[edit]

After claiming an article in the Translators Center, open the source article on Wikipedia (click its title in the Translators Center), go to "Source editing" (at the top right) and copy everything there, then paste it to a new google document (doc.new) for safekeeping. You can read more about how to save your progress correctly here.

Give the LLM a prompt
[edit]

AI models need prompts to come up with solutions. To do this:

  • Go to your selected LLM. Ensure you've selected the best model available to you at the moment of translation.
  • Input your prompt into the text box, for example: "Translate this Wikipedia article into English." (See the image below for an example.)
Important: Each model has a usage limit, that resets after a few hours. If you reach it, you can either:
  • Create a new account using your personal email address or any other email address to which you have access.
  • Try another of the LLMs listed above

Prompts you can use

  • General prompt
Translate this Wikipedia article into English. Adjust the formatting to meet the English Wikipedia conventions. Do not translate book and scientific work titles inside reference type templates. Do not modify ISBN or doi identifiers. Translate dates inside reference type templates into English conventions. Add and fulfill the "trans-title" parameter in reference type templates. Replace {{harvnp}} templates with {{sfn}}. Replace internal links with existing English Wikipedia equivalents. Insert the {{subst:submit}} template at the beginning of the article. Enclose the categories within the {{Draft categories}} template. Add a {{Short description}} that fits the article content. And return the full response in MediaWiki format. Do not add text that wasn't in the original article, and do not omit any paragraph of references.
  • Incomplete output
It's incomplete. Return with the rest of the article.
  • Other prompts (optional)
Don’t add internal links (red and blue links).
  • This prompt depends on your workflow. Some editors may prefer to have LLM add links. Others may prefer to add them manually.
Replace species names with their popular equivalents in [language] as listed in the iNaturalist database.
To consider
  • This prompt has been tested by OKA managers. Feel free to modify it after you've gained experience.
  • The use of the MediaWiki command tells LLMs to preserve line breaks and formatting elements.
  • This prompt was created for translations into English. For other languages, see the corresponding guide.
Translate your article
[edit]
  1. Copy the source code and paste it into the LLM below the initial prompt (use SHIFT + ENTER for a line break).
  2. Either click on the button in the lower right corner or press ENTER. The LLM will return the re-formatted code.
  3. Copy the translated code and paste it back into your Google doc (it is recommended that you paste it with CTRL + SHIFT + V to preserve the format).
  4. Open a new draft URL for your article and paste the translated code into it, in "Source editing" mode.
  5. Proofread the entire article (detailed below).
Important
  • Retranslate or double check terms as needed. You can use DeepL Translator for this.
  • Improve odd sounding sentences using DeepL Write, as described here.
  • Manually check each link, template, category, and reference to ensure they are correct.
  • Ensure there are no AI hallucinations! In rare cases, LLMs may completely invent content that's not in the original text. If you introduce AI hallucinations, your Wikipedia account risks being suspended
Tips
  • Feel free to remove unnecessary templates before translating if you are familiar with wikicode.
  • Consider splitting long articles into parts, if too big.
  • Make sure the code is complete before proofreading.
  • The tool assists, but it's not perfect. If it fails after a few tries, finish the work manually.

Infobox

[edit]

Adding the template

[edit]

Most articles have an infobox in the top-right corner. Since syntax varies between languages, you cannot simply copy-paste it from the source article. Instead, copy-paste one from a similar English Wikipedia article.

  • For example, for a TV series, find Floribella, click on “Edit” at the top right, click on the infobox, and copy it (CTRL + C)
  • Paste it into your new article (CTRL + V).
If an article only has an image box, you can just add one through the “Insert > Template” tools in the toolbar.

Alternative method to insert an infobox

  • To find the exact same infobox type, edit the original article and select its infobox using the visual editor.
  • Access the template’s page and switch the page language to English using the sidebar link.
  • Copy the code in the “Usage” section and paste it at the beginning of your article’s wikicode.

Filling the template

[edit]

Click on the infobox and select “Edit” in the popup. Map the information from the original article into the English fields.

It is ok to leave fields empty if there is no equivalent, provided you don't input incorrect info.

Check that no unknown parameters were added during translation; these can cause errors. Use the "Preview" button in Source mode to find errors like the one below:

The error is resolved after removing the unknown parameter. It is ok to keep unknown parameters are long as they correctly get displayed in the preview and don't cause an error.

Alt text

[edit]

Alternative text (or alt text) is text associated with an image that conveys the same essential information as the image. When an image is unavailable to the reader for whatever reason (images turned off in a web browser, a poor internet connection, or the use of a screen reader due to a visual impairment), alt text ensures that no information or functionality is lost.

In infoboxes, adding alt text to images, diagrams, and/or maps is very important. If an infobox is missing alt text, the article may be placed in specialized maintenance categories such as Category:Articles using infobox body of water without alt.

How to add alt text

  • Image: go to the "Image alternative text" field (if you can't find it, add it), then add the corresponding alt text.


  • Pushpin map: go to "Add undocumented parameter" and type the parameter "pushpin_map_alt", then add the corresponding alt text in the new field.


Note: Some infoboxes already have a parameter for map alt text (usually "map_alt"), so you don't need to create a new one.

Tips to write alt text

  • Alternative text should be short, usually 1-2 sentences.
  • Consider key elements instead of describing every little detail.
  • No need to say "image of" or "picture of" but do say if it's a logo, illustration, painting, or cartoon.
  • Don't duplicate text that's adjacent in the document or website.
  • End the alt text sentence with a period.

More on how to properly write alt text for wikipedia here.

Alt text examples

- A body of water surrounded by buildings and trees.
- A valley surrounded by trees with mountains in the background.
- A topographical map showing the location of Bardenas Canal in northern Spain.
- A map showing the location of Lake Tornow in Ruppin Switzerland, Brandenburg.

Main content

[edit]

After obtaining the fully translated article, as previously explained, you must edit and proofread it thoroughly before submitting it for publication.

Use the Visual editor for most of your editing. Only use “Edit source” when required, for example, if you need to use advanced syntax or when the visual editor has bugs. You can also use the Edit source feature if you need to access the wikicode of your page.

Do a read-through to make sure the translation makes sense, improving the English where needed.

First paragraph

[edit]
  • In the first paragraph of the article, bold the name of the article and its synonyms:


  • We don’t recommend using bolding anywhere else in the article. More information about the correct use of bold type can be found here.
  • Non-Latin characters (e.g. Chinese, Russian, Korean, etc.) should not be bolded or italicized.
  • If the concept is well know by its local, you should add it in parentheses, italicized. See example below:

Sections

[edit]

Apply section headings. Commonly used text formatting styles (sub-headings, preformatted text, block quotes) can be found in “Paragraph”

[edit]
  • Add internal wiki links where possible:
Tips
  • If you can't find the corresponding page in EN Wikipedia, it may be because the target language Wikipedia doesn't have an equivalent page, or because it's called something else.
  • To check, go to the original article, click on the appropriate link to go to the equivalent page in the original language Wikipedia, and check to see if the page has a version in the target language.


If the page doesn’t exist in the target language, you should add an internal link to it using the interlanguage link template. With this tool, your text will return with a red link and a small link to the original wiki article that already exists. For example, if you want to link the IT article Arnolfingi in an EN article, it’ll be shown like this:


Red links are important, because they help identify gaps in Wikipedia, and automatically become blue links when someone creates the page. Red links should almost always be followed by an interlanguage link template.

This template should not be used in citation templates, because it pollutes the citation metadata.

See also: OKA/Instructions for editors#Overlinking and underlinking

Other formatting
[edit]
  • Italicize any text that is not in English (e.g., untranslatable words, name of books, names of places, etc.) as long as it's written in Latin characters. Non-Latin characters (e.g. Chinese, Russian, Korean, etc.) should not be italicized or bolded. More information on the correct use of italic type can be found here.
  • Add images, templates, tables, and other elements manually, where needed, by using the “Insert” tool.

Tips
  • Don't copy elements from the source language to your English page, because it might not work and break your formatting. Instead, find the right template on Google or copy an element from another English article.
  • To find the name of an image: double click on it while in “Edit” mode, then copy the text on top of the caption including the format (jpg, .png, etc.). See an example below:


Transposing citations & references

[edit]

References section

[edit]

All articles must have a "References" section, because a key Wikipedia policy is that articles must be verifiable.

There's no general consensus on where it should go, other than at the bottom of the page after all the main content, but it's usually placed after any "Notes" and/or "See also" sections.


To add a "References" section to your page you must create it manually (as shown here), then add a references template.

There are many styles to add references and all of them are acceptable. However, the most common templates are:

<references/>
{{Reflist}}
Tip
If your reference list is too long and/or has too many redirection elements (e.g. Harvard citations), {{Reflist}} will automatically create a list of appropriate width. Alternatively, you can use {{Reflist|20em}} or {{Reflist|15em}} for a 2 or 3 columns reference list, respectively.

Add citations

[edit]

Add the citations and references that are present in the original article as long as they are relevant and still valid. If a fact or claim likely to be challenged isn't supported by an inline citation to a reliable source, then you should find a new source or remove that statement! In some cases, you may need to delete the whole section of the original article.

Always check that references are reputable and link to a valid URL or book. If the citation you translated isn't behind a paywall, you should also briefly check that it accurately supports the statement it's linked to.

If the page doesn't exist anymore, you can use WayBackMachine or archive.today to find archived pages, or look for new sources by doing a reverse search on Google.

On "Visual mode", click the "Cite" tool to manually add each reference according to type (see image below). To fill out the rest of the cite template, you should also follow the non-English references conventions as presented here.

For simple citations (e.g., webpages, books, etc.), the “Automatic” tool can save you a lot of time by automatically pre-formatting the citation based on a URL or ISBN number (example below). It doesn't always work, but it might give you a partial result, so it's worth trying.

If a source has an ISBN number, always ensure that it was published or reprinted after 1965. Otherwise you will get the error message "ISBN / Date incompatibility".

To avoid/resolve this, do one of the following:

  • Remove the ISBN altogether.
  • If the edition of the cited book was published after 1965, make sure that |date= or |year= has the correct publication year.
Do not publish articles with broken links if possible (e.g. errors 404 or 502). If you absolutely need to (i.e. if you can't find an archived version and/or a replacement reference), make sure to add the appropriate dead link tag.

Non-English sources

[edit]

If a source is in a language other than English, you must make that clear when adding it to your translated article. In Visual Mode, add the necessary fields to the template you want to use (e.g. Cite book) and fill them as follows, then complete the template with the rest of the available information from the original article.

Latin based languages (ES, FR, PT, etc.)

  • Title: original title if available; if not, leave it blank and disregard the warning pop-up.
  • Language: original language or its code. For example: "es" or "spanish", "pt" or "portuguese", etc.
  • Translated title: official English translation of the original title if available; if not, add your own translation.

Non-Latin based languages (RU, AR, JA, etc.)

  • Title: romanization of the original title if available; if not, leave it blank and disregard the warning pop-up.
  • Language: original language or its code. For example: "ru" or "russian", "ja" or "japanese", etc.
  • Script title: original title in its original language prefixed with the language's code. For example: ja:"title in Japanese" (without quotation marks).
  • Translated title: official English translation of the original title if available; if not, add your own translation.

It should look like this:

  • Surname, Name (2024). Tōkyō tawā 東京タワ [Tokyo Tower] (in Japanese) (1st ed.). Japan: Publisher. 
Notes
  • For citation templates that don't have the necessary fields, the codes trans-title= and script-title= can be added in source mode. You must do this only when strictly necessary; ask a manager to assist you if you're not familiar with Wikipedia's source code.
  • If the author, publisher, etc. is also in a non-Latin language, please add the romanization to the template. For example: 岸本 斉史 → Kishimoto, Masashi

Short citations

[edit]

You will sometimes encounter this type of citation:

These are short citations (e.g., Harvard style citations), which are one of the methods you can use when you need to reference the same item (book, journal, publication, etc.) several times. To add one to your article, follow these steps:

  • Go to the "Cite" tool, create a "Basic" citation, and insert a template inside by going to “Insert > Template”.
  • Find the template by its name, for example: "Harvtxt" for Harvard citations. Then add or insert.
  • Fill in the format of the template. Make sure to write only one item per field.

Tips:

  • For short citations to link to your bibliography, you will have to compose a "Bibliography" section manually.
  • Make sure that the author's name and year of publication match in both the template and the bibliography entry it targets (or add a reference if necessary).
  • Once you publish the article, you will be able to test the links and check if they redirect correctly. You can also use your sandbox to test this and any other template.
  • Another way to test these and any other template is by going to "Source editing" and activating "Preview".
  • For more types of short citation, you can go here, here, or here.

Bibliography

[edit]

Within Wikipedia, bibliographies are specialized lists of books, journals and other references important to the topic of the article you are creating. For example: Bibliography of classical guitar is a list of works important to the study of Classical guitar. Bibliographies may also be a listing of published works of an author.

To create a “Bibliography” section you will have to do it manually using templates such as "cite book" or "cite publication", one by one. To do this go to “Insert” > “Template” > cite book/publication/journal/etc. for each one of the items.

As with regular citations, you don’t need to translate the titles of books/journals/etc. Simply add a “Language” field within the template.

[edit]

This section often contains a lot of spam (e.g., people who try to insert their personal blog posts). You should only keep the external links that provide a clear added value to the reader (e.g., official website related to the page) and ignore everything else. If you have a doubt, it’s ok to just skip them, as they are usually not too important.

Explanatory notes

[edit]

This type of reference is used to add explanations, comments or other additional information relating to the main content but would make the text too long or awkward to read. They look like this:

To add a note to your article:

  • Go to the Cite tool > Manual, then select the “Basic” type of citation.
  • In the “Use this group” option type “note” (you can name it whatever you want but “note” is preferable). Then write the caption of your note in the blank box above and click Insert.
  • The note will show as a different set of references so you will have to create a new heading called "Notes" before the "References" section.
Tips
  • Add the code {{reflist|group=Note}} in the "Notes" section to visualize them there.
  • If you still can’t see the notes, change from Visual editing mode to Source editing then back to Visual.
  • Click here for more information on explanatory notes.

Adding more references

[edit]

Frequently, transposing all citations of the source article is not sufficient. This is because the requirements are not the same across Wikipedia languages: what may be considered adequately sourced in one language may not be another language. Therefore, a large part of the Wikipedia translation work consists in finding new sources to complement the existing ones.

The official policy for EN Wikipedia is to have “inline citations for any material challenged or likely to be challenged”. If your article doesn’t meet this requirement, it will likely be rejected when you submit it.

In practice, if a given paragraph has no in-line reference, it usually means that one should be added. The exception is the intro paragraph, which does not require these citations.

If after a reasonable amount of effort you cannot find a source, then you should delete the paragraph. If the information cannot be confirmed, then it’s ok not to translate it and to delete that paragraph or the unsourced statement. Do not spend too much time looking for sources; if it’s missing in the first place, it’s usually due to issues with the quality of the original article, not because of your work!

When adding or replacing sources,

  • Ensure they meet the requirements of reliable sources.
  • Also add them to the source article if you are translating from ES/PT. That way, you are not only improving the quality of the EN article, but also in the other Wikipedia.
Do not make significant changes to other Wikipedias unless you have disclosed your affiliation to OKA. For details on how to disclose your paid editing status in ES/PT Wikis, see Disclosing your affiliation with OKA.

Finding sources can be one of the most challenging parts of the work at OKA. If you do not feel yet comfortable with it, it is recommended that you pick articles that already have good sources and leave under sourced articles to more experienced OKA editors (in the Translators Center, articles known to be under-sourced carry a warning). If an article is particularly poorly sourced, please flag it to your manager (Flag to admin → Poor quality source article) so that we can deprioritize it.

Finalizing

[edit]
  • Add a short description. Each article should have a short description tag at the beginning. It is used in a few places, such as when searching for articles in the internal search bars (see screenshot below – the short description are the gray text):

If a short description already exists in the original article, you can translate it. Otherwise, write one yourself. You can find here guidelines and examples of how to write it.

Use this template:

{{Short description|ENTER TEXT HERE}}

If the article title is already sufficiently self-explanatory, no short description is needed. The tag is still needed, but you can put "none":

{{Short description|none}}
  • If the article is very small (e.g., 1-5 paragraphs), you should also add a “stub” template. To find the right template, it is easiest to search on Google, as each topic has a different code. For example, for articles about Churches in England, you would add {{England-church-stub}} at the bottom of the article.
  • Add relevant templates (Optional) by copy-pasting from other similar articles. For example, at the bottom of articles about the French revolution, you can usually find a large box that lists key articles about the French revolution, which you can simply paste in any article you write on this topic.
  • Check if there are any relevant actions needed in the article's “Notes” in the Translators Center and address them.

Creating Draft

[edit]

At any point, you can save your progress as “Draft”. Drafts are public, but they are not searchable so unless people specifically look for them, nobody will see your work in progress.

  • Click on “Publish page”.
  • Fill the "Edit summary" to briefly describe the changes you are making to the page. To satisfy Wikipedia's copyright and translation requirements, you have to fill the Edit summary box as follows whenever your edit contains translated content:

Translated from Portuguese:

Content in this edit is translated from the existing Portuguese Wikipedia article at [[:pt:EXACT NAME OF THE ORIGINAL ARTICLE]]; see its history for attribution.

Translated from Spanish:

Content in this edit is translated from the existing Spanish Wikipedia article at [[:es:EXACT NAME OF THE ORIGINAL ARTICLE]]; see its history for attribution.

For other languages, modify the text accordingly and use the corresponding language abbreviation (de, fr, it, ru, uk, zh, ja, nl, pl, sv, ar)

For example:

Remember
You should add this edit summary every time you add translated content into your Draft.
Important
Do not use this text in your edit summaries if they don't contain translations, but only small edits. E.g., if one of your edits is just about adding sources you found on the internet, you should not use this description. Instead, you can put something custom such as "Adding more sources"
  • Tick the box “Watch this page”, so that you can easily be informed of future edits to the page.
  • Click “Publish page”.
Make sure that you are publishing as draft! If you publish an incomplete article without the draft prefix, your account may be banned.

Once the draft is created

[edit]
  • Manually add the interwiki link at the bottom of the page, using this tag:
[[fr:NAME OF THE PAGE IN FR WIKI]]
  • Add categories at the bottom of the page by clicking on the “+” symbol (only visible if you have activated HotCat in the settings). It doesn’t need to be comprehensive, as there are usually many categories that would fit, but adding 2-10 categories on a page helps it gain in visibility.

Immediately after that, go to “Source editing” and wrap the Categories with the Draft categories template (because drafts are not supposed to have categories). It’ll have a similar look to this:

{{Draft categories|
[[Category:Star Wars characters]]
[[Category:Star Wars lists|Characters]]
[[Category:Lists of Disney characters]]
}}

Publishing

[edit]

You should only perform these steps once you have finalized your draft and are ready to submit it for review.

Create a Talk page

[edit]

Add a WikiProject banner shell and a translation tag at the top of the "Talk page" of your draft to indicate that you translated the article from a different Wikipedia:

  • Wikiproject banner shell
{{WikiProject banner shell|
{{WikiProject Intertranswiki/OKA}}
}}
  • Translation tag

Translated from Portuguese:

{{translated page|pt|SOURCE LANGUAGE NAME OF PAGE YOU TRANSLATED|small=no}}

Translated from Spanish:

{{translated page|es|SOURCE LANGUAGE NAME OF PAGE YOU TRANSLATED|small=no}}
Important

- If your contribution is an improvement or expansion (not a translation), include the parameter |category=expand inside the translation tag template

- For other languages, use the corresponding language code (de, fr, it, ru, uk, zh, jp, nl, pl, sv, ar, etc.)


To add both elements to the talk page, click on "Create source", copy-paste the codes one after the other, then replace the text on the translation tag with the correct information and the source language name of the article you translated.

This is how the Talk page will look once the tag and banner are in place:

If your Wikipedia username shows up right after the tag, click "Edit source" and delete it, then click "Publish". (Do not delete the tags, only your username and extra code).
The tags should be added at the top of the page, without any section header or signature, and after any preexistent Wikiproject banners. You can see an example of preexistent banners below:

Submit your Draft for AfC revision

[edit]

The EN wikipedia has a special process of publishing for paid editors. Instead of creating and publishing an article directly, it is mandatory to create it following the “Articles for Creation (AfC)” process.

  • Once the content and formatting is ready, and all the steps have been completed, add the code below to the top of your draft (remember to switch to the “Source editing” first). This way the community will be able to find your article and review it:
{{subst:submit}}
Be careful
Do not include the {{subst:submit}} tag in your draft until it is finalized, which would otherwise trigger a review

If you see a yellow box saying "Review waiting, please be patient", you have successfully submitted for review. Sometimes it only appears on “Source editing” using the “Preview” tool.

  • Record the submission in the Translators Center: open the article (from My work), click Mark submitted to AfC, paste the address of your draft (https://en.wikipedia.org/wiki/Draft:...) and click Confirm. The status becomes “Submitted in AfC” and the article moves to Waiting for AfC review on My work. Your manager then reviews the draft while it waits in AfC: they approve it, or ask you something (you receive it by email and as a note on the article; reply with a note on the article). Once your manager has approved it, it needs no further review after it is published. Once you get confirmation on your article and it is published, you may proceed with the next steps.
Important
  • Whether your article has been accepted or declined, you will receive a message on your user Talk page, so you should check your Talk page often.
  • Getting a review can take a while (up to 3 months), but your draft will be reviewed eventually.
  • If an editor add comments to your draft, respond in the draft’s Talk page by tagging the original reviewer. Do not respond in the draft’s page or in your own talk page.

After your article is approved

[edit]

Once your article is approved and published in the Mainspace via AfC, you’ll have to do some final steps.

  • Link the article to its source language version by clicking on “Add interlanguage links” on the “Tools” right side menu.
  • Remove the “Draft categories” {{Draft categories|...}} template that was wrapping the categories. Your code will look like this:
{{Draft categories|
[[Category:Star Wars characters]]
[[Category:Star Wars lists|Characters]]
[[Category:Lists of Disney characters]]
}}
  • Move the Talk page of your draft to mainspace (if it wasn’t done already).
If the Talk page already exists in the mainspace, ensure it contains the OKA template, and delete the “Draft talk” page. Deleting the “Draft talk” page is important so that it no longer shows up in the list of “OKA drafts for review”
  • Add links to other Wikipedia pages that redirect to your article.

For example, if you create a page on “Potato cooking”, then you would want the page for “Potato” to link to your “Potato cooking” page.

This helps your article gain visibility as well as it prevents the article from being tagged as “Orphan” by an administrator. You should make sure to have at least 2 other pages linking to yours (and ideally 3-4) to avoid the “Orphan” tag.

Also, you should do a quick search on Wikipedia to see if there are other pages from which it could be useful to list your article (e.g., if you create a page about a Spanish Castle, then it might be good to add the link to https://en.wikipedia.org/wiki/List_of_castles_in_Spain).

There are 3 main types of links to be added:

  • Regular links from within the paragraphs.
  • Links in the “See also” section at the bottom of the page.
Only add “See also” links to your articles when it is highly relevant to the page it is coming from. If your article is only tangentially related, then adding a link is a violation of the “See also” Wikipedia policy, which could lead to a ban of your account.

Example: One translator had created an article about a local church, then added a “see also” link from the “Organ pipe” article to that church. This was not value-adding for users, and led to a ban of the account.
  • “Main article” links for sub-headings (e.g., if you are publishing “History of Opera”, then the page “Opera” should have a “Main article” tag pointing to it in the “History” section). “Main article” tags can be created by adding the following tag to your source code
{{main|NAME OF THE PAGE YOU WANT TO LINK TO}}

You can also create them by inserting a template. Go to “Insert > Template”, type “Main” and fill out the template with the page you want to link.

When in place, the link to a main article should look like this:

Important
Make sure your page has at least one link from another article before marking it as "Published" in the Translators Center. You can check by going to the "Tools" side panel > "What links here". Note that talk pages, redirects, user pages, and other kinds of wiki pages don't count, only articles. Otherwise, you'll get an "orphan" tag.
Tip

If you’re having trouble finding related articles, you can:

- Enter the name of your article to Wikipedia’s search engine or to the find link tool, then link your article when relevant.
- Go to the source article > "What links here" tool (usually on the right or left sidebar of Wikipedia), which will show you all the articles that link to the source article. If they have an English equivalent, you can add a link to your article.


  • Mark the article as published in the Translators Center, and add its red links to the list at the same time:
    1. Open the article (from My work) and click Mark published.
    2. Under Published (mainspace) URL, paste the address of the live article (https://en.wikipedia.org/wiki/...).
    3. Under Red links in your new article (optional), paste the source-language address of each relevant red link, one per line. If you already know the title it should be published under, add it after a vertical bar: https://es.wikipedia.org/wiki/Gato | Cat.
    4. Click Confirm. The article moves to the Completed tab, and the Translators Center tells you which red links it added to the list and which it skipped.
      Marking an article published: the link to the live article, and the red links to add to the list

“Red links” are links that point to a valid page in the source language but have no equivalent page in the target language. Adding relevant red links to both your page and the list of articles to translate is important because it prevents the list from running out of articles to translate. Each red link you add gets priority “TBD” and the note “Red link from” followed by the link to your new article; an admin then reviews it to prioritize it. If you would like to work on one of them, claim it afterwards in Find an article.

Tips
  • There is no need for completeness: it is ok to miss a few red links – you should not spend too much time on this.
  • You don't need to check whether a red link is already on the list: the Translators Center checks every link against all the articles OKA has ever tracked and skips the ones it already has.
  • You can skip red links to articles of poor quality (e.g., less than 5 verifiable sources, books, already tagged due to article issues, super short, etc.).
  • You can skip red links to articles about persons, as there are too many of these to cover. Articles about songs can be skipped as well.
  • Put one link per line; do not group multiple links into one line.
  • If you forget, you can add red links later with the Add articles tab.
  • Stop the timer for this article on My work (Stop and save), and start it on your next article. If you spend more time on the article after publishing (for example to answer a reviewer), you can still log time against it: finished articles are listed under Recently completed in the timer's Article list.
Maintenance (“Watching” the page)
[edit]

Some people may provide feedback or challenge your page for a variety of reasons (e.g., they feel the topic is not relevant in Wikipedia, have issues with the quality of the translation, etc.). Some of these will require further edits/changes to address the concerns, or to discuss them in the “Talk” section of the page. Other people may make edits to your page, either helpfully (e.g., fixing typos, adding a new section) or not (vandalism).

Once a page is published, the whole Wikipedia community is responsible for it, so you do not necessarily need to address these concerns yourself. However, since you know the topic well (having created the page), you should try to address/answer these to the extent that they are reasonable and that you have the capabilities to do so.

To see recent edits made on pages that you “Watch”, click on the “Watchlist” at the top right corner of the page.

Configure the interface to your liking (e.g., hiding minor edits, edits made by bots). Once you have translated many articles, your watchlist will become long, so checking every change made will soon unsustainable. Instead, focus on reviewing major edits, and ignore minor changes. You should check your watchlist at least once per week.

Review by your manager

[edit]

After you mark an article published, it goes into your manager's review queue in the Translators Center. Your manager reads the published article and then either:

  • signs it off: its status on the Completed tab becomes “Published and reviewed”, and there is nothing more to do; or
  • asks a question: you receive an email and a notification, the article comes back to the top of your My work under Your manager asked something, and its status becomes “Questions from review”. The article stays published on Wikipedia.

To answer a question:

  1. Open the article from My work and read your manager's note under Notes.
  2. Fix what they raised on Wikipedia (log the time against the article as usual), or reply with a note on the article.
  3. On My work, click Send back for sign-off next to the article, say what you changed, and click Send it back. Your manager receives it for sign-off.

Declined or rejected articles

[edit]

If your article is declined or rejected by AfC, you should evaluate the reason and improve the article accordingly (e.g., by addressing the reviewer's or other editors' comments) so you can resubmit it as soon as possible. Log the time you spend on it against the article, as usual.

If an article has been declined more than once and/or you determine that it cannot be improved further, you must:

  1. Open the article in the Translators Center and add a Note with your reasoning; be as specific as you want (include the link to the reviewer's comments).
  2. Click Flag to admin, choose Other, and write a brief explanation under Details (e.g., "Declined article unfit for resubmission"), then click Send flag. Your manager is notified and decides what happens to the article.
Important: You don't need to wait for a manager to point out that your article was declined before reworking or resubmitting it.

Getting paid: your monthly bill

[edit]

Your grant is paid monthly, based on the hours you logged in the Translators Center. You submit your bill yourself, on the Submitting bills tab, usually once a month. The Translators Center fills in your hours for you. The full rules are in OKA's compensation and billing document (in the Resources menu of the Translators Center).

Your payment details

[edit]

Fill these in once, before your first bill; they are used for every bill after that. On the Submitting bills tab, go to How you want to be paid:

  1. Choose a Method. The list says which methods are preferred (OKA covers the sender fees), which cost you more (PayPal), and which have their fees deducted from your payment (Western Union, SWIFT). Wise, a SEPA transfer or a domestic transfer leave you with the most.
  2. Under Pay me in, choose the currency you want to receive. Bills are always worked out in US dollars; finance sends the same amount in your currency, and your payment email says how much arrived.
  3. Fill in the Account holder name and the details your method needs: IBAN or account number, bank name and country, and the bank's code for a bank transfer (its SWIFT/BIC, or the routing number for a US account); your username or email for Wise or PayPal. Western Union also needs your ID number. The form only shows the fields your method uses.
  4. Enter Your monthly rate (USD) and your Billing address. Your monthly rate is what a full month of 173 hours pays you: one of OKA’s rates, set by your role and how long you have worked for OKA (see the compensation and billing document in the Resources menu). It is not the total of one bill.
  5. Click Save preferences.
    The How you want to be paid card, filled in with example details

Your payment details are stored securely, and only the finance team can see them (managers cannot). You can see and change your own details at any time. If you empty a field and save, that detail is deleted from your record.

Submitting a bill

[edit]
  1. Open the Submitting bills tab. The Submit a bill card shows everything you have logged and not yet billed, today included: the hours logged, the billable hours, your monthly rate and the amount in US dollars, with a breakdown by category. There is no period to choose.
    The Submit a bill card: hours, rate and amount, worked out from your time entries
  2. If you want to use wellbeing hours, enter how many under Wellbeing hours to use on this bill (see Wellbeing hours).
  3. Check Hours claimed. You may claim fewer hours than offered; the rest wait for your next bill.
  4. If you are paid through Wise or PayPal, create a payment request for the amount shown and paste its link under Payment link for THIS bill. These links carry the amount and can only be used once, so each bill needs a new one. Leave the box empty for bank transfers. If you have no such link (for example, you are paid to your Wise email), leave it empty too: when the tool asks for the link, tick Submit with my payment details as they are under the note and submit again. The reviewer sees that the link is missing.
  5. If something needs explaining, add a Note for the reviewer. An invoice link is optional.
  6. Click Submit this bill. Your manager and the finance team are told at once, by email and in their notifications.

The amount is worked out for you: billable hours ÷ 173 × your monthly rate. A billing month counts as 173 hours (52 weeks × 40 hours ÷ 12).

If the card says Still needed before you can bill, some payment details are missing: click Show me where. How you want to be paid, your monthly rate and the account holder name are always needed. If the tool refuses another detail that is right as it is (a missing ID number, or a link that does not start with https://), tick Submit with my payment details as they are when it appears; the reviewer sees what did not pass the check. On the payment card, Save as typed does the same when the format of a detail is refused. If it says Recently billed, your last bill is too recent, and the card tells you when the next one can go in.

What happens after you submit

[edit]

Each bill is checked twice:

  1. Your manager checks the work: that the hours match what you delivered. They approve the work, ask you for clarification, or reject the bill.
  2. The finance team then checks the payment and sends the money. You receive an email saying how much was sent, and in which currency.

Under Your bills, click a bill to see what was filed, where the hours went (with the notes you wrote on your time entries; your reviewer sees them too), and what happened to it. Its status is one of:

Status Meaning
Submitted, Under review Waiting for your manager.
Manager cleared Your manager approved the work; finance will pay it.
Paid The money has been sent.
Needs resubmission Your reviewer asked for a change (you also receive it by email). If a note or which article the hours were for needs fixing, fix it and click Resubmit with a comment on the bill. To change hours or your monthly rate, click Withdraw it, correct them, and submit the bill again.
Rejected The bill was refused; the reason is on the bill. You can correct it and resubmit it.
Withdrawn You withdrew the bill. Its hours go back to unbilled and will be on your next bill.

Until a bill is paid, you can take it back with Withdraw it: its hours come back unbilled, so you can correct them and submit a new bill. If your manager had already cleared it, finance is told not to pay it, and your new bill is reviewed again.

To keep in mind

[edit]
  • Submit your bills regularly: you may never have more than 200 unsubmitted hours. A banner on My work and on Submitting bills shows how many hours you have not billed yet, and warns you as you get close to the limit.
  • A bill needs a minimum number of billable hours (the Submit a bill card shows it).
  • OKA expects at least 5 published articles per week, but of course that depends on the articles length. The most important is the quality, not the quantity!
  • Hours that you log late, for days that an earlier bill already covered, are not lost: they go on your next bill.

Wellbeing hours and Wikimedia events

[edit]

Wellbeing hours are paid hours that you earn as you work, like vacation: a billed month of 173 hours, 167 worked and 6 of wellbeing, earns its 6 wellbeing hours. In other words, you earn 6 wellbeing hours for every 167 hours you work (as logged in the Translators Center). If you are new at OKA, you start earning them once you have worked your first 519 hours (three months of full-time work).

  1. To use wellbeing hours, enter them on your bill: the Submit a bill card shows how many you have (what you have earned, less what your earlier bills used), and you choose how many to use on that bill. They are paid at your normal rate, and never billed automatically. You do not need to log them as time.
  2. You can enter more than the card shows, for example hours you earned before you logged your time here. Say why in Note for the reviewer: your reviewer sees both figures. The extra hours are not taken from the wellbeing hours you earn afterwards.
  3. If you want a record of your time off, you can also log it on My work under the category Wellbeing (leave Article empty). That is only a record: you are paid for the wellbeing hours you enter on your bill.

Wikimedia events: time spent editing at a Wikimedia event (category Wikimedia event (editing)) is billed normally. The non-editing parts of events, such as social activities and training (category Wikimedia event (social/training)), are billed at 66% of the hours you log, up to 16 hours a year (over a rolling 12 months) across all such events. The Submit a bill card applies this for you.

Seeing your work

[edit]

  • My work shows the articles you hold, grouped by what they need: Your manager asked something, Being worked on, Waiting for AfC review, and your recently finished articles (Finished, not yet billed, Finished with no time logged, Recently finished and billed). It also shows your hours for the week (click ‹ and › to see earlier weeks), the hours you have not billed yet, and your recent time entries. Click an article to open it.
    The My work tab: the articles you hold, grouped by what they need, and this week's hours
  • Completed lists every finished article, with its status (Published, Published and reviewed, Declined by AfC, Deleted…), its published link and the hours logged against it. Choose your name under Who to see only yours, and click a row to see the whole record. You can correct your own rows by clicking a dotted field, for example link next to the published title to fix the published address. If one of your published articles is later deleted from Wikipedia, click its status and choose Deleted (or Partially deleted). If you marked an article published by mistake, click Flag to admin on its page and say so: your manager can take it back off the list.
    The Completed tab, showing one translator's finished articles
  • Analytics shows charts of OKA's published work and of your own hours. The Articles per month, by outcome chart counts every finished article in the month it was finished, in one colour per outcome: published, published and reviewed, submitted to AfC and awaiting review, declined by AfC, or deleted. Tick Only my articles to see only yours. Its Impact on Wikipedia section shows how OKA's articles are doing on Wikipedia: pageviews, length, and the most-read articles. Long lists show their first rows; click View more for the rest.
    The Analytics tab, with Only my articles ticked
  • Translators lists everyone at OKA; click your own name to see your page, which also shows your details (only you and the finance team see them).

Notifications: the bell at the top right of every page lists what is addressed to you: notes on your articles, questions from your manager, and decisions and payments on your bills. Click an entry to open the article or the bill it is about. The same messages are also sent to you by email, from “OKA Translators Center” (info@oka.wiki) with the name of the person they come from; replying reaches that person.

The notifications bell, opened
An article that was published outside the Translators Center is not in My work, so the time forms do not offer it. To log time on it, find it on the Completed tab, click its row, and click Log hours against this. If it is not on Completed either, add it on the Add articles tab with I have already published these myself ticked.

Tips and best practices

[edit]

Finding articles in the Translators Center

[edit]

The Find an article list contains thousands of articles, so use the filters at the top of the tab to see only what is relevant to you (e.g., only articles from your source language into your target language):

  • From language and Into language: the source and target languages.
  • Type: Create, Expand, Improve or Write from scratch.
  • Priority: 0–3 recommended (the default), 0–1 highest, 0–5 full list or 0–9 including not recommended. Choose All to also see articles that have not been prioritized yet (“TBD”).
  • Taken by: the articles held by one person.
  • Category: what the article is about.
  • Filter as you type: part of a title, a link, a note or a category. You can also paste the address of a Wikipedia article to find it.
  • Hide assigned and Hide articles that need admin approval are ticked by default.

Click a column heading to sort the list by that column, and hover over it to see what the column means. In the Taken by column, yellow means that the article was claimed over a month ago and has not been finished. These filters only change your own view, so you can use them freely. Click Reload from server to see the articles that other people have just claimed or added.

Saving your work in progress

[edit]

To save your progress, simplify publish the latest version of your work as draft. It is very important to regularly save your work in progress!

Ensure that you do not submit your draft through AfC until it is finalized.

Alternatively, you can also save your wikicode in a separate document. Click on “Create source” or go to “Source editing”, select all text (scroll or use CTRL + A), copy, and paste into document.

Do not copy from the visual editing, or you will lose your progress!
This is an example of how it should look like:
  • To create an empty file, you can type doc.new in your browser.
  • You can find all your docs in Google Drive.
With your OKA professional account, you also get near unlimited storage on Google Drive, as well as all the advanced functionalities included in Google Workspace (e.g., for Google Sheet, Google Meet, Gmail). Therefore, you shouldn’t need any Microsoft Office license or other software subscriptions, because Google Workspace already contains all of these functionalities.

Overlinking and underlinking

[edit]

Appropriate links can be very helpful to increase readers' understanding of the topic at hand. To achieve this, it is important to find the right balance between what should and shouldn’t be linked.

What should be linked

[edit]
  • Relevant connections to the subject of another article that will help readers understand the article more fully. This can include people, events, and topics relevant to the article in question
  • Articles with relevant information
  • Articles explaining words of technical terms, jargon or slang expressions or phrases. If there is no appropriate Wikipedia article, a hyperlink to Wiktionary could be used
  • Proper names that are likely to be unfamiliar to readers

If you feel that a link is relevant to the topic of the article, but does not belong in the body of an article, consider moving it to a "See also" section

Typically, the following elements should always be linked (both blue links and red links):

  • Name of specific places, institutions or companies
  • Name of people
Note:
  • You can also create links to potential articles that do not yet exist (called red links). Here is an example:
  • You should add relevant red links to the list of articles to translate when you mark your article published in the Translators Center (as explained in this part).

What should not be linked

[edit]
  • Everyday words understood by most readers in context (e.g., education, violence, aircraft, river)
  • Common occupations (e.g., accountant, politician, actor)
  • The names of subjects with which most readers will be at least somewhat familiar. (e.g., countries, geographic features, famous locations, languages, nationalities, ethnicities or descent, and religions). However, try to be conscious of your own demographic biases – what is well known in your age group, line of work, or country may be less known in others
  • Common units of measurement (e.g., units relating to time, temperature, length, area, or volume)
  • Dates
  • Disambiguation pages. You should instead link to an appropriate choice on the disambiguation page
  • Red links about “subjectively defined” sub-aspects of the page you are translating. For example, if you translate the article “Paris”, it is ok to add a red link to “Paris Cathedral”, but you should not create red links to “History of Paris” or “Contemporary Art in Paris” as these are “optional” pages that some Wikipedia languages may not even find desirable to have
  • Pages that redirect to the page where the link is (circular reference)
The purpose of linking is to clarify, not emphasize. Do not link solely to draw attention or as a mark of respect.

Using underline

[edit]

In general, you should not use underline in your Wikipedia articles. If there is something that you feel like should be underlined, it is probably best to use bolding instead.

Improving the source article

[edit]

If you make improvements to an article (e.g., adding sources, shortening sentences, adding sub-sections), you should ideally do it to both the original article and the translated article. The easiest is to first do it on the source article before starting your translation, to minimize efforts.

Expanding existing articles

[edit]

Articles that are marked as “Type = Expand” already exist in the target language, but can be expanded with text translated from the corresponding article in the source language. If you are new to Wikipedia editing, it is easier to start with new articles than with expanding existing articles.

When doing so, the main guideline to keep in mind is: try to re-use as much of the existing content as possible. This is not only to minimize the amount of rework, but also to make sure that we don’t inadvertently delete valuable information.

Also, removing valuable text (reliable, well-written, and sourced) during the process, especially to replace it with text that is not as good, can be perceived by the community as disruptive editing and lead to the permanent banning of your Wikipedia account (and, consequently, the inability to continue participating in OKA).

This requires making some judgment calls. If a section is:

  • Missing entirely in the target language: you can translate it
  • Almost empty in the target language but very detailed and of much higher quality in the source language: you can completely replace the existing content with your translation.
  • Reasonably detailed in the target language but more detailed in the source language: you can either skip the section entirely, or translate a few paragraphs that add the most value. It is best to avoid deleting any content that already exists.

Whenever replacing content that already exists, try not losing the sources (for example by moving them somewhere else), “See also” section, images, categories, etc.

Important

You don't need to submit your expanded article to AfC, just edit the original page and publish directly. However, you must follow the same steps as with any other article:

  • Adequate attribution (brief summary, talk page, etc.)
  • Links from other pages to your new expanded article
  • Add/fix interlanguage links
  • Include the parameter category=expand inside the OKA template
  • Mark it published in the Translators Center, with the link to the expanded article (see After your article is approved)

Proofreading tool: DeepL Write

[edit]

DeepL Write is a useful tool that provides suggestions to improve your writing. It helps correct mistakes and choose better words so that the text is clearer and easier to understand.

As an OKA translator, proofreading is a crucial aspect of your work. Here's how DeepL Write can help you:

  • Improve clarity: it provides alternative words and suggestions for rephrasing sentences, making the text more concise and understandable.
  • Enhance grammar: it offers grammar corrections, helping you avoid common grammatical errors.
  • "Encyclopedic" tone: by using the "Academic" writing style instead of the default settings.
  • Assist non-native speakers: it can be particularly helpful in producing more natural-sounding text that will be better understood by English speakers.

While it is not advisable to depend entirely on this tool to proofread every translated paragraph (as you should be able to rely on your own skills and it will increase the time spent proofreading), there are some situations where we recommend using DeepL Write. These include:

  • Complex articles/topics, (e.g.: Priority 0-1, Medical, Law, etc.)
  • Confusing/poorly written original text.
  • Addressing/removing "Copy Edit" tags from already published articles.

Different rules for different Wikipedias

[edit]

As said, each Wikipedia has different rules and methods. This applies to templates, guidelines, help pages, noticeboards and others. Sometimes, for example, a template available on the English Wikipedia may not be available on the Portuguese Wikipedia. One way to check if the page also exists in the language you are translating is to click on the language links tab (top of the page, right side) and search for the target language.

Furthermore, when exploring Wikipedia, you may come across shortcuts, which are a special type of redirect page that can be used to access a page in the project more quickly. They are often used on talk pages or communities, but should not be used in articles. The same shortcut may work for different Wikipedias (WP:OR, which indicates a guideline related to the use of original research, works for both the English and Portuguese Wikipedias).

Error message "This graph was using the legacy Graph extension…"

[edit]

The error in the legacy Graph extension dates back to April 2023. You can find a summary of the issue and updates here.

Wikipedia has recently implemented a new Chart extension. However, it's still in the testing stage, so it may take some time before the new extension is implemented in every affected article.

If you encounter this error while translating, here's how to include the affected graphic in your translation:

  1. Find an older version of the article where the graphs still work. You can use the Internet Archive Wayback Machine website for this but also any other web archives available. For a list of known web archives you can go here.
  2. Take a screenshot of the graph and upload it to Wikimedia Commons with its corresponding description and attribution.
  3. Add the resulting image file to your translated article along with the original description and any other applicable translated data.
  4. Add a note to the article in the Translators Center (see Notes, questions and flags). For example: "Added unavailable legacy extension graph to "XXX" section by retrieving it from [link to the internet archive page]."
[edit]

Citation Style 1 (CS1) is a collection of reference citation templates that can be changed to create different types of styles for different referenced sources. It includes most of the templates used in the article creation process, such as Cite web, Cite book, Cite journal and Cite news.

Errors in CS1 citations occur when the parameters in the references are misused or incorrectly filled in. They can be visualized by installing the following script on your common CSS page (common.css).

:root .mw-parser-output .cs1-maint {display: inline;} /* display Citation Style 1 maintenance messages */

This error occurs when the parameter |year= is filled with a value other than YYYY(i.e. complete dates should not be added to this parameter).

This error occurs when the parameter |url-status= is filled with some value, but the parameters |archive-url= and |archive-date= are omitted from the template.

To fix this, if the value is live, either:

  • add both |archive-url= and |archive-date=,

or

  • remove the parameter |url-status= from the template.

If the value is dead, either:

  • add both |archive-url= and |archive-date= ,

or

  • Replace the reference if there are no archived links available.

This error occurs when the parameter |language= is filled with a value not recognized by MediaWiki. It's a simple mistake that can happen due to inattention when filling in the parameter.

This error occurs when the parameter |ref= is filled with a value equal to the CITEREF anchor ID created automatically by the CS1 templates.

For example, the reference {{cite book |last=Black |first=AB |last2=Blue |first2=CD |date= 2021 |title=Title}} automatically generates CITEREF anchor ID CITEREFBlackBlue2021. If the anchor ID created is the same one referenced in the text body when using the Harv template (or similar), the |ref= parameter does not need to be filled in, as this creates a conflict of information.

This error occurs when the citation includes the parameters |location=, |place=, or |publication-place=, and |date= or |year= , but not |publisher=.

This error only happens with books or encyclopedias published after 1850. If the work is older, the correct thing to do is to fill in the parameter as |publisher=none.

This error occurs when the system identifies multiple author names or the use of commas in the same parameter. It happens when filling in parameters |author=, |last=, |first=, its similar and succeeding equivalents (|last2=, |last3=, etc.).

Examples of incorrectly filled parameters: |first=Smith, John, |first=FC White, RN, MD.

When multiple separator characters are legitimately present in a name (commonly a corporate, institutional, or governmental author), the name may be wrapped in two sets of parentheses to suppress assignment to this category: |author=((Federal Ministry of Transport, Building, and Urban Development))

This error occurs when the parameter |url-status= is filled with bot: unknown. Editors should review these URLs and adjust the value assigned to the parameter accordingly.

This error occurs when the parameters |author=, |last=, |first=, its similar and succeeding equivalents (|last2=, |last3=, |first2=, |first3=) are filled with values that mix letters and digits.

Example of incorrectly filled parameter: |first=1938 John

When the author is a corporate or organizational name that includes digits, the accept-this-as-written markup may be applied to suppress this category: |first=((123 Company))

Frequently asked questions (FAQ)

[edit]

Can I also create new articles or improve existing ones, or only translate?

[edit]

You are also free to create new pages from scratch if you feel they would add a lot of value (e.g., because an important concept related to a page you are translating is missing entirely).

You do not need to ask for permission, unless this is a significant amount of work (e.g., it is ok to create a stub, but if a topic requires significant research to create a page and find the relevant sources, then please let your manager know first).

You are also encouraged to improve existing articles, even if they are not from OKA. Fixing issues and improving content is actually even more important than translating.

Add all pages you created or substantially improved to the Translators Center with the Add articles tab (see Articles that are not on the list), so that your hours and the result are recorded (if you have already published them, tick I have already published these myself there). For a new article that is not a translation, choose the Type “Write from scratch” and paste the English Wikipedia address the article will have; for an existing article you improved, paste its address and choose “Improve” (or “Expand”).

What should I do if I receive feedback on an AfC article?

[edit]

You should implement the feedback and resubmit the article.

In some cases, reviewers provide feedback without declining your submission; in that case, you should still implement the feedback but you do not need to resubmit the article. You should respond to their comments: go to the talk page of the draft and leave a comment there. Tag the person who added the comment (and add some context so they’ll know what it's about). and sign your own comment by using ~~~~ (which will automatically add your signature).

It isn't sufficient to just respond in your talk page or on the reviewer’s talk page, because it may not be visible to other people looking at the draft

What should I do if someone raises an issue about an article I created?

[edit]

Try your best to address the issue. If you are unsure about the right next steps, you can ask for help in the chat. If you expect the work to be significant, and you are not sure whether it is worth it, you can also ask in the chat whether you should continue to work on it.

If the issue puts you at risk of an account suspension, or if it could affect the reputation of OKA, then raise it in the chat so that we can look into it.

Whatever you do, do not use AI to respond to the editor who raised concerns. Reply in your own words.

If you have spent significant time addressing issues on an article, log that time against the article and add a Time note (T/N) to it in the Translators Center, so that we know why it took you longer.

Can I abandon a draft that's rejected?

[edit]

If you feel like it's no longer worth working on a rejected draft, open the article in the Translators Center, add a note with your rationale, and click Flag to admin (choose Other) so that your manager sees why you believe it should be abandoned. If your manager agrees with the rationale, they will deprioritize the article.

Don't leave a draft untouched for more than a month, as drafts get deleted if they are abandoned for too long.

How are articles prioritized for translation?

[edit]

The prioritization (0 being the highest priority, 9 being the lowest priority) is indicative only and does not follow a set of strict rules. It is based on a quick assessment by the admins or managers. New articles, such as red links, show “TBD” in the Translators Center until an admin or manager has prioritized them.

Generally speaking, anything with priority 0-3 should eventually get translated. Things with priority 4 will likely get translated if budget allows for it. Articles with priority 5 may be reconsidered. Items with priorities 6 or higher are unlikely to be ever translated, unless it matches the personal interests of a specific translator or if OKA focus changes.

The below is a rule of thumb on how articles get prioritized for translation into English. For translation into other languages, the prioritization also includes the the criteria below but relies mostly on the pageviews potential.

0. Highest priority

[edit]

For critical articles on very important topics. For example:

  • Good quality or critical articles about Law, Medicine, Mathematics, Computer Science. These articles are often more technical in nature due to the complexity of novelty of the topic.

1. Very high priority

[edit]

For articles on important topics. For example, articles about:

  • A mountain, valley, or other geographical feature covering a large physical area (e.g., Tagus Basin)

2. High priority

[edit]

3. Medium priority

[edit]

Will likely be translated, though with a lower priority.

Note

If a person/company is still alive/in existence, it will usually receive a much lower priority.
This is because:

  • His Wikipedia page is likely to continue to evolve; and
  • The individual/company itself and people who interact with it will have interests to create/translate the page.
OKA is here to create articles that would otherwise not exist, so we try to avoid translating articles that would anyway have been translated if we didn’t exist (crowding out effect).

Important: Any article that was labeled "Featured" or "Good" in the source language should be rated as priority 3 or below, regardless of the topic. This is because OKA strives to translate all "Good" and "Featured" articles into English. The only exception is articles that may not be allowed in English (e.g., ES Wikipedia has featured articles about a single song, which isn't considered notable enough in EN).

4. Low priority

[edit]

Will be translated if budget allows for it. Pages in this category will often have less sources, less formatting (e.g., may lack an infobox). Example of pages include:

  • Events that are notable enough to deserve a page, but not particularly important (e.g., Tropical Storm Erick (2007))
  • Specific aspect of a topic (e.g., Faculty of Psychology (Universidad Nacional Mayor de San Marcos) is a subtopic to the university itself)
  • Buildings that no longer exist (e.g., Portal de Mar)
  • Very small geographical areas or neighborhoods (e.g., Santa Terezinha)
  • Alive individuals or companies with a significant enough influence (e.g., RecordTV Brasilia) but without much interest outside of the source language
  • Historical ships (e.g., Araraquara)
  • Articles that would normally fall in the above priorities, but where the quality of the text low or sources are lacking, requiring some additional work to meet the Wikipedia standards

5. Very low priority

[edit]

Typically, the article will be a mix of low importance or low quality (e.g., lacking sufficient sources). It may still be worth translating but will require checking first whether the page is good enough. Example of topics:

  1. Individuals or companies where notability is not evident without further investigation (e.g., Netos’s)
  2. Specific movies, books, shows that may not be very popular outside of the source language (e.g., Floribella (Brazilian telenovela), MTV Live: Ivete Sangalo)
  3. Roads (e.g., Augusto Montenegro Highway), or train stations (e.g., Estación Limache). The issue with these is they often change as they are dependent on urban planning. As a result, the translation is often unstable. And these articles are often written by transportation hobbyists, thus sometimes getting more depth than they deserve
[edit]

You can pick it up if the topic interests you, but you should be very careful and check with a manager before translating. Reasons for this rating include:

  1. The topic is likely to be rejected in EN wikipedia due to lack of notability (e.g., a specific song, a character within a book, a person that is not relevant enough in their country of origin or would not be relevant elsewhere)
  2. The topic is too specific to the source language and cannot easily be translated
  3. The page is of very low quality or too short
  4. The topic is already well covered in other articles in the target language
  5. Topic is about a niche aspect of sport or a hobby (e.g., México en la Copa Mundial de Fútbol de 2010, Gol del terremoto). Sport articles are often written by fans and do not always justify the depth of coverage that they receive on Wikipedia

Manual of style (MoS)

[edit]

Wikipedia has a style of its own, due to this, the Manual of Style (MoS) serves as the definitive style guide for English Wikipedia articles. It is very long and detailed, so you can find below a summary of the most important aspects of it for your work at OKA. Neverheless, you are encouraged to go deeper into the official MoS.

The MoS helps writers compose articles using clear, concise language, and to organize content with uniform, reader-friendly layouts and formatting.

Article titles, sections, and headings

[edit]

Article titles

[edit]

A title should effectively capture the essence of the topic with a recognizable name or description that is natural, adequately precise, concise, and aligns with related articles. In cases where these criteria may conflict, strive for a balanced approach that considers the interplay between naturalness, precision, conciseness, and consistency with related topics.

In article titles, capitalize the initial letter (except in rare cases, such as eBay), but follow sentence case (e.g., Funding of UNESCO projects) rather than title case (e.g., Funding of UNESCO Projects), unless title case would be expected in ordinary prose. Refer to Wikipedia's Naming Conventions (capitalization) for guidance.

For italicization, insert the following template near the top of the article:

{{italic title}}

In mixed situations, use, for example:

{{DISPLAYTITLE:Interpretations of ''2001: A Space Odyssey''}}

It will appear as follows:

Interpretations of 2001: A Space Odyssey

Avoid using articles (a, an, or the) as the first word in titles unless they are an inseparable part of a name (e.g., The Hague) or title of a work (e.g., A Clockwork Orange, The Simpsons).

Prefer using nouns or noun phrases in titles (e.g., "Early life", not "In early life").

The final character in a title should not be punctuation unless it is an inseparable part of a name (e.g., Saint-Louis-du-Ha! Ha!, Do Androids Dream of Electric Sheep?) or an abbreviation (e.g., Inverness City F.C.), or when a closing round bracket or quotation mark is necessary (e.g., John Palmer (1814 schooner)).

Whenever quotation marks or apostrophes appear, create a redirect for the same title using the appropriate punctuation.

Section organization

[edit]

The content of an article should commence with an introductory lead section, providing a succinct summary that is not divided into sections. The subsequent sections of the article are typically organized and presented in a structured manner.

Main tag: If the topic of a section is covered in more detail in a dedicated article, insert one of these immediately under the section heading:

{{main|page name}}

or

{{further|page name}}


Short description: Each article should have a short description. Add one with the following template:

{{Short description|description}}

If the article title already contains everything required, you can put “none”, but the tag should still be added.

Hatnote templates: these tags can be useful to help readers locate different articles with similar titles or articles connected to your subject.

Here are some examples:

{{Hatnote|description}}


{{About|text}}


{{For|text|page-name}}


Section headings

[edit]

Section headings should generally adhere to the guidance for article titles, utilizing sentence case (e.g., Funding of UNESCO projects in developing countries) rather than title case (e.g., Funding of UNESCO Projects in Developing Countries).

For technical reasons, section headings should:

  1. Be unique within a page to ensure accurate section links.
  2. Avoid containing links, especially if only part of a heading is linked.
  3. Exclude images or icons within the heading.
  4. Exclude <math> markup.
  5. Exclude citations or footnotes.
  6. Avoid misusing description list markup (";") to create pseudo-headings.
  7. Exclude template transclusions within the heading.

To maintain a consistent style, section headings should:

  1. Avoid redundant references to the subject of the article, using concise titles like "Early life" instead of "Smith's early life" or "His early life."
  2. Refrain from referencing a higher-level heading unless it results in a shorter or clearer title.
  3. Avoid numbering or lettering headings in an outline format.
  4. Frame headings as statements rather than questions; for example, use "Languages" instead of "What languages are spoken in Mexico?"
  5. Steer clear of using color or unusual fonts that may pose accessibility problems.
  6. Ensure headings are not wrapped in markup to prevent display and accessibility issues.

National varieties of English

[edit]

National varieties of English, such as American English or British English, exhibit differences in vocabulary (e.g., elevator vs. lift), spelling (e.g., center vs. centre), and occasionally grammar. The English Wikipedia maintains a neutral stance, preferring no national variety over others.

The formatting of dates in articles (e.g., December 4, 2023 vs. 4 December 2023) is also related to national varieties of English and should align with the conventions of the relevant variety being used.

For an international encyclopedia, it is preferable to use vocabulary that is common to all varieties of English:

  1. Utilize universally accepted terms rather than those less widely distributed, particularly in titles. For example, "glasses" is preferred to the national varieties "spectacles" (British English) and "eyeglasses" (American English); and "ten million" is preferable to "one crore" (Indian English).
  2. If a variant spelling appears in a title, create a redirect page to accommodate others, as demonstrated with "artefact" and "artifact," allowing all variants to be used in searches and linking.
  3. To prevent confusion, gloss terms that differ between varieties of English or have divergent meanings. For instance, clarify "trunk" (American English) or "boot" (British English) when referring to a car.
  4. In cases where terms have different meanings due to national differences, use a commonly understood word or phrase rather than one with a different meaning. For instance, prefer "alternative" or "alternating" over "alternate" (except in technical contexts, such as "alternate leaves" or "alternate law"), unless such substitution would be inappropriate.
  5. When multiple variant spellings exist within a national variety of English, usually prefer the most commonly used current variant. However, exceptions can be made where the less common spelling holds specific usage in a specialized context, as seen with "connexion" in Methodist connexionalism.

Capital letters

[edit]

Generally, do not capitalize the word mid-sentence:

  • Correct: throughout the United Kingdom.
  • Incorrect: throughout The United Kingdom.

Conventional exceptions include certain proper names ("he visited The Hague") and most titles of creative works ("Tolkien wrote The Lord of the Rings"), but be aware that "the" may not be part of the title itself, ("Homer composed the Odyssey").

The English-language titles of compositions (books and other print works, songs and other audio works, films and other visual media works, paintings and other artworks, etc.) are given in title case, in which every word is given an initial capital except for certain less important words. The first and last words in an English-language title are always capitalized.

Capitalization in foreign-language titles varies, even over time within the same language; generally, retain the style of the original for modern works, and follow the usage in current English-language reliable sources for historical works. When written in the Latin alphabet, many of these items should also be in italics, or enclosed in quotation marks.

Capitalize names of particular institutions, but not generic words for institutions:

(...) the founding of the University of Delhi.

(...) the history of Stanford University.

(...) high school is near the university.

Do not capitalize "the" at the start of an institution's name, regardless of the institution's preferred style. There are rare exceptions, when a leading "The" is represented by a "T" in the organization's acronym: The International Cat Association (TICA). Treat political or geographic units similarly:

"The city has a population of 55,000." "The two towns merged to become the City of Smithville."

Do not mimic the style of local newspapers which refer to their municipality as "the City" or "The City"; an exception is the City of London, referred to as the City in a context that already makes the subject clear, as distinct from London and Greater London. When in doubt, use the full name for accessibility reasons; users of text-to-speech systems usually cannot hear a difference between city and City.

Ligatures

[edit]

Ligatures are appropriate in languages where they are standard practice, as seen in the preference for "clin d'œil" over "clin d'oeil" in French (for example, Moreau's last words). However, in English, the use of ligatures is generally avoided, with words like "encyclopedia" or "encyclopaedia" being acceptable, but not "encyclopædia." Exceptions exist for proper names, where ligatures may be retained, as in "Æthelstan" instead of "Aethelstan."

Abbreviations

[edit]

When an abbreviation will be used in an article, first introduce it using the full expression:

“(...) an early local area network (LAN) developed by Digital Equipment Corporation (DEC) (...) DEC's later LAN products were (…)”

Do not use capitals in the full version merely because capitals are used in the abbreviation:

“(...) an early Local Area Network (LAN).”

Except in special circumstances, common abbreviations (such as PhD, DNA, USSR) need not be expanded even on first use.

Pluralize acronyms by adding -s or -es, not by adding apostrophes:

  • Correct: “Three CD-ROMs and two BIOSes were released.
  • Incorrect: “Three CD-ROM's and two BIOS's were released.”

To indicate approximately, use c., is preferred over circa, c., ca., or approx. For that, use the following template:

{{circa}}

Avoid devising new abbreviations, especially acronyms. For example, “World Union of Billiards” is good as a translation of “Union Mondiale de Billard”, but neither it nor the reduction “WUB” is used by the organization or by independent sources; use the original name and its official abbreviation, “UMB”.

If it is necessary to abbreviate in a tight space, such as a column header in a table, use widely recognized abbreviations. For example, for “New Zealand gross national product”, use “NZ” and “GNP”, with a link if the term has not already been written out in the article: NZ GNP. Do not make up initialisms such as “NZGNP”.

In normal text and headings, use “and” instead of the ampersand (&):

  • Correct: January 1 and 2.
  • Incorrect: January 1 & 2.

You can retain an ampersand when it is a legitimate part of the style of a proper noun, the title of a work, or a trademark, such as in “AT&T”. Elsewhere, ampersands may be used with consistency and discretion where space is extremely limited (e.g., tables and infoboxes).

Italics

[edit]

Italics can be used for emphasis, rather than boldface or capitals. But overuse diminishes its effect; consider rewriting instead.

There’s a template that can be used for emphasis. This allows user style sheets to handle emphasis in a customized way, and helps reusers and translators. Try:

<em>emphasized-text</em>

or

{{em|...}}

Use italics for the titles of works (such as books, films, television series, named exhibitions, computer games, music albums, and artworks). The titles of articles, chapters, songs, episodes, storylines, research papers and other short works instead take double quotation marks.

Italics are not used for major religious works (the Bible, the Quran, the Talmud).

Italics is indicated for phrases in other languages and for isolated foreign words that are not common in everyday English. However, proper names (such as place names) in other languages are not usually italicized, nor are terms in non-Latin scripts. There are templates that support all ISO 639 language codes, correctly identifying the language and automatically italicizing for you. Please use these templates rather than just manually italicizing non-English material:

{{lang}}

Use italics for the scientific names of plants, animals, and all other organisms except viruses at the genus level and below (italicize Panthera leo, but not Felidae). The hybrid sign is not italicized (Rosa × damascena), nor is the "connecting term" required in three-part botanical names (Rosa gallica subsp. officinalis).

Use italics within quotations to reproduce emphasis that exists in the source material. If it is not clear that the source already included italics (or some other styling) for emphasis, add the editorial note “[emphasis in original]” after the quotation. If adding emphasis that was not in the original, add the editorial note “[emphasis added]” after the quotation.

Quotations

[edit]

Quotations must be verifiably attributed, and the wording of the quoted text must be faithfully reproduced. This is referred to as the principle of minimal change. Where there is good reason to change the wording, bracket the changed text; for example, “Ocyrhoe told him his fate” might be quoted as “Ocyrhoe told [her father] his fate”.

If there is a significant error in the original, follow it with [sic]) to show that the error was not made by Wikipedia. Use this template:

{{sic}}

However, insignificant spelling and typographic errors should simply be silently corrected (for example, correct “basicly” to “basically”).

Quotation should be used, with attribution, to present emotive opinions that cannot be expressed in Wikipedia's own voice, but never to present cultural norms as simply opinional:

  • Acceptable: “Siskel and Ebert called the film ‘unforgettable’.”
  • Unacceptable: “The site is considered ‘sacred’ by the religion's scriptures.”

Be conservative when linking within quotations; link only to targets that correspond to the meaning clearly intended by the quote's author. Where possible, link from text outside of the quotation instead – either before it or soon after. (If quoting hypertext, add an editorial note, [link in original] or [link added], as appropriate, to avoid ambiguity as to whether the link was made by the original author.)

Format a long quote (more than about forty words or a few hundred characters, or consisting of more than one paragraph, regardless of length) as a block quotation, indented on both sides. Block quotations should be enclosed in:

{{blockquote}}

Do not enclose block quotations in quotation marks (and especially avoid large, decorative quotation marks; those provided by the {{cquote}} template have been disabled in mainspace). Block quotations using a colored background are also discouraged.

Dates and time

[edit]

Times of day are normally expressed in figures rather than words. Context determines whether the 12- or the 24-hour format is more appropriate.

Full dates are formatted 10 June 1921 or June 10, 1921; or where the year is omitted, use 10 June or June 10.

For month and year, write June 1921, with no comma. Abbreviations for months, such as Feb, are used only where space is extremely limited. Such abbreviations should use three letters only, and should not be followed by a period (full point) except at the end of a sentence.

Names of seasons may be used when there is a logical connection to the event they are describing (“the autumn harvest”) or when referring to a phase of a natural yearly cycle (“migration typically starts in mid-spring”). Otherwise, neutral wording is usually preferable:

  • Correct: “He was elected in November 1992.”
  • Incorrect: “He was elected in the fall of 1992.”

Years are denoted by AD and BC or, equivalently, CE and BCE. Use only one system within an article, and do not change from one system to the other without good reason. The abbreviations are written without periods, and with a non-breaking space, as in 5 BC. Omit AD or CE unless omitting it would cause ambiguity.

Terms such as "current", "now", and "recent" should be avoided. What is current today may not be tomorrow; situations change over time. Instead, use date- and time-specific text. To help keep information updated use a template that will allow editors to catalog and update dated statements:

{{As of}}
  • Correct: “As of March 2011, he is the ambassador to…”
  • Incorrect: “He is the current ambassador to…”

Numbers

[edit]

Spell out integers from zero to nine, while those greater than nine and expressible in one or two words can be presented in either numerals or words.

For larger numbers, use commas to group digits in numbers with five or more digits to the left of the decimal point; for four-digit numbers, it is at the editor's discretion (e.g., 12,345 or 1000).

Prefer decimals over fractions for measurements, but use fractions with imperial and U.S. customary units for consistency within articles.

Scientific notation (e.g., 5.8 × 107 kg) is favored in scientific contexts.

Introduce "million" and "billion" in full on the first use, and afterward, use unspaced "M" for millions and "bn" for billions (e.g., 70M and 25bn).

Express percentages as "3%," "three percent," avoiding spaces (e.g., not "3 %" or "three %"). Use the American term "percent." In percentage ranges written with an en dash, include a single percent sign (e.g., 3–14%).

Currencies

[edit]

On the initial mention, employ the complete abbreviation (such as US$ for the US dollar and A$ for the Australian dollar), unless the context already clarifies the currency. For instance, "the government of the United States always spends money in American dollars, and never in Canadian or Australian dollars."

Represent ranges with a single symbol, as in $250–300.

In articles not specific to a particular country, express monetary amounts in United States dollars, euros, or pounds sterling. Avoid linking well-known currency names or symbols ($, €, £) unless there's a specific reason to do so. Do not use potentially ambiguous currency symbols unless the context makes the meaning clear.

For country-specific articles, use the local currency. On the first occurrence, consider providing conversion to US dollars, euros, or pounds sterling, using a context-appropriate exchange rate (e.g., "Since 2001 the grant has been 10,000,000 Swedish kronor (€1.0M as of August 2009)"). Avoid using terms like "approx." for simple rounding-off of converted amounts.

Generally, use the full name of a currency, linking it to its initial appearance if English-speakers might be unfamiliar with it (e.g., 52 Nepalese rupees); subsequent mentions can use the currency sign (e.g., just 88 Rs). Most currency symbols precede the number and are unspaced ($123, not $ 123).

Units of measurement

[edit]

In non-scientific articles strongly associated with the United States, the primary unit typically adheres to the U.S. customary system (e.g., 22 pounds (10 kg)).

Conversely, in non-scientific articles with strong ties to the United Kingdom, while the primary unit is generally metric (10 kilograms (22 lb)), imperial units may still serve as the main units in certain contexts (e.g., 7 miles (11 km) by road).

When English-speaking countries employ different units for the same measurement, include a conversion in parentheses, as demonstrated with the lengths of the Mississippi River (2,320 miles or 3,734 km) and the Murray River (2,375 kilometres or 1,476 mi).

Use the convert template for conversions. In direct quotations, maintain the original units, providing conversions in square brackets "[ ]" when necessary:

{{convert}}

For concise formats like tables, infoboxes, parenthetical notes, and mathematical formulas, use unit symbols.

In prose, spell out unit names initially if infrequently used, transitioning to symbols for repeated instances (e.g., Up to 15 kilograms of filler is used for a batch of 250 kg), unless the unit name is rarely spelled out (°C instead of degrees Celsius).

Use "per" instead of a slash when writing out a unit (e.g., "meter per second," not "meter/second").

Introduce unfamiliar units to general readers with a name–symbol pair on the first use, linking the unit name (e.g., Energies were originally 2.3 megaelectronvolts (MeV), but were eventually 6 MeV).

Unit symbols precede figures and are separated by a non-breaking space, such as 5 min.

The percent sign (%) and units of degrees (°), minutes (‘), and seconds (‘’) for angles and coordinates are unspaced.

Vocabulary

[edit]

Contractions

[edit]

Steer clear of contractions in formal writing, as they are generally deemed inappropriate. For instance, opt for "do not" instead of "don't." However, an exception is made for the use of "o'clock." Refrain from using contracted titles like "Dr." and "St." in formal writing, although exceptions may be warranted in certain contexts, such as quoted material, place names, or titles of works.

Gender-neutral language

[edit]

Employ gender-neutral language, avoiding generic pronouns such as “he” or “she” when clarity and precision permit. However, this guideline does not extend to direct quotations or the titles of works, which should remain unchanged.

Additionally, gender-neutral phrasing is recommended for references to space programs, encompassing past, present, and future endeavors, with terms like “human spaceflight”, “robotic probe”, “uncrewed mission”, “crewed spacecraft”, “piloted”, “unpiloted”, “astronaut”, and “cosmonaut”, as opposed to “manned” or “unmanned”. It's important to maintain the original gendered language in direct quotations and proper nouns.

When referring to ships, both neuter forms ("it," "its") and feminine forms ("she," "her," "hers") are acceptable. However, each article should consistently adhere to one style or the other, and changes between styles should only be made for substantial reasons.

Instructional and presumptuous language

[edit]

Eliminate phrases like "remember that" and "note that", which adopt an unencyclopedic tone by directly addressing readers and can be perceived as instructional, thus breaking the fourth wall of Wikipedia self-reference.

Similarly, avoid expressions such as "of course," "naturally," "obviously," "clearly," and "actually," as they may make presumptions about readers' knowledge, convey a viewpoint, and cast doubt on the rationale for presenting information.

Refrain from asserting that something is interesting, ironic, surprising, unexpected, or amusing. Instead, present sourced facts neutrally, allowing readers to draw their own conclusions. These constructions can typically be omitted, leaving behind sentences with a more academic and less assertive tone.

Additionally, avoid rhetorical questions, especially in headings. Opt for a heading like "Active Listening" with accompanying text such as "The term active listening, coined in...", rather than posing a question like "What is active listening?"

Subset terms

[edit]

A subset term denotes a group of members within a broader class. Common subset terms include "including," "among," and "etc." It is advisable to avoid redundant use of subset terms, such as constructions like "Among the most well-known members of the fraternity are included two members of the Onassis family" or "The elements in stars include hydrogen, helium, etc." The term "including" does not indicate a comprehensive list; instead, consider using alternatives like "consisting of" or "composed of" for clarity.

Gender identity

[edit]

Only use gendered words for individuals if they align with the person's most recent self-identification, as reported in recent sources.

In the case of living individuals who were not notable under a former name, that previous name should be excluded from any Wikipedia page, including quotations, out of respect for privacy. However, this exclusion does not apply to source citations.

Former names that were notable should be introduced with "born" or "formerly" in the lead sentence of the individual's primary biographical article.

In unrelated articles, avoid delving into specifics about a person's name or gender unless directly relevant to the context. To prevent confusion, consider paraphrasing, omitting, or using square brackets to replace portions of quotations when necessary, particularly to address former names and mismatched gendered words.

Foreign terms

[edit]

Limit the use of non-English terms. Italicize phrases in other languages and isolated foreign words that are not widely used in English, utilizing the following template with the appropriate ISO language code where feasible:

{{lang|es|casa}}

For foreign names of people, places, or organizations, where italics are not applied on Wikipedia, you can employ this template to apply language markup without italicization:

{{langr}} 

The {{lang}} template and related templates automatically italicize text for Latin-alphabet scripts, so additional italicization markup is unnecessary.

Non-Latin-based scripts like Chinese should not be italicized, as it is evident.

Loanwords and borrowed phrases that have common usage in English – Gestapo, samurai, vice versa – do not require italics. A rule of thumb is to not italicize words that appear in major general-purpose English-language dictionaries.

Names originally written in scripts such as Greek, Cyrillic, or Chinese must be provided in a romanized form for use in English. Utilize a systematic transliteration or another recognized romanization method (e.g., Aleksandr Tymoczko, Wang Yanhong). However, if there is a more commonly used English form of the name (e.g., Tchaikovsky, Chiang Kai-shek), prefer the widely accepted English version.

Technical language

[edit]

While certain topics are inherently technical, editors should strive to make them comprehensible to a broad audience. Minimize the use of jargon, and when it is unavoidable, either explain it within the text or tag it using {{Technical}} or {{Technical-statement}} for other editors to address. In instances where articles are unavoidably technical, creating a separate introductory article (e.g., Introduction to general relativity) might be the most effective approach.

{{Technical}}

or

{{Technical-inline}}

Avoid excessive wikilinking as a substitute for parenthetic explanations, and refrain from introducing new and specialized words solely for the purpose of educating the reader when more common alternatives are available. When the concepts denoted by jargon are too intricate to succinctly explain within parentheses, consider providing additional background information, possibly through a brief section with {{main}} tags directing readers to comprehensive articles on the prerequisite notions. This approach is practical when the prerequisite concepts are integral to the article's main topic and not overly numerous. Note that shorter articles, like stubs, typically do not include such sections.

Geographical items

[edit]

As an English-language encyclopedia, established English names are preferred when available, and spellings in non-English alphabets should be consistently transcribed into the Roman alphabet. In general, articles should reference places by the names used in their respective articles, following the guidelines outlined in Wikipedia's Naming Conventions for Geographic Names. However, if a different name is more suitable in a specific historical or contextual setting, it may be used, with the standard modern name provided in parentheses after the first occurrence.

At the outset of an article, include notable equivalent names from other languages, incorporating transcriptions where necessary. For example:

"Cologne (German: Köln, IPA: [kœln]) is the..."

"Mount Fuji (富士山 Fuji-san, IPA: [ɸuʥisaɴ]) is the..."

Media files

[edit]

Images

[edit]

Position each image within the level 2 section to which it corresponds, located either within the section defined by the most recent ==Heading== delimited by two equal signs or at the top of the lead section. Do not place images directly above section headings.

Avoid placing text horizontally between two facing images or between an image and an infobox.

When displaying images of people, it is often preferable for them to "look" toward the text, but do not achieve this by reversing the image.

Refrain from referencing image placement as being to the left, right, above, or below, as such descriptions are platform-dependent and lack meaning for users relying on screen readers. Instead, use captions to identify images. The |alt= text for an image serves as a substitute for those unable to view the image.

Captions

[edit]

Captions should typically commence with a capital letter. While most captions consist of sentence fragments and should not conclude with a period, any complete sentence within a caption necessitates proper punctuation with periods.

The text of captions should adhere to standard formatting, with special emphasis applied only when applicable to the main text (e.g., italics for the Latin name of a species). Keep captions concise, reserving additional information for the image's description page or the main text.

For technical charts and diagrams, captions may require more extensive content to fully describe all elements of the image and convey its significance. In such cases, a more detailed caption is warranted.

Other media files

[edit]

Recommendations for other media files, including video and audio files, closely align with those for image files, where applicable. Consistent with style guidelines for images, ensure appropriate placement within the content.

Bulleted and numbered lists

[edit]

Avoid using lists if a passage reads easily as plain paragraphs. When lists are necessary, employ proper wiki markup or template-based list code.

Avoid leaving blank lines between items in a bulleted or numbered list unless there is a specific reason, as this can lead the Wiki software to interpret each item as starting a new list.

Use numbers rather than bullets if there is a need to refer to elements by number, the sequence of items is crucial, or the numbering holds independent meaning (e.g., in a listing of musical tracks).

Maintain consistent grammatical form for all elements in a list. Do not mix sentences and sentence fragments within the same list.

[edit]
[edit]

Create links only where they are relevant and provide contextual value. Excessive use of hyperlinks can be distracting and may impede the reader's flow. Avoid redundant links, as they clutter the page and complicate future maintenance. High-value links should be clearly noticeable.

When linking to sections within a page, use a hash sign (#) followed by the appropriate heading. For example, to directs to a specific section of the article on Apostrophes, use this:

[[Apostrophe#Use in non-English names]]

Capitalize the first letter only when natural or when explicitly referring to the linked article by its name.

It is essential to check links to ensure they lead to the intended destination. Many dictionary words may redirect to disambiguation pages rather than comprehensive or well-chosen articles.

[edit]

External links should generally not be embedded within the body of an article. Instead, articles should incorporate an "External links" section at the end, pointing to additional information outside Wikipedia, distinct from citation sources. Clearly identify each link and briefly indicate its relevance to the article. For example:

[https://history.nih.gov/exhibits/history/index.html History of NIH]
[https://nih.gov/ National Institutes of Health homepage]

These links will be displayed as:

History of NIH

National Institutes of Health homepage

When applicable, use external link templates like:

{{Official website}}

and

{{URL}}

Add external links judiciously, as Wikipedia is not intended to serve as a repository for links.

Words and expressions to be careful with

[edit]

On WP, there are no explicitly prohibited words or expressions; however, you are advised to exercise caution in their language choices to avoid introducing bias. It is recommended to refrain from employing expressions that may be considered as either complimentary or disparaging, overly vague, clichéd, or indicative of a specific viewpoint.

All WP content must show a neutral point of view. If the original article you’re working on has neutrality issues, sometimes it can be solved by choosing more adequate words. These tips apply to all languages that OKA works with, not just English.

Translators should take some time to study the appendix of the Manual of Style: Words to watch. Here, we summarize the most important examples that may help you improve your translation. Keep in mind that the examples are in English, but the guidelines apply to any other language.

Subject promotion

[edit]

Avoid the use of terms for expressions that promote a subject without providing verifiable information (“peacock terms”). You can employ factual content and attribution to support these expressions if they were truly used by some reliable source

  • Bad example: “Bob Dylan is the defining figure of the 1960s counterculture and a brilliant songwriter”.
  • Adequate information: “Dylan was included in Time's 100: The Most Important People of the Century, in which he was called ‘master poet, caustic social critic and intrepid, guiding spirit of the counterculture generation’[1]”.
  • Avoid: legendary, best, great, acclaimed, iconic, visionary, outstanding, leading, celebrated, popular

Contentious labels

[edit]

Be cautious when employing value-laden labels, such as "cult" or "racist," preferring their usage only when widely accepted by reliable sources, with in-text attribution. Avoid informal use of terms like "myth" and provide scholarly context for formal applications. Use prefixes (e.g., pseudo-) and suffixes (e.g., -gate) judiciously, ensuring wide external recognition and utilizing in-text attribution when uncertain. Instead of labeling individuals as "controversial," offer specific information about pertinent controversies, verifying their existence through reliable sources.

  • Avoid: cult, racist, perverted, sexist, homophobic, transphobic, misogynistic

Unsupported attributions

[edit]

“Weasel words” encompass language designed to create the illusion of specificity while conveying vague or ambiguous claims. This often occurs through vague attribution, where a statement appears authoritative but lacks substantial basis. Such phrases may give the semblance of supporting statements while concealing the source, potentially masking biased views. To maintain clarity and transparency, claims about people's thoughts, feelings, beliefs, or demonstrated facts should be explicitly attributed.

  • Avoid: some people say, many scholars state, it is considered, most feel, experts declare, it is widely thought, research has shown.

Expressions of doubt

[edit]

Some terms suggest a level of uncertainty or potential inaccuracy regarding a given point.

  • Avoid: supposed, apparent, purported, alleged, accused, so-called.

Editorializing

[edit]

Some adverbs and phrases can highlight things as significant or special. This must be avoided to prevent particular opinions from being brought up.

  • Avoid: notably, arguably, interestingly, essentially, absolutely, happily, sadly, tragically, fortunately, unfortunately.

Euphemisms

[edit]

Use of mild or indirect expressions to soften/mask an unpleasant or direct idea.

  • Bad example: pass away, make love.
  • Adequate information: die, have sex.

Clichés and idioms

[edit]

Prefer direct and literal expressions over clichés and idioms when describing something. Be precise in your language and avoid phrases that may lead to misunderstanding.

  • Avoid: tip of the iceberg, at the end of the day, bird in the hand, white elephant, lion’s share.

Unspecified places, events or time references

[edit]

Prioritize specific statements over general ones. Utilize explicit descriptions, grounded in reliable sources, to detail the precise when, where, or how of an event. Opt for absolute time specifications over relative constructions, as the latter may become outdated and pose challenges in measurement.

  • Bad examples: “Recently, contributions have dropped”.
  • Adequate information: “By December 2023 contributions had dropped”.
  • Avoid: recently, lately, currently, today, presently, to date, 15 years ago, this country, here, there, somewhere, sometimes.

Appendix

[edit]

Learning from our mistakes: pages that should not be translated

[edit]

Sometimes, even if a page is perfectly translated, it may get deleted. This is not the fault of the translator: one article may be considered notable and high-quality by the Wikipedia community of one language, but get rejected by the Wikipedia community of another language.

Whenever this happens, we analyze the facts and adapt our processes to avoid repeating the same mistakes. As a result, we decided not to translate articles that meet any of the below criteria:

  • Medical articles without first ensuring that the original version meets the EN WP policies for Medical articles (e.g., that biomedical facts are supported by secondary sources rather than primary sources). For example, “Violence and Autism” was nominated for deletion despite being featured in French WP as too many of the key sources were primary sources. As no secondary sources existed that cover this exact topic (or couldn’t be found easily), salvaging the article would have been too complex
  • Legal articles that rely excessively on primary sources. For example, Contravention in French criminal law was deleted because most of the content relied on the actual law (e.g., the French constitution itself). Even when the law is paraphrased directly from the constitution, it can constitute Original Research. Thus, legal articles shouldn't be translated unless they also have a healthy number of secondary sources.
  • Risk of being considered an undue content fork. Most frequently when an article covers a sub-portion of a topic that is already well covered elsewhere. For example, the addition of Rococo painting was challenged because another user felt that it was best to keep the content within the various sections of the existing “Rococo” article.
Note

Content forks are tolerated, however, when they focus on an aspect that is

  • barely covered in the original article, and
  • where the concepts are distinct enough to justify separate pages.

For example, “Battle of Tordesillas (1520)” could be considered a content fork from “Revolt of the Comuneros”, but is sufficiently distinct and adds a lot more details than what was covered in the broader article about the revolt.

While there is no clear-cut definition of what is justified or not for content forks, we should avoid topics where the existing English pages are already well established: the lower the value-add, the higher the risk that other users disagree on whether the page should exist.
  • Large overlap with an existing article. Even if the article is not a “sub-element” of another article, large overlaps can be problematic. If there is any doubt as to whether the overlap is justified, we prefer to err on the side of caution and not to translate the page at all. For example, the article List of Vagrant Birds of the Iberian Peninsula was deleted due to its overlap with the article List of Birds of Spain. The Iberian Peninsula covers both Spain and Portugal, and Spain covers more than the Iberian peninsula, so technically the two lists were only partially overlapping, but the overlap was (1) very large and (2) from a zoological perspective, the community deemed that it was not adding much value to have two separate pages (as it doubles the maintenance effort).
  • Specific song/episode of an album or series. Such articles are likely to not meet the notability guidelines (e.g., notability guidelines for music). This is what happened, for example, to the article The Queen (Lady Gaga Song) which was deleted after being translated by an OKA translator.