Another month, another 4 releases. This month has three major highlights: We improved on Auto Pre-Translate, Crawls can now be started based on the settings of a previous crawl and the JavaScript translation engine got improved compatibility. This is a good one. Read the full article for the details!

Crawl Re-Setup

This may be my personal favourite feature we released in quite some time. Have you ever found yourself setting up multiple similar crawls? Maybe you forgot to turn off one setting, and now you need to recrawl, or you just need to Scan the site for new content just like you did a couple of days ago. The new feature we released will help you out in all of these situations. You can find it in the Crawl list. You’ll notice that every element now has a three dot action menu. Clicking it reveals the option Recrawl with same settings. When you select this option, you are navigated to the Crawl wizard with the previous crawl’s settings already filled in. You can change them around or just hit Start crawl.

APT filters on URL

Auto Pre-Translate is a great feature for preventing bleedthrough. You can immediately translate new content as it’s being ingested either via your Translation Memory or a Machine Translation engine.

However, depending on project needs, you may want to treat parts of the website differently - use different APT settings. Some sections, for example can have lower priorities. These sections could be simply machine translated while translated content on the rest of the site is reviewed by a team of human translators.

Up until now, you could specify these partitioning rules based on the following criteria:

• Path prefix of the page
• Target language

We were made aware of a site where path infixes had to be used to correctly model the client’s requirements. So, naturally, we took the Hammer of Overengineering, and added path regular expression support. Now, you can filter on any property of the URL that you can express as a Java regular expression.

Note: The user interface for this feature isn’t ready for its prime time yet. We’ll add it as soon as we can. In the meanwhile, if you think you need this feature, reach out to us at support@easyling.com.

HTML attribute translation in Crest (and Crebbl)

HTML attribute translation is an Advanced setting on the Dashboard (it’s called Process custom HTML attributes). Support for it was added to Crest, the JavaScript-based publishing method as well as Crebbl, the Chrome extension. It is useful for two main scenarios:

• SEO: There are multiple attributes, like description on meta tags that are invaluable for SEO. These must be marked as translatable to ensure that they are properly localised, improving SEO scores.
• Sites that display attribute values as text: There is always the odd site that uses a script to take the value of an attribute and use it as displayed text. It’s quite rare, but in such a case, being able to localise these values is invaluable.

One more thing

Well, more like a few small things:

• Ctrl+S (or Cmd+S on a mac) can now be used to save your changes in JavaScript/CSS editors and in the Page Content Override editor. This has been bugging me for quite a while. No more accidentally trying to save the HTML code of the Dashboard.
• The Crawl statistics card, visible in the Crawl list was tweaked. A pie chart was added that you can use to quickly get an overview of the amount of content on a site.
• We broke and fixed the OAuth authorisation workflow - the page where you specify which projects to give access to was broken for a couple of days.
• A bug that caused a user’s workflow roles to get lost when their privileges were adjusted under Sharing settings was fixed.
• Added the “Send target language as cookie” tweak to Advanced settings, under Serving settings. This is an additional way to detect the current target language, enabling language-specific customisations on the website. This feature itself was added last month but now the toggle itself is available for everyone.
• We fixed the “Show hints in full” toggle under Advanced settings → Tweaks.
• We tweaked the wording on the Dashboard to clarify what we consider to be a unique word. Unique word counts now mean that a given segment has no repetition anywhere on the site, not even fuzzies. Additionally, we introduced a new expression, Translatable words, to signify the text that is used by our pricing model: unique words, fuzzy repetitions as well as context matches.