Another month, another round of updates, another set of powerful new features – just business as usual at Easyling. Expanding the translation proxy’s arsenal this month are changes as tiny as adding a new header to be forwarded, and as great as a complete rework of the crawl history interface. Also deployed this month are our public caching service, the balance info box facelift, the ability to handle TMX files with only partial locales, and an SEO filter for the workbench. See the complete listing after the jump!
Workbench SEO filter
Content on a site can come from a variety of sources, ranging from the text body itself, to various titles, alternative text, and metadata. Some of these sources are more important than others for SEO, as they have a greater impact on how your site ranks in searches. Starting in October, the Workbench displays the exact source of the content underneath the entry number, including the tag and attribute name. Along with this comes a new filter category that allows you to filter for specific sources, as well as a filter preset that selects only the most SEO-relevant sources, to reduce information overload.
Partial locale TMX import
Translation memories, like XLIFF files, usually include at least one language identification code to designate the target language. Such code itself consists of two parts, a language ID and optional geographic region identifier, for instance, US English is designated by en-US, while British English is en-GB. This allows the TMX file to store multiple translations for a single language, accounting for dialects and regional variations of target content. Up until recently, our parser refused to recognize the language-only files as valid, and returned an error, but now, we have upgraded it to handle these truncated locale codes. Once imported, translations that are assigned to the language itself will be available across all locales of that language.
Balance info box facelift
The balance info box on the dashboard also got a well-deserved rework: while it previously drew its information from the user, now it ties to the project opened, meaning it will always display information related to the project at hand, even if it uses a shared wallet or you’re only invited onto someone else’s project. Also, depleted balances are indicated by a red border, and an additional warning dialog on pageload.
If a page is clearly marked as publicly cacheable (Pragma: public, Cache-control: public headers), Google’s Edge Cache may store it in its geographically distributed POP locations for faster loading, at its own discretion. However, even if it is stored in one location, it doesn’t speed up things at another location. Now, we’re preparing for the private beta rollout of our own public caching feature: storing publicly cacheable pages, being able to serve translated responses at the speed of MemCache (measurable in single-digit milliseconds), overcoming network latency or server lag. Soon to be released to the public, with proper UI. Should you need this sooner, enquiry in email.
Crawl History Dialog
In a move that was some time in the making, we decided to do away with our previous crawl history interface, displaying on the last eight crawls in small type. Instead, we constructed a highly visible dialog that pops up when the View History link is clicked. This dialog lists all crawl of the project, past, present, or future (provided there is a scheduled crawl set up) with all the relevant information, such as the number of pages found, the time it took, and the termination reason.
We also conducted a number of miscellaneous optimization and minor feature passes, such as the ability to proxy the Access-Control-Allow-Headers headers, or adding automatic syntax highlighting to the Content Override editor (the highlighting scheme is determined by the entered Content Type).Dedicated demo for You Tweet