Lokalog

🌟 What's new?

Vantage now handles Markdown and MDX files more cleanly, so your content is split into sensible pieces and the parts you want to keep stay untouched.

• No-translate blocks. Wrap any text in a custom <notrans>…</notrans> block in your Markdown or MDX files, and it stays out of translation.
• Clearly marked in the editor. Non-translatable words are highlighted in the editor and in the preview. For example, a product name like "Acme Cloud" stays visible and is clearly marked as not to be translated.
• Sentences stay together. Soft line breaks inside a Markdown paragraph no longer split a sentence into separate translation units.
• Your formatting is preserved. Intentional hard breaks and your original line breaks are kept when you export the translated file.

🎯 Why it matters to you?

You get cleaner, more natural translations of your Markdown content, brand and product names stay exactly as written, and your files come back formatted the way you wrote them, with less manual fixing afterwards.

🌟 What's new?

Braze Live Preview is now available in Vantage. Your reviewers can see translated email content as it will appear, instead of reviewing text in isolation.

• No setup required. Previewable (HTML-based) items show up in the preview screen automatically.
• Emails, campaigns and Canvases. Email body previews are available for email templates, campaigns and Canvases.
• Easier Canvas reviews. Reviewing multiple emails in a Canvas is now simpler, with all of them in one place.

For campaigns and Canvases, the preview currently covers email content. Push and in-app content aren't previewed yet.

🎯 Why it matters to you?

Reviewers can check translated emails in context, without switching back and forth between Lokalise and Braze. That makes it easier to catch content and layout issues earlier and shortens the feedback loop before your content goes live.

🌟 What's new?

You can now remove custom filters without worrying about breaking your Workflows.

• Deleting a custom filter now works in the editor, in task scope selection and in the workflow trigger.
• If a workflow still uses the filter, you'll get a notification before the filter is deleted.
• You'll be prompted to remove the filter from that workflow first, and only then can you delete it.

🎯 Why it matters to you?

Keeping your filters tidy is now simpler and safer. You can clean up old filters with confidence, and your Workflows keep running the way you expect.

🌟 What's new?

You can now save Machine Translation straight into your Translation Memory when you work with Tasks and through the public API. Until now, this was only possible in Workflows.

• Available in Tasks. Turn on the option when you set up a task, and your machine translations are added to your Translation Memory.
• Available in the API. The same option works through the public API, so your integrations can use it too.

The setting is off by default for manually created tasks. Once you save it, Lokalise remembers it, like your other advanced task settings.

🎯 Why it matters to you?

Machine Translation is a cost-effective choice in many situations. Now you can reuse those translations in your Translation Memory without having to set up a workflow first, which gives you more flexibility.

🌟 What's new?

Two new dashboards on the Usage tab of Analytics give you a full view of how your Workflows and Automations run and what they deliver.

• Workflows at a glance. See which workflows are live, paused or canceled, plus a "Workflows needing action" list that explains why each one stopped and how to fix it.
• Run health. Track runs over time, including succeeded, failed and waiting-on-task runs, along with your success rate. You can also spot workflows that are live but have been idle for 30 days.
• Workflow results. Measure keys touched, tasks created and completed, and processed words, and compare them with other ways of delivering words, like the editor, file uploads, the API and manual tasks.

The Automations dashboard shows what's configured versus purchased and which projects use automations. It also shows how they changed over time, the action chain behind each one (Translation Memory, Machine Translation, Pro AI) and what they delivered, from keys touched to processed words.

🎯 Why it matters to you?

Workflows and Automations do a lot of work behind the scenes. Now you can answer "Are they running? Are they stuck? What are they delivering?" yourself, without a support ticket or a custom report. Catch broken or idle workflows early, check you're getting value from the automations you pay for, and see how much of your translation volume runs on autopilot.

🌟 What's new?

Ruby developers can now work with the Lokalise Vantage API through Ruby SDK Next, our new official Ruby client.

• Vantage client. Create a Vantage client with your access key and call Vantage resources directly.
• Short, readable code. For example, listing your team's projects takes just a few lines.
• Documentation. The SDK has its own documentation site to help you get started.

The Vantage API is in beta, so some changes may happen as it evolves.

🎯 Why it matters to you?

If you build with Ruby, you can connect Vantage to your own tools and workflows without writing the API requests by hand. It saves setup time and gets you started faster.

🌟 What's new?

Our official Node.js SDK now supports the Lokalise Vantage API, starting with version 17.

• Vantage client. A dedicated LokaliseApiVantage client gives you direct access to the Vantage endpoints.
• Same familiar style. Use your Lokalise API key and call Vantage resources, such as listing your projects, in a few lines of code.
• Documentation. The SDK docs include a Vantage introduction to get you started.

The Vantage API is in beta, so some changes may happen as it evolves.

🎯 Why it matters to you?

If you build with Node.js, you can plug Vantage into your own tools and workflows without writing the API requests by hand. It saves setup time and gets you started faster.

🌟 What's new?

We've released new versions of our GitHub Actions, the ones that sync translation files between your GitHub repository and Lokalise: Push Action v5.7.0 and Pull Action v6.0.0.

• Improved reliability and stability for your automated translation workflows.
• Better handling of translation files and Git operations.
• More predictable synchronization between GitHub and Lokalise.
• Improved error handling, plus fixes for several edge cases.

Heads-up: Pull Action v6.0.0 includes breaking changes. Check the release notes before upgrading.

🎯 Why it matters to you?

Your translation pipeline runs more smoothly, with fewer surprises when files move between GitHub and Lokalise. Developers spend less time debugging sync issues and more time shipping.

🌟 What's new?

Webflow Live Preview is now available in Vantage. Your reviewers can see translated content on the actual rendered page, instead of reviewing text in isolation.

• Quick setup. Sign in to your Webflow account and connect your project. There's no plugin, code snippet, or change to your site.
• Review on the real page. Once content is published to your Webflow review environment, reviewers open the rendered page and see where each translated segment appears.
• Segments highlighted. The relevant segments are highlighted in the preview, so reviewers know exactly what they're checking.

The preview is read-only for now, and we're building on it.

🎯 Why it matters to you?

Reviewers can check translations in the context of the final page, without switching back and forth between Lokalise and Webflow. That makes it easier to catch issues with fit, tone, and layout before you go live.

🌟 What's new?

Pro AI translation in Expert now uses your team's style guide together with your translation examples (translation memory matches, reviewed or tagged keys). Before, it used one or the other.

• Your preferences shape every translation. Tone, formatting, and wording rules from your style guide now apply to every Pro AI translation.
• No setup needed. Existing style guides are picked up automatically.
• Pro AI only.

🎯 Why it matters to you?

Your investment in a style guide now counts in every AI translation. It helps most when the system can't find close examples from your past translations. Keep your style guide summary clear and concise for the best results.