ReviewFold
Guide · Reading across languages
How to Analyze Multilingual App Reviews
A translation is a reading, not a replacement. Once you replace the sentence, the negation, the payment condition and the hesitation go with it — and the theme that survives is your translator’s, not your reviewer’s. This page keeps the original in the room.
01 · The order that keeps evidence
Store the original before you translate anything.
The sequence is unglamorous and it decides whether you can defend a theme later.
- 1
Keep the review as published
Original characters, original spelling, original punctuation. If the review has three lines with no full stops, keep three lines with no full stops.
- 2
Attach a stable ID and the store it came from
The ID is what lets you find the sentence again. The storefront is what stops a US review written in Spanish from being filed under Mexico.
- 3
Put the translation in a separate field
Never overwrite. The two fields answer different questions — what was said, and what you understood — and you will need the first one when the second is questioned.
- 4
Name who translated it
“Editorial translation” is a different claim from “translated by the product”. The label is the honesty of the whole page.
02 · What it looks like when it is done
Five reviews, four languages, one storefront.
Each record keeps the original above the reading, then names the task and the part that is still uncertain. Ratings and dates are the ones the store reports.
-
ESSpanish
DramaBox · US App Store ·
“Las series están muy bien pero debería ser fácil desbloquear lo capítulos”
Editorial translation
“The series are very good, but unlocking the episodes should be easy.”
- Task
- Watch the episodes already in front of them.
- Still ambiguous
- “lo capítulos” is a misspelling of “los capítulos”. And a one-star rating opens with praise — the star and the sentence point different ways.
-
ESSpanish
DramaBox · US App Store ·
“No me gustó por qué hay que pagar obligatoriamente después de unos episodios es obligado pagar eso no me gusta”
Editorial translation
“I didn’t like it because you have to pay obligatorily after a few episodes; paying is forced, and I don’t like that.”
- Task
- Keep watching after the free episodes.
- Still ambiguous
- “por qué” is written where “porque” is standard. The obligation is repeated twice, which is emphasis rather than two separate rules — and no price is mentioned.
-
PTPortuguese
Remini · US App Store ·
“…é uma luta pra conseguir editar uma foto. Mesmo assistindo os milhares de anúncios ainda dar erro.”
Editorial translation
“…it’s a struggle to manage to edit a photo. Even after watching thousands of ads, it still gives an error.”
- Task
- Edit one photo and get a result.
- Still ambiguous
- “dar erro” is colloquial for “dá erro”. “Milhares” is emphasis, not a count. The excerpt starts mid-sentence, so the complaint before it is missing here.
-
ARArabic
Remini · US App Store ·
يوجد فيه الكثير من الأعلانات
بصعوبة يتم معاجلة الصور بسببها
اجعلوه مجانيEditorial translation
“It has a lot of ads; processing images is difficult because of them. Make it free.”
- Task
- Process an image with less interference from ads.
- Still ambiguous
- “معاجلة” is written for “معالجة”, and “الأعلانات” for “الإعلانات”. There is no punctuation, so the sentence breaks above are an interpretation.
-
TRTurkish
Remini · US App Store ·
“mükemmel” / “gerçekten çok güzel”
Editorial translation
“excellent” / “really very nice”
- Task
- Not described.
- Still ambiguous
- The object of the praise is unspecified. Translating this review perfectly still leaves you with no task, no blocker and no next step.
Translations are editorial English renderings, reviewed with AI assistance rather than independently verified by native speakers. Check the original before relying on a subtle distinction. The originals are reproduced as published, including their spelling; nothing has been corrected in place. ReviewFold is not affiliated with DramaBox, Remini or their publishers.
03 · The decision that changes the count
Same theme, different stance — or same words, different product.
Two reviews above look like one problem in English. Whether they belong in one group is a judgement you have to make explicit.
Keep together
“debería ser fácil desbloquear lo capítulos”
This reviewer asks for easier unlocking. The sentence does not establish acceptance of payment or a preferred unlocking method.
Keep apart
“hay que pagar obligatoriamente después de unos episodios”
This reviewer objects to the payment model itself. Both can sit under a broad unlocking theme, but they should not be counted as two requests for the same change.
The same trap is easier to fall into across products. The Portuguese and Arabic reviews both concern Remini. One reports an error even after ads; the other says ads make processing difficult. They can inform a broad ads-and-editing theme, while keeping these different claims separate. Cross-product comparisons must also preserve the App behind each review; similar language does not establish a shared cause.
04 · Reading the translation against the original
Four things a clean translation quietly drops.
- Negation
“No”, “não”, “لا”, “değil”. A dropped negative turns a complaint into praise, and it can reverse the meaning of a short review. Read the original for the negative before you accept the reading.
- Conditions
“After a few episodes”, “even after watching”, “only if”. These words carry the payment model and the workaround. Check that a fluent translation has retained each condition.
- Intensity and idiom
“Uma luta”, “milhares”, “mükemmel”. Hyperbole is information about feeling, not about quantity. Keep it in the quote, and do not turn it into a number in your notes.
- Typos and missing punctuation
Keep them in the original and name them in the note, as above. Silently correcting them makes the quote unverifiable for the person who wrote it.
If a sentence cannot be read with confidence, leave it in the original with a note. An honest blank is cheaper than a confident mistranslation that becomes a ticket.
One distinction worth keeping
Multilingual is not multi-region.
All five reviews on this page were collected from the US App Store listing. Four languages, one storefront.
- Language follows the reviewerA Spanish review on the US storefront is a US review. Filing it under Spain changes the population without changing a single sentence.
- Region follows the storefrontOne report covers one app in one storefront. Two storefronts are two reports, and their reviews are not merged.
- No in-product translationThere is no per-review translate button and no promise that every language has been checked. Original text is what gets stored.
- No cross-store mergingCombining the same app across regions is not something a single report does, so no page here should imply it.
05 · Writing it up
An English brief still has to point back to the sentence.
When the brief is written in English, the themes will be in English too. That is fine as long as each theme keeps its original excerpts — otherwise a reader who speaks the language has no way to disagree with you.
Practically: put the original quote in the theme, the translation underneath it, and the language tag on the quote rather than in a footnote. Keep the review ID with both. Three fields, and the theme survives being questioned.
If you are comparing what two products get right, the competitor review guide covers the sampling side; the language handling is the same, and the rule about not merging different products applies twice over.
Current support, stated plainly
- Apple App Store: US and Canada. Google Play: US.
- Up to 200 recent public reviews per report.
- One app and one region per report; no cross-app or cross-region merging.
- Reports keep the original review text; no automatic per-review translation.
- No claim that every language has been tested.
Originals kept
Grouped in English, quoted in the original.
A report groups a recent sample and keeps each excerpt in the language it was written in, so the reading can be checked against the sentence.