iFixit Translator Guidelines

At iFixit, we believe everyone should have access to free repair knowledge, no matter what language they speak.

For years, our incredible community of volunteer translators has helped make that possible. You've translated thousands of repair guides and wikis, shared your expertise, and helped people around the world fix their stuff.

Now, you've got a new teammate: Translation Bot!

As our library of repair knowledge keeps growing, it's become increasingly difficult to keep up with the demand for translations. People searching for repair instructions in their own language have often found nothing, even when the information they needed was available in another language.

After all, if you can't find the fix, you can't fix the thing.

That's why we introduced Translation Bot. It uses AI and iFixit's technical glossary to generate draft translations of repair guides and wikis, helping us make repair information available to far more people, much faster.

But making repair knowledge available is only half the job. Making sure it's accurate, understandable, and safe to follow is just as important.

Translation Bot can produce impressive results, but it can also make mistakes. It might misunderstand a technical term, miss a subtle distinction, or translate a repair instruction in a way that sounds perfectly natural but means something entirely different.

That's where you come in!

Translation Bot isn't here to replace our volunteer translators. It's here to help make your contributions go further.

Now that most of our repair content has an initial translation, our biggest priority is reviewing, refining, and improving those translations.

You no longer need to start from scratch to make a meaningful contribution. Instead, you can focus your time and expertise where they make the greatest difference: ensuring that repair information is accurate, technically sound, and genuinely helpful to readers in your language.

Translation Bot doesn't make final editorial decisions or earn reputation points, badges, or recognition intended for human contributors. Your improvements also become valuable context when the bot needs to update a translation.

Whether you review an entire guide, correct a confusing instruction, or fix a single technical term, you're helping people repair with greater confidence.

Translation Bot helps us reach more people. You help make that knowledge worth trusting.

This is still an evolving project, and your feedback matters. We're continuing to evaluate and improve how automatic translation works, with the goal of combining the reach of AI with the expertise of our community.

Together, we can make repair knowledge not just available in more languages, but better in every language.

1. Accuracy comes first. Make sure every translation faithfully reflects the original. Pay particular attention to repair instructions, safety warnings, technical terminology, and measurements.

2. Write naturally and clearly. Use modern, accessible language that people actually understand. Avoid awkward literal translations, unnecessary jargon, and overly complicated sentences.

3. Use AI wisely. AI and machine translation are excellent starting points, but they can make mistakes. Always check their output against the original and use your own judgment.

4. Think like a repairer. Would someone following these instructions know exactly what to do? Make sure the translated content is complete, understandable, and safe to follow.

There are several ways to help improve iFixit in your language.

Most iFixit guides and wikis now have automatically generated translations, but many still need human review.

Visit Translate iFixit to find content awaiting review in your language.

Compare the translation with the original, correct any mistakes, and make sure the instructions are accurate and understandable.

You don't need to rewrite every sentence or review an entire page in one sitting. Even a small correction can make a difference.

You can also improve translations that have already been edited by community members.

If you notice outdated terminology, unclear instructions, incorrect information, or changes that haven't been reflected from the original, you're welcome to make corrections.

Some guides and wikis may still be missing in your language.

You can translate these manually or use AI to help create a first draft. In either case, make sure the final result accurately reflects the original.

For detailed instructions, see How to Manually Translate Guides and How to Manually Translate Wikis.

Menus, buttons, messages, and other website interface elements are translated separately using Crowdin.

See the Crowdin section below for more information.

Reviewing machine-generated translations is often called post-editing. It means checking a draft translation against the original and correcting anything that's inaccurate, unclear, or unnatural.

The goal isn't to rewrite the translation simply because a machine created it. If a sentence is already accurate, clear, and natural, leave it as it is.

Focus on changes that genuinely improve the reader's experience.

1. Choose a language. Open Translate iFixit and select the language you want to contribute to.
2. Find content awaiting review. Look for automatically translated guides or wikis that haven't yet been reviewed by a person.
3. Open the translation. Read the translated content and compare it with the original, using images and surrounding steps for context.
4. Correct any problems. Prioritize errors that affect meaning, safety, or technical accuracy. Improve awkward or unclear phrasing where necessary.
5. Save your changes. You don't have to review the entire page before saving a useful improvement.

If you decide to review an entire guide or wiki, check all its content against the original, including titles, summaries, warnings, prerequisite instructions, and individual steps or sections.

Remember: A human correction to one part of a guide doesn't necessarily mean the rest of the translation has been checked.

1. Safety and repair instructions

These are your highest priority. Even a small mistranslation can change the meaning of an instruction or create a safety risk.

Pay particular attention to:

• Negations: "Do not disconnect" must never become "Disconnect."
• Directions: left versus right, clockwise versus counterclockwise, push versus pull.
• Sequence: make sure the steps and actions are described in the correct order.
• Safety warnings: preserve all precautions involving batteries, electricity, heat, sharp tools, or fragile components.
• Tools and parts: make sure the correct components are identified.

2. Technical terminology

AI sometimes chooses technically incorrect terms or translates expressions too literally.

Check tool names, components, connectors, and repair procedures against our Dictionary of Technical Terms.

Use the established terminology consistently throughout the translation.

If you come across an incorrect or missing glossary entry, please let us know. Your feedback can help improve future automatic translations, too.

3. Accuracy and completeness

Compare the translated text with the original to make sure that:

• No important information has been omitted.
• No information has been invented or added.
• Numbers, specifications, and measurements are correct.
• All instructions communicate the intended action.
• Links, references, and formatting are preserved.

A translation can sound perfectly natural while being factually or technically wrong. Always check the meaning, not just the language.

4. Natural language and readability

Once the information is correct, make sure it reads naturally in the target language.

Avoid awkward word-for-word translations. Prefer clear, concise sentences that a repairer can easily understand.

Preserve the tone and meaning of the original. Don't unnecessarily rewrite sentences that are already correct.

5. Localization

Adapt content to the conventions of the target language where appropriate.

This may include punctuation, number formatting, units of measurement, or culturally specific references.

Be careful not to alter technical specifications or introduce inaccuracies when localizing.

Sometimes, the problem isn't the translation. The original guide or wiki may contain an error, unclear wording, or outdated information.

Whenever possible, correct the original first rather than simply fixing its translation.

That way, the improvement can benefit readers in every language and prevent the same mistake from appearing in future translations.

If you're unsure about the technical content, ask for help rather than guessing.

Translation Bot generates draft translations of guides and wikis directly on iFixit.

It uses our technical glossary and follows formatting rules to help preserve terminology, structure, and links.

Its contributions are clearly attributed, so readers and editors can recognize automatically generated content.

Translation Bot doesn't make final editorial decisions, replace community review, or receive reputation points and badges intended for human contributors.

Your corrections are preserved while the corresponding source content remains unchanged.

When the original is updated, Translation Bot uses the existing translation, including human improvements, as context for generating the updated version.

This helps retain previous work, but it doesn't guarantee that every sentence will remain unchanged. Updated passages may need further review.

You're welcome to use tools such as ChatGPT or DeepL when creating or improving translations.

They can help you understand unfamiliar expressions, research technical terminology, or suggest more natural phrasing.

However, AI-generated text must always be checked before you submit it as reviewed work.

When using these tools:

• Compare the output with the original text.
• Check terminology against the iFixit glossary.
• Preserve technical details, warnings, and instructions.
• Make sure no information has been omitted or invented.
• Review the result for natural language and readability.
• Never submit raw, unchecked AI output as a translation you've personally reviewed.

Translation Bot is an ongoing project. We're testing and evaluating how well it works, and feedback from experienced translators is particularly valuable.

If you notice recurring mistakes, problematic technical terminology, or systematic issues affecting multiple translations, please contact us at translate@ifixit.com.

Your expertise can help improve not just one translation, but the system that produces them.

You don't need to be a professional translator to contribute to iFixit.

However, you should be comfortable reading and writing in your target language and understand the source language well enough to recognize mistranslations.

This is particularly important when reviewing automatic translations. A sentence can sound perfectly fluent while communicating the wrong instruction.

If you're working outside your area of expertise, research unfamiliar terminology or ask someone with relevant technical knowledge.

Don't hesitate to ask other translators for advice if you're struggling with a particular phrase or technical concept.

Our goal is for translated content to read as if it were originally written for its audience.

Use clear, approachable language appropriate for your target language.

iFixit's tone is generally friendly, direct, and helpful. Think of how you would explain a repair to a friend.

However, conventions differ between languages. Choose the appropriate level of formality for your audience and maintain it consistently.

Avoid unnecessarily formal or overly casual wording that would sound unnatural in the target language.

Prefer modern, commonly understood words and expressions over outdated or overly literary language.

Use terminology that reflects current usage, particularly when referring to electronic devices, tools, and repair procedures.

iFixit content sometimes uses humor, informal language, or a distinctive writing style.

Try to preserve the tone and personality of the original without translating expressions too literally.

The goal is to communicate the same meaning and spirit in a way that feels natural to readers of your language.

For technical instructions, clarity should always take priority over stylistic flourishes.

Idioms, puns, metaphors, and culture-specific expressions often don't work when translated word for word.

Look for an equivalent expression in the target language that conveys the same meaning and tone.

If no natural equivalent exists, choose a clear translation that communicates the intended meaning, even if it's less colorful than the original.

Our name is always written iFixit. Don't translate it or change its capitalization.

People's names: Preserve names in their established form. For languages using other writing systems, follow conventional transliteration or transcription practices where appropriate.

Places: Use the established name of a location in your target language. If no conventional name exists, use an appropriate transliteration.

Device names: Follow iFixit's established naming conventions. See our Device Nomenclature reference for guidance.

Use the punctuation conventions of your target language while preserving the meaning, structure, and readability of the original.

Use standard Unicode characters and avoid platform-specific characters that may not display correctly for all readers.

You may adapt units of measurement to make them more understandable to your audience, but always make sure conversions are accurate.

For technical specifications, preserve the precision and meaning of the original. Don't round values in ways that could affect a repair.

Use the correct decimal separators, thousands separators, and spacing conventions for the target language.

Where appropriate, use a non-breaking space between numbers and units to prevent them from separating across lines.

If a guide or wiki doesn't yet have a translation in your language, you can create one manually.

Open Translate iFixit, select your target language, and find content that needs translation.

Translate the guide information and any prerequisite guides before working through the individual steps.

Use the accompanying images to understand the actions being described.

Preserve all safety warnings, measurements, tool names, and other important technical details.

For detailed instructions, see How to Manually Translate Guides.

Compare each translated field with its corresponding source content.

Preserve the wiki structure, formatting, and markup. Check links and adapt them for your audience where appropriate.

For detailed instructions, see How to Manually Translate Wikis.

When reviewing or translating links, first check whether the linked content is useful and accessible to your target-language audience.

Where suitable, link to an equivalent page in the target language. If no equivalent exists, you may retain the original link or use another reliable resource that serves the same purpose.

Preserve the underlying link syntax. In iFixit wiki markup, structural elements such as link, guide, page identifiers, and other markup must not be translated.

For example, in a wiki link containing a page title followed by a vertical bar and display text, preserve the original page reference and translate only the display text, unless you are intentionally replacing the destination.

Use the editor's link-insertion tools where possible to avoid damaging the markup.

Links should generally open in the same browser tab rather than forcing a new tab.

For technical details, consult the existing Wiki Formatting and Syntax and Links reference pages.

Repair guides and wikis are translated directly on iFixit. Website interface text, including buttons, menus, system messages, and other interface elements, is translated through Crowdin.

Crowdin is an online collaborative translation platform where translators can contribute, review suggestions, and discuss terminology.

Create a Crowdin account and join the iFixit translation project.

We recommend familiarizing yourself with Crowdin's interface and translation tools before you begin.

Our goal is for the entire site to sound consistent in each language, even when many different translators contribute.

Use the glossary, translation memory, and existing approved translations as references.

If you're unsure how a phrase should be translated, use Crowdin's comments to discuss it with other translators or ask the iFixit translation team for context.

Some Crowdin strings include comments explaining where they appear on the website.

When more context is needed, you can try finding the phrase on iFixit or using our in-context translation tool.

For strings that can't easily be located, ask for clarification through Crowdin or email a screenshot to translate@ifixit.com.

Crowdin organizes interface strings into different files and categories.

The core interface strings, including those in Base.po, are especially important because they affect frequently used parts of the website.

Even when a language reaches 100% completion, new strings may be added as the site evolves. Check back regularly for new or updated content.

Before submitting a string:

• Read it again and check its meaning.
• Make sure it sounds natural in the target language.
• Verify terminology and consistency with existing translations.
• Preserve all placeholders, variables, and formatting.
• Ask for context if the meaning isn't clear.

Crowdin provides a collaborative review process, so translators can help identify and correct problems.

Crowdin's Translation Memory lets you find how words and phrases have been translated previously.

This is helpful for maintaining consistency, but an older translation isn't automatically the best or most current choice. Check the context before reusing it.

Crowdin also provides a glossary with suggested translations and, in some cases, definitions or additional context.

Use the established glossary terminology whenever appropriate and flag errors or missing terms for review.

Some interface strings contain placeholders that are replaced with information such as numbers, usernames, or links.

These placeholders must remain intact.

For example:

I Have %1 Reputation

Here, %1 will be replaced with a value. You may adjust the sentence structure for your language, but you must preserve the placeholder exactly.

Don't insert spaces inside it, change its characters, or remove it.

Another example:

This is a %1Link%2 to Google

In this case, the placeholders may control formatting or a hyperlink.

Preserve the placeholders and their required relationship to the surrounding text. If you change their position to suit the grammar of your language, make sure the resulting string still functions correctly.

• Small placeholder markers or symbols may appear in the Crowdin interface. These aren't necessarily part of the translated text.
• Crowdin validates strings for missing placeholders and other formatting problems.
• Occasionally, validation may incorrectly interpret characters immediately following a placeholder as part of it. Check the source carefully before deciding whether to save despite the warning.
• If you're unsure, ask for help rather than changing or removing a placeholder.

Some interface strings contain HTML or XML formatting tags.

Don't translate the tags themselves, and don't remove or alter them unless explicitly instructed.

If you encounter unexpected or broken markup, report it through Crowdin or contact translate@ifixit.com.

There are many useful dictionaries, terminology databases, and reference materials available online.

For general translation questions, you may find these resources helpful:

Bilingual and general dictionaries

• LEO
• Linguee
• Cambridge Dictionary
• Merriam-Webster

Technical terminology

• Restarters Wiki — repair-related terminology and background information
• iFixit's own technical glossary, available below

Thesauri and writing resources

• Thesaurus.com
• Power Thesaurus — Synonyms, antonyms, and related expressions to help explore different shades of meaning and tone in English.
• Collins Thesaurus

These resources can help you research unfamiliar expressions, but remember to check terminology against the actual repair context.

Researching technical terms can be challenging and time-consuming. To make sure we’re consistently using accurate terms throughout our platform, we invite you to use our glossary of technical terms that we have put together over the years. Please find your language pair here:

iFixit Technical Glossary

The XLSX files for all language pairs can be found in this Google Drive folder.

Simply open the web-based file in your browser alongside our translation interface on your computer. These files are synchronized with our main glossary, so they're updated automatically to include new terms.

If you prefer using your phone, you can upload the CSV or XLSX file to your preferred dictionary app on Android or iOS.

These are the apps we recommend:

• WordTheme (available for Android and iOS): See our existing tutorials for importing dictionary files on Androidand iOS.
• Own Dictionary with Gifs (Android only): See our dictionary import guide.
• My Dictionary: polyglot (Android and iOS): Detailed instructions on how to use the app and import data can be found on the app's website.

These apps also allow you to study words with flashcards and word puzzles.

If you have questions or suggestions about terms in our Technical Dictionary, send an email to translate@ifixit.com, add a comment below, or join the discussion about translating iFixit on Meta.

We regularly add new terms to our dictionary. The glossary files above are updated to include the latest changes and additions, so make sure to check for updates from time to time.

If you know of another app that allows importing a custom dictionary, let us know!