Using Gloty
Managing translations
Gloty → Translations is a searchable table of every string on your site, in every target language. It is where you review machine output, correct anything that reads wrong, and re-queue work.
Finding a string
The table has four filters that combine:
A good review routine. Filter to one language, status Synced, and search for your product or brand terms first — those are the strings where a wrong translation costs the most. Anything you correct is protected from then on.
Reading the table
| Column | What it tells you |
|---|---|
| Pair | Source and target language for this row. |
| Status | Pending, Processing, Synced, or Manually edited — plus a Stale marker where the source has changed. |
| Original | The source text. Block content is shown as readable text rather than raw markup. |
| Translation | The current translation, editable in place. |
| Context | Where the string came from — see below. |
| Updated | When this row last changed. |
Context labels
| Label | Meaning |
|---|---|
| Post — content, part N | A segment of post or page content. Long content is split into parts so blocks and markup survive translation. |
| Post / Term | A field on a post or taxonomy term — title, excerpt, term name, description. |
| Theme / UI string | An interface string from your theme, a plugin, or WordPress core — or text captured from the rendered page, such as Customizer content. |
| Site option: … | A site-level value such as the site title or tagline. |
Editing a translation
Click a translation cell to edit it in place, or use Edit for a dialog with more room — useful for long content segments. Save and the change is live immediately: the row is marked Manually edited and the affected pages are purged from your page cache.
An empty translation is not accepted in either the inline field or the dialog. If you want a string to fall back to the source text, delete the row instead.
Manual edits are protected
Machine sync never silently overwrites a human edit. Once a row is Manually edited it keeps your wording even when the same string is retranslated elsewhere or the source is re-scanned. Incoming translation results are dropped for that row rather than applied.
The protection covers automatic sync. Two deliberate actions still replace your text: selecting the row and choosing Translate selected, or deleting the row and letting it be rediscovered. Both are ways to hand a string back to the machine on purpose.
What to keep intact
When you edit by hand, preserve anything that is not prose. Gloty asks the translation engine to do the same, and validates the result:
- HTML tags — keep the same tags in the same order.
-
Placeholders such as
%s,%1$s, and{0}— these are filled in at runtime. A translation whose placeholders do not match the source is rejected and the source text is shown instead, so a bad placeholder cannot break a page. - Shortcodes — copy them verbatim.
Bulk actions
Select rows with the checkboxes, then use the bar above the table.
Translate selected discards manual edits on the rows you select. Re-queuing resets a row to Pending and clears its current translation — including a translation you wrote by hand. Automatic sync will never do this, but this button asks for it explicitly. Filter to Status: Synced before selecting if you want to leave your corrections untouched.
Re-queuing costs quota. Every re-queued string is translated again and its characters are billed again. Re-translate deliberately — for a genuinely changed source or a bad batch — not as a general refresh.
Deleted rows that come back
If a string is still present on your site, deleting its translation only clears the translation — the string is rediscovered the next time a page containing it renders, and re-queued. That is intended.
Junk strings are a different case. Machine-generated text — a "shop by brand" list, for instance — used to reappear endlessly. Gloty now recognises and skips those patterns, so deleting such a row sticks. 1.10.1 / 1.11.1
To stop a legitimate but unwanted region from being translated at all, add a CSS selector to Exclusion selectors on Gloty → Settings instead of deleting rows repeatedly.
Handling stale translations
When you edit a post, its existing translations are marked stale rather than discarded — visitors keep seeing the previous translation instead of suddenly reverting to your source language.
To refresh them:
- Filter by Stale only, and optionally by language.
- Review what actually changed.
- Select the rows and choose Translate selected.
Text that is genuinely new — a paragraph you added, a newly published post — is queued automatically and needs no action from you. Re-queuing is only for rewriting text that already has a translation.
Working per language
Language coverage is summarised on Gloty → Overview, which shows how many strings are translated per language and how much is still pending. Use it to decide where review effort is worth spending before you promote a language.