Launching today
LocaleCheck 2.0
Local JSON/ARB review, glossary and release checks
2 followers
Local JSON/ARB review, glossary and release checks
2 followers
I built LocaleCheck around a question: how much translation review can stay on your own computer? The 2.0 beta combines editing, glossary, memory, portable reviewer files and release checks. Try it without signup: https://bellocchio23m.github.io/PlayGround/localecheck/preview/ I want concrete objections: where does this workflow break for your team? This is an evaluation beta, with no machine translation, live co-editing or authenticated roles.
Free Options
Launch Team
Atlassian LoomHit record, hand off to AI
Promoted
I am developing LocaleCheck for frontend developers, Flutter engineers and localization reviewers who want to keep catalog editing and asynchronous review local. Start with Explore example, edit a translation, inspect Memory & terminology and Review exchange, then run Checks & release. My challenge: which exact operation would still force your team back to a hosted TMS? Please give the smallest fictional example, your expected result and what makes the current workflow difficult. Critical feedback is welcome. The public 2.0 beta does not offer machine translation, live co-editing or authenticated permissions. It is separate from the existing paid 1.2 kit; please do not buy that kit expecting this beta. Free beta: https://bellocchio23m.github.io/...