Slate is a Windows application that was due for release around the time this issue of ITI Bulletin went to press. It has been designed to integrate with CAT tools to provide machine translation suggestions from an engine created on your local machine, based entirely on your own translation memories.
Tom Hoar is the founder and chief executive of Slate Rocks, LLC, the company behind Slate. I asked Tom if he would explain to ITI Bulletin readers in more detail how Slate will work, and also tell us more about the novel way it was marketed and pre-sold in the months leading up to its release.
EG: First of all, Tom, can you tell us what makes Slate different from cloud-based machine translation tools such as Google Translate?
TH: Letʼs start with whatʼs the same. Slate and most cloud-based machine translation service providers (MTSPs), such as Google Translate, rely on statistical machine translation technologies. From there, Slate and MTSPs diverge significantly in both intention and design.
Cloud-based machine translation engines serve millions of users across a broad range of subjects. Theyʼre designed to serve anyone with ease and convenience. Translators, for example, can simply upload jobs and receive translated suggestions through their CAT tools. However, the quality is debatable and, more importantly, confidentiality agreements often prohibit any use whatsoever of cloud-based machine translation.
Some cloud-based engines can be customised, leading to improved quality for specific subjects, but customisation requires users to share their translation memories with the MTSP. Translation memories are not only confidential, but also strategic assets. Therefore, many translators and agencies abstain from customisation to protect their translation memories.
In contrast, a Slate engine serves one translator working in one or a few subject areas. Translators can convert their translation memories into customised translation engines. The engines then generate suggestions that accurately reflect the focus, quality and consistency of the translation memories. Confidentiality agreements and strategic translation memories are safe because all the work stays on the translatorʼs computer.
EG: Will Slate work for all languages? And all language variants?
TH: On release, Slate will support 29 languages. That means translators can create engines across 812 language pairs. We will automatically add support for new languages with free updates as we develop the necessary ʻtokeniserʼ utilities. There are several approaches for managing language variants. The simplest approach relies on the content of your translation memories. For example, if you want suggestions in British English, simply create an engine from translation memories with British English only as the target language.
EG: Using our own translation memories sounds very exciting for translators who have years of resources under their belts. But how useful will Slate be for people who are just starting out?
TH: Slate might not be very useful for new translators because it takes time for translators to build their own inventories. We estimate that roughly 130,000 segments are required to create reliable statistical machine translation engines. However, some customers report good experiences with as few as 50,000 segments, particularly if they work in a very specialised field. Translators without their own translation memories can use publicly available ones, such as the DGT corpus, but then Slate mimics that writing style.
EG: Many CAT tools already have smart engines that repair or patch fuzzy matches from translation memories in real time, drawing on a variety of resources to do so. How will Slate do this better?
TH: Iʼm aware of these new features, but we havenʼt tested any of them. I think they also go by names such as ʻsubsegment matchingʼ and ʻauto-assemblyʼ. So my answer here is mostly speculation, and I welcome readersʼ feedback on this point, but here goes: these features use language-specific rules to break apart translation memory segments and identify phrases. Then, more language-specific rules are applied to splice new suggestions. I perceive these features as a type of rules-based machine translation. Thatʼs great if youʼre working with languages that support these rules. But statistical machine translation is the ultimate subsegment match and auto-assembly tool. It uses machine-learning techniques to identify rules, instead of language-specific rules crafted by hand. This makes it accessible across many more languages. It will be interesting to see how the two compare.
EG: Will Slate be able to give priority to certain terms or glossaries?
TH: You can set up Slate to force specific translations — just create a table with side-by-side source and target language terms. Slate will use the table entries to override the engineʼs choice.
EG: What happens when Slate comes across new terminology in a source text? Will it look for the nearest match? Will it leave a blank?
TH: Words that are missing from your translation memories altogether are called out-of-vocabulary (OOV) words. During translation, the engine uses the words it knows, and OOV words are passed through to the target sentence as source language words. You can add newly translated OOV words to your forced translation table to reduce repetitive corrections.
EG: How easy will it be to set up Slate? Will non-tech-savvy translators be able to get it to work?
TH: To create an engine, you first export your translation memories, glossaries and other bilingual resources to TMX or tab-delimited files and import them into Slate. Then, you label imported segments by subject or other identifier. Finally, you define which labels to use to create each subject-customised engine. To run the engine, you add its machine translation connector to your CAT tool. Once configured, the CAT tool will present machine translation suggestions from your Slate engine like any other machine translation provider.
EG: As you know, I was one of the backers of your Indiegogo crowdfunding campaign for Slate. Can you explain to ITI Bulletin readers what Indiegogo is and why you decided to market your product through crowdfunding?
TH: Thank you for your backing! Slate is the first Windows application of its kind, so we didnʼt know what to expect from potential customers. A novel application deserved a novel marketing strategy to quickly test the market and learn from the experience. I considered Survey Monkey, expert interviews and other research techniques, but nothing tests a market like customers spending real money. We could have set up an online store on our own website, but why would prospective customers have trusted us? I learned that some companies use Indiegogo as a test market platform. Instead of trying to raise a large sum, we focused on learning how to actively engage translators with our new product. We didnʼt know what to expect in terms of sales. We set the $6,500 goal to test a reasonable sales volume of about 20 units in 60 days.
EG: In addition to the $6,500 target, I saw that you had some ʻstretch goalsʼ that later disappeared from the campaign page. Does that mean the response wasnʼt as good as youʼd initially hoped?
TH: From the start, we designed two versions of the sales message. We ran one for the first 60 days with stretch goals to see if they would inspire more sales. We dropped the stretch goals for the second half of the campaign because the first half showed we needed to focus on simplifying our message. It was a great learning experience and we even overshot our money goal by 40 per cent at the very end. We have some great new customers and we learned what translators are looking for. Now that the market knows weʼre here, we have a lot to live up to!
EG: Campaign backers had to pledge for a product they hadnʼt tested. Iʼm sure some translators werenʼt prepared to take that risk. Will a trial version be available when the product is released?
TH: I agree. Most consumers want to test new software before buying it. Yes, in the long run, we will offer a trial version. Along the way, weʼll try a variety of promotions.
EG: How do you see the tool being developed, once its on the market?
TH: Itʼs not only about how we develop the tool. Slate includes a programmable application programming interface (API). Translators can build extended features, inspired by their language skills and their own creativity. Our development will focus on language-independent features and improving the shared framework. Weʼll also create online resources for translators to share.
EG: How do you see the future of machine translation?
TH: Iʼd like to see ʻmachine translationʼ become a legacy term. Itʼs an antiquated term that comes with 65 years of emotional baggage – some of which is justified – but we are living in a modern age where software has been abstracted from the machine. I believe quality estimation is the biggest remaining challenge in translation software, but the unknown is exciting to me. I think we will see some unpredictable advances in this field as translators start to experiment with this democratised technology on their desktops.
EG: Thank you very much for answering these questions. I look forward to putting Slate through its paces!
TH: Thank you. Iʼve enjoyed our exchanges as weʼve got to know each other through the Indiegogo campaign. Several other ITI members are customers of our products and itʼs always fun working with them. I look forward to continued growth with the ITI membership.
Tom Hoar is a language technology veteran with 30 years of experience and founded Slate Rocks, LLC in 2010 with the vision of simplifying statistical machine translation technology for professional translators.
Our thanks to ITI Bulletin for permission to re-publish this article on our blog.