As the end of the year is near…

As the end of the year is near, I want to share something for future thinking:

There are more languages coming with more than one language variant (mostly default and formal). At the moment de_DE and pt_PT have two variants. nl_NL is the latest language that has added a new (formal) variant.

But at the moment GlotPressGlotPress GlotPress is the translation management software that powers More information is available at is not optimized to handle that well. We should look for optimizations to handle languages with more than one language-variant better.

What would be helpful?

  • A side-by-side-view for example would be great. But do we have enough space/width?
  • Or should we add the variant(s) below the default translation? Could be very long/confusing if you have plurals, which have already more than one textarea …
  • Or a copy from (x) feature – where (x) is a select with all variants, suggested here #432
  • Adding a diff view, to just see the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. which differ between the variants …

This is a problem for the future of translating WordPress and I want to start the discussion about possible solutions. This has not to be solved fast, but we should think about it. If GlotPress is handling this better, I think, more languages will use more variants.

Do you have an idea? Want to make a design mockup? Every help is appreciated.

Maybe we can help making GlotPress better for handling more language variants in 2016.
This would be great!

#formal, #glotpress, #variants

Hello If possible I’d like to add a…


If possible I’d like to add a Dutch (NL) ‘formal’ localizationLocalization Localization (sometimes shortened to "l10n") is the process of adapting a product or service to a particular language, culture, and desired local "look-and-feel." repositoryWordPress Localization Repository The WordPress Localization Repository at is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details..

Could someone tell on how to do this best?

#formal, #nl_nl, #request