Easyling Release Notes September, 2020

Autumn is here and it’s beautiful. Unfortunately, we can’t see much of it as we are still stuck inside due to the pandemic. The good news is that we can keep adding features to Easyling without distractions. This month, we made the Dashboard 2.0 the default landing page and added the option to create Work packages with settings based on previous packages. Read the full article for the details!

Dashboard 2.0 is the new default

With every month, we are getting closer to fully modernising the user experience in Easyling. We are at the point where the Dashboard 2.0 has most options available so there isn’t much of a reason (except for Advanced settings) to go back to the old Dashboard. As such, we made the Dashboard 2.0 the new default. Don’t worry, the old Dashboard isn’t going anywhere yet. You can still go back to it if you feel more comfortable using it.

Not only does the Dashboard 2.0 look better, its underlying technology is more modern and will allow us to add new features faster than ever before so don’t hesitate to let us know at support@easyling.com if you’d like to see something changed, improved or added.

Work packages

Work packages can be used to split the segments into sets that you can separately work on (either in the Workbench or in your external CAT via XLIFF exports). One omission so far has been pre-translation. With this month’s update, it is now possible to pre-translate Work packages. Click on the context menu (the one with 3 dots) of a Work Package in the Work package list and select Pre translate to open the dialog. There, it is the usual pre-translate settings. Select the language and your translation memory or your preferred Machine Translation engine to continue.

Additionally, it is now possible to start the Work package wizard with a previous package’s settings filled-in as defaults. Head to the same context menu mentioned above and click Create new Work package with the same settings. Don’t worry, it won’t immediately start generating a package, just pre-fill the wizard. This is useful if you want to create similar multiple Work packages (e.g. one every week) with similar settings (like a source filter). This way, you can avoid having to copy and paste the settings. Note that due to technical limitations, only work packages created after February 2020 support this feature.

Caching headers

Some proxy modes (mostly those used for website analysis), like the Preview, the ABC-proxy or the X80 & X130 modes prevent resources from being cached. This is to ensure that your Preview (and analysis data) are always up to date. However, instead of just changing them, if the original resource allowed caching through the Cache-Control or Pragma headers, the original values will now be sent under alternative header names like X-TranslationProxy-Remote-Cache-Control. This will prevent confusion as you’ll be able to both see the caching rules in place for the current mode as well as those set for the original site and you won’t need to guess where the current set of active rules are coming from.

Other tidbits

Some other, smaller improvements worth mentioning:

• We added the option to pre-translate multiple languages of the same project at the same time. This can speed up the process significantly for projects with lots of target languages.

• We fixed an issue that prevented CSS/JS injections defined in Path Prefix Overrides from being added. Additionally, we added a limit of 1 kbytes to ensure good performance. Larger files should be imported via injected links (but don’t need to have them on the original site, just create a content override for them).