As you may have already read, we moved offices: let’s face it, we’ve outgrown our previous shell. But the move or the day spent assembling our new furniture didn’t do much to hold us back, so we could keep working on newer and newer features for Easyling to make your lives easier. Maybe the most important of these is the Import Log, helping you see if your XLIFF import encountered any errors. Also, the Audit Log now includes memory population events, and the Workbench now has a full text search capability. You can find the details after the jump!
Lastly, we’ve completed work on a very convenient feature we call the Full-text Search. All projects created after 15 April are created with an Index making their source- and target language entries searchable on the server. Thus, when you try searching the All Entries view for a single string, your machine will no longer get bogged down searching a potentially very large project. Instead, the search query is sent to the server, which executes it at blinding speed, returning only the entries relevant.
Further to this, the Workbench now handles special keywords (in addition to the /\[\.\.\.\]/ regular expression format) that can modify the behavior of the search:
- source:foo – searches for the word “foo” in only the source entries
- target:bar – searches for the word “bar” in only the target entries
- ~cats – stems the query word, searching only for the word stem. This means “cat” and “cats” will both be returned as valid matches.
Possibly the most important (and most low-key) upgrade to roll out in April was the Import Log: from now on, the “Import complete” notification email will include a link to a text log of the import process. Usually, this will have two entries (“import started” and “import complete”), if you see more entries, it’s a good clue that something went wrong and you’re likely to have segments that did not import. If you encounter such a case, please refer to our FAQ on the most common causes (and ways to contact us for help).
Audit Log upgrade
Second is the Audit Log’s upgrade to include events of memory population.
To recap, Easyling Translation Memories can be populated either by confirming segments one-by-one or en masse, or they can be populated by taking all the translations on the project and inserting them at once, done by the Populate button on the TM screen. Since this latter action causes a task to be started, Easyling will now log its triggering in the Audit log, so the current states of memories can be tracked, more or less. Logged information will also include which memory was populated, and available target languages at the time.Dedicated demo for You Tweet