GlotPress

Description

Many open source projects span regions, countries and dialects and need to support a variety of translations, GlotPress is here to help you collaborate online with your translators to ensure your users see your software in their native language.

GlotPress has two versions, a standalone version and this WordPress plugin version. At this time these two versions are functionally similar, but the plugin version is likely to start moving away from the standalone version in future versions. For the rest of this document, any reference to “GlotPress” should be taken as the plugin.

For more information about GlotPress, feel free to visit the channels listed below in the “Communication” section.

So who should use GlotPress?

Any developer of software that uses gettext, like WordPress theme or plugin authors. But that’s just the start, anyone who uses a gettext bases system can use GlotPress to help their translators collaborate.

This plugin wouldn’t be possible without all the hard work that has gone in to the standalone version of GlotPress and we’d like to thank all those who contribute to it.

Support

For basic support questions, please use the WordPress.org support forums.

If you have a bug or feature request please visit the issues list to help improve it in future.

If you’d like to work on something and there’s not currently an issue for it, open a new issue and describe your proposed change before jumping into coding.

Communication

Installation

Search for “GlotPress” in the WordPress.org plugin directory and install it.

After activating the plugin, GlotPress can be accessed via <home_url>/glotpress/

Manual Installation

  1. Upload the entire /glotpress directory to the /wp-content/plugins/ directory.
  2. Activate GlotPress through the ‘Plugins’ menu in WordPress.
  3. GlotPress can then be accessed via <home_url>/glotpress/

More Info

More information can be found in the GlotPress Manual.

FAQ

How can I contribute to GlotPress?

Drop by the GlotPress GitHub repository and look through the open issues and pull requests.

So who should use GlotPress?

Any developer of software that uses gettext, like WordPress theme or plugin authors. But that’s just the start, anyone who uses a gettext bases system can use GlotPress to help their translators collaborate.

How do I migrate my standalone GlotPress install to the plugin?

There’s a conversion document on the GlotPress wiki on how to convert your standalone install.

I’ve written a custom plugin for the standalone version, will it work with the plugin?

Short answer, no.

You will need to update the plugin to be a WordPress plugin. Instructions on how to do so can be found on the GlotPress Wiki.

Reviews

April 19, 2022
We have been using GlotPress for many years to organize the translations of the Advanced Ads add-ons. The plugin works wonderfully and helps us with this task. Thank you very much for your work. Joachim
April 1, 2018
I am impressed by this plugin, it is simple but really efficient.
October 7, 2017
Отличный плагин как для больших так и для маленьких проектов. Аналогов практически нет, тем более бесплатных. Минимум кода, максимум возможностей. Документация написано от и до. Спасибо, ждём новых версий!
August 19, 2017
I'm loving this developing plugin. I would love more features of course, am willing to wait for them at this stage.
December 20, 2016
I'd like to thank your contribution. It really help us to develop worldwide product. Though there are not many tool currently (tranlations memory, leave comments, etc) But I believe the powerful Open Source will make your project better.
September 24, 2016
Very useful plugin, I used it, when i was looking for a plugin for my own Wordpress. Because my coworkers do not speak english, I decided to take part in the translation process of plugin onto Wordpress.org. I discovered a very powerfull and useful tool. Also, i would like to request an specific add in order to include a "glossary" plugin (similar than WebLate or Transifex).
Read all 12 reviews

Changelog

This project adheres to Semantic Versioning. All notable changes to this project will be documented in the CHANGELOG.md file on GitHub.