couple of weeks ago Lionbridge announced that it had purchased CMS
middleware Clay Tablet.
first response was: That's terrible -- it'll make it much harder for
smaller vendors to get into content management systems for translation
second thought was: Maybe it's a good thing after all because now
translation environment tool makers might actually be forced to provide
ways to get that done themselves rather than rely on a third-party tool.
I sent out a note . . .
wait, let's first make sure that we all know what we're talking about.
Tablet offers ready-made
connectors between commonly used content management systems (CMSes) and
translation environment tools and/or translation workflow systems so
that text from the CMS (which really is just a database that contains
text for all kinds of purposes) can be monitored and easily extracted.
Once the extracted text is translated within the TEnT, it's then
reinserted into the correct position inside the CMS. If newly authored
text is placed into the CMS, Clay Tablet sees that and sends it
off to the TEnT again. It all sounds pretty straightforward, but it's
complicated by the fact that there are a good number of CMSes out there
and each one works differently, so there has to be different
programming for each. Plus, if you don't have a good way to get into
the CMS, a lot of manual work is required, which is exactly what you
(and your client) want to avoid. Very large language service providers
might be able to build custom connectors to a CMS, but that's typically
out of reach for small providers. So in some ways, access to CMSes has
become one of the technological differentiators that separates the big
from the smaller players.
back to my note. This is what I sent to all of the TEnT vendors:
is an email that I'm sending to all CAT tool developers in preparation
for my newsletter that is going out next week. I would like you to
state in no more than 150 words what your plans are in regard to CMS
connectors. With the recent purchase of Clay Tablet by Lionbridge, this is something
that is on many people's minds, and some of you might have re-evaluated
your plans for how to proceed with developments in that area.
I'm interested in (and would like you to address) is: What is your
current status of being able to directly connect to content management
systems (and if you already provide support, for which CMSes)? What are
your plans to develop solutions that would not rely on a third-party
middleware solution like Clay
Tablet? And if you don't provide any support or are not planning to,
what do you expect your users to do aside from developing customized
are their responses. (I've left them uncommented even though I feel
some might have misunderstood my question.)
Connecting to Content Management Systems (CMSes)
is vital for a Translation Management System (TMS) like our Language
Server. As there are so many different CMSes available, it is
impossible to have individual connectors to every system.
Across Systems has created a generic CMS connector that allows an
automatic exchange of data with virtually any third-party application
that has structured export/import processes. This connector allows not
only for translation files to be exchanged, but can be directly linked
to our translation automation workflows.
it is generic, our customers do not have to use middleware and can rest
assured that the connector still works after either CMS or TMS is
about 65+ CMSes have been connected, including Adobe AEM, Quark
Publishing Platform, Typo3, OpenText, Hybris,
addition, Across offers open web services APIs so that
third-party applications can interact and, e.g., access terminology or
sentences for authoring assistance purposes.
I released the new version of CafeTran featuring its own CMS
system based on the H2 database. It is named Total Recall and basically
it allows you to store your projects in the database for later
retrieval. The recalling procedure for translation is context-sensitive
-- that is, it takes into account the current source document lexical
content. You can apply further filtering for the recall based on a
specific client, a field, a previous project, or a user-defined context
property. The CMS system is segment-based, meaning that it stores your
working translation memory in a segmented form along with all the
project properties. It can also import TMX memories. The default
configuration is for the translator's computer, but there are no
obstacles to configure it in a server-mode. The future plans are to
extend the 'Total Recall' functionality to other databases (MySQL
Déjà Vu X3 is capable of translating
content exported (as HTML, XLIFF, or XML) from most CMS platforms, it
does not currently offer support for connecting directly to any CMS. At
the moment, most of our customers who work with a CMS take advantage of
the automation capabilities offered by the Déjà Vu X3
Workgroup API to develop custom solutions for pulling source texts
from and pushing translations to their CMS.
said, integration with several CMS systems is high on our list of new
features for 2015 for the TEAMserver platform, rather than
directly for the Déjà Vu desktop client.
Libellex is an on-line CAT tool with its own internal
machine-translation engine, tuned project by project. It currently has
three connectors to CMS :
is an ASP.NET CMS & Cloud CMS for building and managing responsive
websites and apps.
Calenco is a web application designed to write,
structure, store content, and publish automatically complex documents
for output in printable, digital, web, or mobile channels.
SharePoint is a web application framework and platform integrating
intranet, content management, and document management.
connectors are based on a simple API using XML-RPC scripts and are
therefore easy to develop for new CMSes, should a customer or partner
strategy is unchanged by the recent announcement that Lionbridge has
acquired Clay Tablet. The Lingotek Enterprise Translation
Hub fulfills the promise of Continuous Translation and already
seamlessly connects to a multitude of CMS platforms, including Adobe
Experience Manager, Drupal, Oracle WebCenter, WordPress,
and SharePoint. Each of these integrations (collectively
referred to as Lingotek Inside) are proprietary to Lingotek and
powered by Lingotek's industry-leading Multilingual API.
This strategy provides Lingotek's customers with the assurance that
their investment in Lingotek's translation technology and their various
content repositories will never be in jeopardy.
fact that Lionbridge is both a technology and service provider and can
offer this "one-shop stop" experience to customers who don't mind
buying everything from the same vendor makes them a competitor to us
that has a unique selling point that we cannot and don't want to match.
We cannot consider them a partner like we consider Plunet, XTRF,
or Easyling, for example, because we sometimes compete with
Lionbridge. So you can expect Kilgray and memoQ to move into
this area, offering a surprisingly fresh business model. Currently
about a dozen CMSes are integrated through our content connectors
framework, but we will go beyond that and match the depth of the Clay
Tablet technology offering. However, this is not an immediate
priority; we won't throw everything away now, and many other
interesting things are in the making.
have developed a CMS connection framework that lets us easily connect
to any open-source CMS as well as proprietary CMSes with public API or
SDK support. For instance, connecting to Wordpress and Dropbox
works really well.
have had discussions with Clay Tablet for a specific customer,
but in the end it did not work out because Clay Tablet was too
expensive for the customer. However, based on our findings, to develop
a connector between Clay Tablet and Memsource would not
be hard at all, so it really depends on someone requesting it and being
willing to pay for Clay Tablet.
strongly believe that the corporate usage of SmartCAT
absolutely requires providing the possibility of integration with the
client's corporate infrastructure (including CMS). That is why
we've developed our own Translation Connector (API for SmartCAT).
Right now we are testing it on pilot projects and plan to publicly make
it available in 2015.
to content management systems needs to scale and be available at all
levels -- TMS to CMS (Enterprise level), Translation Productivity
products to CMS (via OpenExchange as part of the Studio
platform; scales down to smaller teams and even individual users [where
needed]). In our view, it is vital to offer a platform so developers
can plug in at will. Clay Tablet is part of this ecosystem and
as such we don't have any plans to change our strategy with respect to
partnering with Clay Tablet where required (chiefly at the
TMS/Enterprise level). As an example for an OpenExchange
connector between Studio/GroupShare and CMSes that does not
need to rely on Clay Tablet, see Connecting Content (by
generic interfaces of Transit support all common standard
formats for translation jobs and data (e.g., XML, XLIFF, TBX, TMX,
etc.). In addition, the entire process chain can be automated with the Corporate
Language Management platform STAR CLM in any level of
detail from triggering the translation job in the CMS to the
final, quality-proofed "delivery" and integration back to the CMS.
CLM and Transit provide
many customizable options for an easy integration into the existing IT
landscape, such as automated interfaces or "hot folders," direct
integration per API or CLI, and even interfaces to accounting systems
the end of the day, a direct connection to the CMS is the most
efficient and best way for sustainable information processes. In our
experience, a third-party "one fits all" interface is not only
unnecessary, but may even impair the optimal integration of CMS, TMS,
and all process participants.
standards-based approach to developing our cloud-based Translation
Ecosystem brings us a step beyond the more rigid structure of the
traditional Translation Management System. The central tenet of the XTM
ecosystem is a highly flexible and powerful translation workflow
solution enabling our enterprise clients to automate traditionally
manual project management tasks through the tight integration with
direct integrations with not just CMSes but also other solutions such
as source control systems is of strategic importance to XTM.
International assists and supports clients with their own integrations
with the use of our extensive web services API and Clay Tablet.
September XTM announced the release of "XTM Connect." XTM
Connect includes the complete web service API as an SDK and also a
library of pre-built connectors to key solutions. Existing
out-of-the-box connectors include Drupal, Wordpress, Adobe
InDesign Server, SDL Trisoft, AutoCAD files, and Instinct
Tools. There are also connectors for XTRF, Plunet, Easyling,
and TermWeb. Watch this space, though, as we will be adding
direct connectors for Adobe Experience Manager, Documentum,
Episerver, Perforce, and many others.