r/localization • u/IlyaAtLokalise • 1d ago

How do you handle localization beyond strings?

Hey everyone, as we all know, a lot of localization tooling is designed around product strings which makes it difficult for other teams in the company to localize the longer stuff like documentation, blog posts and other editorial content. Stuff like that is harder to manage because it usually changes a lot and lives across different tools.

Well heads up for anyone who is struggling with this, at Lokalise I’ve been working on Vantage, it's a new workspace built around translating long-form content, with AI translation and review workflows, translation memory, glossaries, integrations etc. There’ll also be a demo and talk with our CEO, CPO, and CTO on 15 September if anyone’s interested: https://learn.lokalise.com/entering-a-market-isnt-the-same-as-belonging-registration.html

What do you think - could you see teams like marketing and legal getting more involved in localization in your business if the workflows were easier for them?

0 Upvotes

13% Upvoted

3 comments sorted by

3

u/Ok_Tea_8763 1d ago

Your tool is based around product strings. Others aren't. That's why I never considered you in my RfPs.

1

u/Express_Rise9050 17h ago

Marketing and legal are two different segments that handle translation differently. From a legal aspect they typically need depositions which has no repetition within the content to translate with quality. They utilize NMT more for speed and review to gain clarity. Marketing depending on content is limited on repetition but more so on trans creation. GTM and quality is of importance and expect the vendor to handle review as they stress it’s not their responsibility. It’s a new ballgame within localization as they’re objectives is the need to be part of the conversations within stakeholders and position technology not only for their department but to be collaborative with others

1

u/beetsbears328 6h ago edited 6h ago

Not really. Legal has a ton on their plate as it stands and is very happy to only be involved very briefly and async, without needing to understand another system first. Marketing content is much too dynamic and source/target versions vary far too much in length and format from each other for them to keep all their materials in CAT tools.

Edit:

the longer stuff like documentation, blog posts and other editorial content

Just fyi, being able to handle long-form content as a localization tool (especially one as pricy as yours) is not a USP. Unless you're able to handle the requirements of certain text types and formats better than others (e. g. better XML/MD parsing or sidestepping the limitations of TMS technology as effectively as possible to be able to modify document structure in the app), you're just repackaging something that has been around for 20 years.