Hungarian review, proofreading and linguistic QA
A second linguist's check on Hungarian content that is already translated: accuracy against the source, terminology, tone and the small errors that survive a first pass. This is the work I do as lead reviewer for Binance.
Three different jobs, often confused
- Review — bilingual check against the source: accuracy, omissions, terminology, register, style guide compliance. Delivered with tracked changes and comments.
- Proofreading — monolingual check of the Hungarian: typos, grammar, punctuation, number and date formats, consistency.
- Linguistic QA — the text checked in context, in the built app or page, where length limits, truncation, broken variables and strings that make no sense out of context finally show themselves.
Ask for the one you need. If you are not sure, tell me what you are worried about and I will say which of the three answers it.
What you get back
For review and proofreading: your file with tracked changes, plus comments explaining anything that is a judgement call rather than a correction. For LQA: each finding logged with its location, a severity, a category and a proposed fix, in your bug tracker or a sheet, whichever you use.
Where a change is a matter of preference rather than correctness, I say so. A review that rewrites a competent translation into the reviewer's own voice wastes everyone's time and sours the relationship with the original translator.
Why a crypto specialist for review
Most Hungarian review errors in crypto content are not grammar. They are terminology decisions that do not match how Hungarian users actually talk about the product, inconsistency between the app and the help content, and translations that are correct in the abstract but wrong for the screen they appear on. Catching those needs someone who knows the subject, not only the language.
Experience behind it
I have been lead reviewer for Binance since 2015 on Hungarian content: website pages, articles, UI, the mobile app and marketing. I also review content for Welocalize clients including WizzAir, Apple, Vinted and FedEx, and for Microsoft Xbox and Microsoft Learn through Jonckers.
Questions agencies ask
What is the difference between review and LQA?
Review compares the Hungarian against the English source in the file. LQA checks the Hungarian in context, in the running app or page, where truncation, layout and variables cause problems a file-level review cannot see.
Can you review a translation done by machine translation?
That is post-editing rather than review, and it is priced and handled differently. See the MTPE page.
Do you provide scored LQA reports?
Yes. Findings are logged individually with severity and category, in your own LQA framework if you have one.
Can you review content you did not translate?
Yes, that is the usual case. Review is a second pair of eyes on someone else's work.
Need a quote?
Send the files or a word count, the deadline and any glossary or style guide. You get a fixed price the same day, within 24 hours at the latest.