---
title: "Languages"
description: "Bundled Free and Pro translations, locale codes, loading behaviour, translation quality and how to report an issue."
url: "https://maksut.net/price-anchor/docs/languages/"
language: "en-US"
datePublished: "2026-10-10T08:40:01+00:00"
dateModified: "2026-10-10T08:40:01+00:00"
---

# Languages

English is Price Anchor’s source language. Both Free (text domain `price-anchor-for-woocommerce`) and Pro (text domain `price-anchor-pro`) also ship bundled WordPress translation catalogues for the following 12 locales:

| Locale | Language |
| --- | --- |
| `tr_TR` | Turkish |
| `de_DE` | German |
| `es_ES` | Spanish (Spain) |
| `fr_FR` | French |
| `ru_RU` | Russian |
| `ar` | Arabic |
| `pt_BR` | Portuguese (Brazil) |
| `pl_PL` | Polish |
| `it_IT` | Italian |
| `fa_IR` | Persian |
| `az` | Azerbaijani |
| `uk` | Ukrainian |

## How WordPress chooses a translation

Price Anchor loads the catalogue that matches the current WordPress locale. A user-specific admin language takes precedence when WordPress supplies one; otherwise the site language is used. There is no separate language selector inside the plugin. For a locale outside the list above, the plugin stays in English.

Free and Pro register their bundled catalogues when WordPress initialises. Free can also receive a newer community language pack through the normal WordPress.org translation updates, which then takes precedence for Free. Pro does not depend on WordPress.org: its translations always come from the files bundled with the add-on.

Arabic and Persian follow WordPress’s right-to-left admin layout. Currency codes, placeholders and numerical values remain machine-readable inside translated sentences.

A few environment notices stay in English on purpose. They appear only when a required component is missing — for example WooCommerce is not active — and can run before WordPress loads translations.

## Translation quality

Every catalogue is complete against the current source text, keeps each placeholder exactly as written and is checked to load inside WordPress. Russian, Polish and Ukrainian use their three plural forms; Arabic uses the six-form WordPress rule.

The bundled translations began as machine-assisted translations. Turkish financial and admin terms, such as *kur*, *fiyat artışı* and *satın alma maliyeti*, have had an additional terminology review. No locale has had a full review by a native editor yet. Before you rely on a translated screen for accounting work, or quote its wording to your own customers, check the terms that matter to you against the English source.

## Reporting a translation issue

If wording is unclear or unnatural, [get in touch](https://maksut.net/contact/) with the locale, the screen where it appears, the English source text and your suggested translation. Financial terms such as rate, markup, margin and acquisition cost benefit especially from local merchant review.