Translate

We'd love your help translating BleachBit into your native language! While it can be time-consuming, the web-based interface makes the process smoother.

What you'll need:

  • Strong English comprehension
  • Excellent writing skills in your native language
  • Willingness to translate around 2,300 English words (as of August 2024). The workload might be less if someone has already begun translating in your language. There's no pressure to translate everything; feel free to contribute as much or as little as you'd like.

Since February 2022, the translation platform has migrated from Launchpad to Weblate.

Procedure

Please do not submit translations to GitHub as a pull request. Instead, follow the procedure outlined below:

Visit the BleachBit page on Weblate, create an account, and follow the instructions provided.

Verifying Translations

There are several methods for verifying your translation. If you are confident in your work, you may skip these steps.

  • Use the spell checker in your web browser as you type new translations.
  • Download your translation and open it in your office application. In Weblate, select the language, click the "Files" tab, choose "Customize Download," and select CSV or XLSX. Proofread the translation in the spreadsheet or paste it into a word processor. Make any necessary edits in Weblate.
  • Download the translation and load it into BleachBit to see the translations in context.
  1. Go to the list of languages.
  2. Select the language.
  3. Click the "Files" tab and choose "Customize Download."
  4. Choose gettext mo.
  5. Rename the file to your locale code (e.g., Spanish is es.mo).
  6. Move this file to /usr/share/locale/(your locale code)/LC_MESSAGES/ (Linux) or c:\Program Files (x86)\BleachBit\share\locale\(your locale code)\LC_MESSAGES (Windows).
  7. Start (or restart) BleachBit.
  • If you already have an updated .po file on your computer, use a .po to .mo file converter, and then follow the procedure above.
  • Shortly after committing translations to Weblate, the AppVeyor CI system will rebuild the whole application and provide a Windows build at the BleachBit CI site. Use the installer or portable version to test your translations.
  • Understanding Context

    If you are unsure how to translate a string, you have several options:

    • Download and run BleachBit to understand the context. Use the latest stable or CI build.
    • Look for hints. Hints in the source code are copied to the .pot. Launchpad automatically displayed them like what follows. Launchpad is no longer used. FIXME: Does Weblate show the hints too? Launchpad showing translation tip for the word 'vacuum'
    • If you have any programming skills, cross-reference the source code. To locate the right file, open the string in Weblate, and look on the right sidebar for "source code location."
    • Ask in the forum or open a GitHub issue. Request to add a hint to the source code (which displayed in Launchpad, maybe in Weblate too), modify the English string, provide a screenshot, or record a video of the application. Weblate can attach screenshots to strings.

    License

    Translations must be licensed under the GNU GPL v3+, the BSD license (without the advertising clause), or both.

    Updates

    BleachBit is actively developed, so please check back periodically for new strings to translate. Here are some options:

    • Regularly visit Weblate to check for untranslated strings.
    • Subscribe to RSS feeds from Weblate.
    • Follow BleachBit on Facebook or Twitter for release announcements.
    • Enable notifications for beta releases in the BleachBit application, and monitor the application for notices of application updates.