The JSON opens but still says “1 files”: review the plural

Opening the file does not establish that the sentence is right

“1 files” retains a number and a recognizable noun, but English agreement needs “1 file.” Before approving a resource, check what the reader will see for one item, several items and zero. A JSON file opening successfully or preserving a placeholder does not answer that language question.

Iria Localization Studio works with JSON and RESX resources and checks supported structures, including placeholders and plurals. Its documentation separates those checks from meaning review. This guide uses a small sample to examine that boundary; it does not present an automatic grammar certificate.

Two keys that expose the mistake

This is an invented English resource sample. The names files.one and files.other are labels for this example. They do not promise that any application automatically selects a branch from those names.

{
  "files.one": "1 file",
  "files.other": "{count} files"
}

A proposed Spanish translation could retain both keys and the placeholder while still being wrong:

{
  "files.one": "1 archivos",
  "files.other": "{count} archivos"
}

The first Spanish sentence should read “1 archivo.” The second supports “2 archivos” and “0 archivos” in this file-list example. Do not replace {count} with a fixed number while correcting the wording: the application still needs to supply its actual quantity.

Review the wording without inventing the application’s selector

Sample case	Spanish wording to review	Human question
One item	1 archivo	Is the noun singular?
Two items	2 archivos	Do the number and plural agree?
Zero items	0 archivos	Is the empty state clear?

These are expected outputs to review. Your application must select the appropriate resource and substitute the quantity. The JSON does not implement that logic by itself. Reading the phrases in a note is not the same as testing your interface.

If your project uses ICU messages rather than separate keys, review its branches and numbers through the relevant workflow. Do not paste this pair of keys expecting it to convert or replace an ICU contract. Other languages need their own category and wording review.

A useful pass before export

1. Add context: this is the number of files in a list, not file size or a save action.
2. Preserve the keys and placeholders the application expects.
3. Correct agreement and read all three full phrases.
4. Inspect Studio’s review obligations and blockers alongside its structural checks.
5. Review the result in your application before treating it as accepted for real use.

New Studio projects require human approval by default. Automatic export is an explicit choice and does not remove reviewable import, ICU or access-key obligations. Passing structural checks must not become a promise that every quantity is expressed correctly.

Where to go next

Weblate and Crowdin’s ICU documentation were read as localization references on 25 October 2026. Their workflows are not attributed to Iria, and these examples are original.

Read the public Localization Studio workflow and Iria’s product facts. Iria is an available paid Windows application. Models translate on the PC, while licensing checks and downloads use the network. To evaluate your case, prepare a small sample of your own resources without private data and keep the three output phrases you intend to check.