An exploration of language technologies, translation education, practice and politics, ethical market strategies, workflow optimization, resource reviews, controversies, coffee and other topics of possible interest to the language services community and those who associate with it. Service hours: Thursdays, GMT 09:00 to 13:00.
Note: This post has been updated to reflect a planning change. The five-day trainer training course has been replaced with a two-day (eight hour) course for translators to master key memoQ features.
The CETAPS institute at Universidade Nova de Lisboa FCSH has planned a week-long (20-hour) memoQ online project management training course and a two day (8-hour) course on memoQ mastery for translators in the latter part of January 2024 which might be of interest.
The first course (from January 22nd to 26th) will be for those in project management roles or similar functions using memoQ TMS servers; it will begin with a day of intense review and instructional guidance for memoQ basics in online projects from a translator and reviewer perspective and proceed from there to topics such as online project creation and administration, rights and resource management, template use, optimal preparation workflows, mid-project updates and more as well as participant-specific issues. The cost is €480.
The second course (from January 29th to 30th) is aimed at translators and reviewers, who want to better understand and handle project workflows for both their own projects and agency-created ones. This will include resource customization, project management, project templates, file import filters, and project navigation, including some regular expressions magic. The cost is €90.
Further information on the course and an enrollment form can be found HERE. The registration period has been extended and enrollments will be accepted through January 5th. Questions regarding the program and enrollment can be directed to Prof. Marco Neves (e-mail: mfneves@fcsh.unl.pt).
Certificates will be issued to all participants completing the courses. Course availability is subject to sufficient enrollment.
As usual each year, the summer school at Universidade Nova de Lisboa is offering quite a variety of inexpensive, excellent intensive courses, including some for the practice of translation. This year includes a reprise of last year's Best Practices in Translation Technology from July 16th to 21st, with some different topics and approaches.
Using machine translation in a humane, intelligent way.
Using checklists to improve communication in translation.
Using glossaries, bilingual texts and other references in multiplatform environments.
Good practices for using terminology and reference texts in the target language.
Planning and creating lists for auto-translation rules and the basics of regular expressions for filters.
Some knowledge of the memoQ translation environment and translation experience are required.
The course is offered in the evening from 6 pm to 10 pm Monday (July 16th) through Friday (July 20th), with a Saturday (July 21st) session for review and exams from 9 am to 2 pm. This allows free days to explore Lisbon and the surrounding region and get to know Portugal and its culture.
Tuition costs for the general public are €130 for the 25 hours of instruction. The university certainly can't be accused of price-gouging :-) Summer course registration instructions are here(currently available only in Portuguese; I'm not sure if/when an English version will be available, but the instructors can be contacted for assistance if necessary).
Two other courses offered this summer at Uni Nova with similar schedules and cost are: Introduction to memoQ (taught by David and Marco – a good place to get a solid grounding in memoQ prior to the Best Practices course) from July 9–14, 2018 and Translation Project Management Tools from September 3–8, 2018.
All courses are taught in English and Portuguese in a mix suitable for the participants in the individual courses.
It has been interesting to see the behavior of my codornizes since I moved them from the confines of a rabbit hutch in a stall at my old quinta to the fenced, outdoor enclosures in the shade of a Quercus suber grove. In the hutch, they were fearful creatures,panicking each time I opened their prison to give water and food or to collect eggs. Their diet was also rather miserable; the German hunters who first introduced me to these birds for training very authoritatively told me that they ate "only wheat", and I felt bold to offer them anything different like cracked corn or rice. In the concentration camp-like conditions in which they lived, they also developed a serious case of mites and lost a lot of feathers. I thought about slaughtering and eating them as an act of mercy.
Then last spring I moved to a new place with a friend, who built a large enclosure for my goats and chickens. She didn't know about the quail. I brought them one day and hastily improvised an enclosure for them with a large circle of wire fence around a tree, because I was afraid the goats might trample them. There was far more space in this area than they had before, and real, dry dirt for taking dust baths. Soon the mite infestations improved (even before regular dunks in pyrethrin solution began), and the behavior of the birds began to change. They became less nervous, though sometimes when someone approached the enclosure they flew straight up in panic as quail sometimes do and bloodied themselves on the wire.
A few months later I built a much larger enclosure for a mother hen and her chicks to keep them out from under trampling feet or from wandering through the chain link fence of the enclosure into the hungry mouths of six dogs who watched the birds most of the day like Trump fans with a case of beer and an NFL game on the TV. The quail were moved in with the chickens as an afterthought. With nine square meters of sheltered space, the three little birds underwent further transformations, becoming much calmer, never flying in panic and allowing themselves to be approached and picked up with relative ease. They also exhibited a taste for quite a variety of foods, including fresh fruit and weeds such as purslane. Most astonishing of all, they began to lay eggs regularly in an overturned flower pot with a bit of dried grass. Nowhere else. All the reading I've done on quail on the Internet tells me that quail are stupid birds who drop their eggs anywhere, do not maintain nests and seem to have no maternal instincts whatsoever. I am beginning to doubt all that.
At various times in my life I have heard many statements made about the cultural proclivities of various ethnic minorities, but these assertions usually fail to take into account historical background and circumstances of poverty and prejudice, choosing instead to blame victims. In cases where I have seen people of this background offered the same opportunities I take for granted or far less than my cultural privilege has afforded me, I cannot see any result which would offer itself for objective negative commentary.
There are a lot of ignorant assumptions and assertions made about the class of digital sharecroppers known as translators. Some of the most offensive ones are heard from the linguistic equivalents of plantation owners, some of whom have long years of caring for these hapless, technophobic, unreliable "autistics" who simply could not survive without the patriarchal hand of their agencies.
Fortunately, technology continues to evolve in ways which make it ever easier to take up the White Man's Burden and extract value from these finicky, "artistic" human translation resources. The best of breed in this sense could make old King Leopold II envious with the civilization they have brought to us savage translators.
On many occasions, I have advocated the use of various server-based or shared online solutions for coordinating translation work with others. And I will continue to do so wherever that makes sense to me. However, I have observed a number of persistent, dangerous assumptions and practices which reduce or even eliminate the value to be obtained from this approach. It's not a matter of the platform per se, usually, unless it is Across to bear, but too often over the past decade, I have seen how the acquisition of a translation memory management server such as memoQ or memSource or a project management tool such as Plunet, OTM or home-rolled solutions has led to a serious deterioration in the business practices of an enterprise as they put their faith more in technology and less in the people who remain as cogs in their business engines.
As the emphasis has shifted more and more to technologies remote to the sharecroppers actually working the fields of words, a naive belief has established itself as the firm faith of many otherwise rational persons. This is expressed in many ways – sometimes as a pronouncement that browser-based tools are truly the future of translation, often in the dubious, self-serving utterances of bottom-feeding brokers and tool vendors who proclaim the primacy of machine pseudo-translation while hiding behind the fig leaf argument that we need such things to master the mass of data now being generated. It is fortunate for them perhaps that this leaf is opaque enough to hide their true linguistic and intellectual potency from public view.
A related error which I see too often is the failure to distinguish between the convenience of process and project managers and the optimum environment for translating professionals. I don't think this mistake is malicious or deliberately ignores the real factors for optimal work as a wordworker; it's simply damned hard much of the time to understand the needs of someone in a different role. I could say the same for translators not understanding the needs of project managers or even translation consumers, and in fact I often do.
So indeed, the best tool for a project manager or a corporate process coordinator might not be the best tool for the results these people desire from their translators. Fortunately, this is usually a situation where, with a little understanding and testing, both sides can win and work with what works best for them. The mechanism to achieve this is often referred to by the nerdy term "interoperability".
Riccardo Schiaffino, an Italian translator and team leader based in the US, recently published a few articles (trouble and memoQ interoperability) about memSource, a cloud-based tool whose popularity among translation agencies and corporate or public entities with large translation needs continues to grow. High-octane translators like Riccardo and others have trouble sometimes understanding why these parties would choose a tool with such great technical limitations compared to some market leaders like SDL or memoQ, but the simplicity of getting started and the convenience of infrastructure managed elsewhere on secure, high-performance servers with sufficient capacity available for peak use is an understandably powerful draw.
And the support team of memSource and the tools developers are noted for their competence and responsiveness, which is equal in weight to a fat basket full of sexy technical options.
So I will not argue against the use of memSource by agencies and organizational users whose technical needs are not particularly complex and who do not have concerns about a tool almost entirely dependent on reliable, high bandwidth internet connectivity at all times to fulfill its key promises. In fact, it's a good and easy place to start for many, perhaps more so than the rival memoQ Cloud at present, which suffers sometimes from limited capacities (at the same data center used by memSource and others!) during peak use. Unlike the barbed-wire, unstable and unfriendly solution Across, which has achieved some popularity in its native Germany and elsewhere through sales tactics relying on fear, uncertainty and doubt regarding illusionary or delusional data security, memSource works, works well, and the data are portable elsewhere if a company or individual makes another choice some day.
But damn... it's just not very efficient for professional work, especially not for those of us who have amassed considerable personal work resources and become habituated to other tools like SDL Trados Studio, Déja Vu or memoQ like a carpenter is to his time- and work-tested favorite tools. Trading one of these for the memSource desktop editor or, God forbid, the browser-based translation interface feels worse than being forced to do carpentry with cheap Chinese tools cast from dodgy pot metal. Riccardo mentions a few of the disadvantages, and I could fill pages with a catalog of others. But compared to some other primitive tools, it's not so bad, and for those with little or no good experience with leading translation environment tools, it may seem perfectly OK. You don't miss a myriad of filtering options to edit text or sophisticated QA features if you are still amazed that a "translation memory" can spit out a sentence you translated once-upon-a-time if something similar shows up six months later.
And as mentioned, memSource - or some other tool - may indeed be the best solution on the project management side. So what's a professional translator to do if an interesting project is on offer but that platform is unavoidable? Riccardo's tips on how to process the MXLIFF files from memSource in memoQ offer part of a possible good solution which would work almost equally well in most other leading tools as well these days. One additional bit is needed in the memoQ Regex Tagger filter to handle the other tag type (dual curly brackets) in memSource, but otherwise the advice given will allow safe translation of the memSource files in other environments. I can even change the segmentation in memoQ if, as usual, the project manager has failed to create appropriate segmentation rules in memSource to accountfor some of the odd stuff one often sees in legal or financial texts, and this does not damage or change the segmentation seen later when the working file is returned to memSource.
Even concerns about the "lack" of access to shared online resources in memSource if an MXLIFF is translated elsewhere are easily addressed. A few useful things for this include:
pretranslation of the memSource files to put matches into the target before transferring to other environments,
leaving the browser-based or desktop editor for memSource open in the background for online term base or TM look-ups, and
occasionally exporting and synchronizing the MXLIFF in memSource to make the data available to team members working in parallel on a large project - this takes just a minute or two and allows one as much time as needed for polishing text in the other environment.
The last tip is particularly helpful to calm the nerves of project managers who are like mother hens on a nest of eggs which they fear might in fact be hand grenades and who panic if they don't see "progress" on their project servers days before anything is due. One can show them "progress" every twenty minutes or so without much ado if so inclined.
I am past the point where I recommend any translation memory management server in particular for agency and corporate processes. There are advantages to each (except Across, where these are actually hallucinations) and disadvantages, and where I see real problems, it is seldom due to the choice of platform but rather the lack of training and process knowledge by those responsible for the processes. The bright and shining prospects of a translation server are easily sold with a slick tongue, but without an honest analysis and recommendation of needs for initial and ongoing staff training these too often end up being bright and shining lies. I think very often of a favorite German customer who invested heavily in such a system four or five year ago and has not managed one single successful project with the system in all that time. This makes me sick to think of the waste of resources and possibilities.
So on the project management and process ownership side, memSource may be a great choice. Certainly some of my clients think so, and the improvements in their business often back this belief up. And for those who work with gangs of indigent, migrant or sharecropping translators whose marginal existences make the investment in professional resources like SDL Trados Studio or memoQ seem difficult or undesirable, it may be all that is needed by anyone.
The good news for those who depend on the efficiency of a favored tool, however, is that with a few simple steps, we need not compromise and can get full value from our better desktop tools while supporting interesting projects based in memSource. So each side of the translation project can work with what works best for them, without loss, compromise, risk or recriminations.
And the translating quail who start out in a dark box with a stunting lack of possibilities can look forward to the real possibilities of work liberation in a larger environment richer in healthy possibilities and rewards.
A recent ripple in the social media pond concerned the demise of London-based Fluently.io, a platform with pretentions of replacing human interaction in translation project management with a glory hole of electronic anonymity into which companies could plug their projects to be serviced by its team of digital sharecroppers. Aside from an understandable lack of enthusiasm on the part of venture capitalists, who have likely had their fill of such "innovation" promising to conquer great linguistic landscapes, things appear to have fallen apart after a year because wordworkers mostly had better things to do. Like washing their hair, for example.
Fluently is another of many examples where the desire for innovative imitation generated sound and perhaps some occasional fury among companies hoping for the satisfaction of a translated quickie, but made no waves, left just a bit more brown scum in the pond. The worldwide internet web has a lot of life in its tides, many niches where life and scum can proliferate, even depths so far from the light that one can look at the Smartling business concept and believe it to be unique and worthy of investment, because the better angelfish of linguistic Nature are swimming with that concept far away in sunnier, more accessible waters with fewer denizens drunk on pressure and nitrogen narcosis.
The War on Common Sense waged by a cabal of greedy, occasionally deluded fools with the help of some who merely have a healthy, but misdirected intellectual curiosity, tells us that machinery physical and virtual can automate away the pain of human interaction and our inevitable disappointment over words and actions which do not follow the algorithms of profit accumulation for a chosen few. If there is a God of Translation Technology, that is surely Janus, but it is often hard to understand which of His faces is toward the future, which toward the past best left behind.
There are prophet pretenders, like Robert "Sketchy" Etches, who preach that the future face is toward machine pseudotranslation and declare those who do not suck the firehose of bulk electronic content for every drop of profit to be had are fools and dinosaurs destined to perish. I suppose that those who choose to linger by a cool, clear spring and savor its content are equally fools for not drinking deeply the salty vastness of the oceans and using their waters to grow food in their gardens.
A viable future of health and prosperity for all of us will use technology like a pair of shoes to protect us from the stones and thorns on the road, help to climb over the barriers we face, but it is our human motor capacities that take us on the paths our sound human minds choose. How can a static algorithm adequately serve our often complex, surprising social and commercial needs with our desires for fresh variety and innovation? Is our wardrobe really enriched by an automated straightjacket?
The CEO of the Fluently failed venture, Karin Nielsen said that “Translators are their own worst enemy. They could ditch agencies and earn more money. But they miss the human interaction.” As surely many translation buyers would, particularly those with a real concern for the communicative quality of the texts they pay good money to translate. But translators and translation buyers do have an alternative in which nothing goes amiss: a direct relationship, facilitated perhaps by the modern technologies of communication, but with people and their productive, creative interactions at the hub of the commercial wheel. And sometimes a good agency with a sound understanding of human needs in complex processes is essential, but seldom can satisfaction be had from automation if it confuses the avoidance of responsible and sometimes uncomfortable human participation with real productivity.
For those of you who thought that "House of the Rising Sun" was an Animals original, think again. It's likely that the song predates the recording of Leadbelly's wife here; the traditions of translation and the often similar business described here go back a long time, and these days, they seem to intersect particularly, particularly if one is "in a relationship" with a large Linguistic Sausage Producers (LSPs) like thebigword, which recently issued one of its periodic demands for translator rate cuts in a year in which record profits were posted and fat bonuses paid (see "Meaty Payday for thebigword Director").
Often when veteran translators gather at conferences, online or even down the road for coffee, the subject of project management quality - or the lack thereof - at companies like thebigword, TransPerfect, Lionbridge et alia comes up. There is a widespread impression that these big agencies hire recent university graduates as staff to recruit, test and manage translators, editors and interpreters for their corporate and government clientele. I cannot count how many times some outraged language service greybeard like me has griped about the stupidity of some PM who is presumed to be not only wet behind the ears but in other ways as well, not having yet graduated from diapers.
I am pleased to report that these assumptions appear to be baseless, at least as far as thebigword is concerned. After a tip from one colleague, I began to research the impressive qualifications of the human interfaces at this LSP using their LinkedIn profiles. Here is some of what I found:
Clearly, the next time I do a translation related to veterinary science or training dogs to track and hunt, I will need to take care, because my work might be reviewed by a volunteer dog handler. And I'm sure that these big sausage shops have the erotica angle covered too.
Reviewing the educational histories of some staff at thebigword who claim to recruit and test translators, I found it interesting to note that university education did not appear to be a job requirement. No matter; I can name two good linguists who never attended university, and I'm sure there must be a third one out there somewhere. With project management skills, of course.
So, dear colleagues and corporate clients, the next time you are frustrated in your dealings with some large translation agency and start to grumble about the qualifications of recent university translation studies graduates, be careful. My initial research shows that you may owe a big apology to some recent grads.
If you are looking for an exit strategy from the bulk market bog, don't let the glass door hit you in the a**e!
Here is an opportunity to spend the day learning from one of the world's leading industrial terminologists and the current president of the German Association for Terminology (Deutscher Terminologie-Tag) in the next of Stridonium's scheduled professional education events in the Netherlands. I made Mark's acquaintance some 14 years ago as a systems consultant, software developer and sometime translator for an electronic archiving solutions provider and SAP integrator. We needed to get the SAP terminology in the translations of our software manuals right, and I soon learned that he was the man. He also very unbureaucratically made the French, German and English terminology available to me in formats I could use with Trados and Déjà Vu in the days before the current online terminology portal for SAP, when the only game in town seemed to be a CD that was never up to date. This gave me an edge in certain areas of technical and business translation for years, for which I was very grateful. It was, alas, another ten years before I could made that acquaintance a face-to-face one at the Warsaw conference for Translation Management Europe, where I also discovered that he was a gifted speaker and a patient teacher with a wealth of inspiring examples.
On October 29, 2014 at the Restaurant Hotel Savelberg in Voorburg (NL), just a few minutes by car or train from The Hague, Mr. Childress will be conducting a full-day workshop with an overview of practical terminology management:
The basics of terminology theory and practice in an organization
Deciding between process-based or project-based approaches to terminology issues
Simple pro-terminology arguments you can use to convince your managers, your colleagues, your clients – or yourself!
Get started climbing the terminology mountain, one step at a time
The cost for the workshop is €375 per person (€325 for Stridonium members). Register by August 25th to receive the Early Bird rate of €325. Further information on the schedule and registration are now available on the Stridonium events page.
In Mark’s own words,
"This one-day seminar gives an overview of topics related to practical terminology work. No academic theorizing, no technobabble, no sales pitch – just good solid tips you can use to make your work run more smoothly."
*******
Mark Childress has a B.A. from Humboldt State University in California and an M.A. from Heidelberg University in Germany. He joined SAP AG in Walldorf, Germany in 1995 as a translator and has been responsible for the company’s terminology management since 1998. He is the current president of the German Association for Terminology (Deutscher Terminologie-Tag / DTT). Mark gives frequent lectures and training on terminology management to technical writers, translators, and universities and has written articles on terminology work for publications including MultiLingual and eDITion, the journal of the DTT.
Every translation environment tool has its own approach to project management and languages. Recently, a colleague asked for advice on outsourcing options for a client project which may involve a number of target languages translated from an English source text. I think her usual tool is some flavor of SDL Trados Freelance, but the five-language restriction on freelance software versions from SDL means that Studio is not an option in this case without an expensive upgrade to SDL Trados Studio Professional. This might be a worthwhile option, though it's difficult to judge in this case, because I don't know if this sort of project will be part of the future routine.
As I recall from my days as a Déjà Vu user, projects could have multiple target languages, but without the Workgroup version, collaboration was made difficult by restrictions on the bilingual files ("external views"). I don't know if this is still an issue in DVX3, because the uncertain future of Atril makes me reluctant to invest much study time in that tool.
memoQ does not restrict the languages one uses, but creating a project with multiple target languages requires the Project Manager edition. Kilgray doesn't talk much about this edition of memoQ and usually tries to link it to a server license sale (or a memoQ cloud subscription); if you look on the Kilgray web site, you will find very little information. I think the license typically costs about €1500, with €300 (20%) annually for maintenance upgrades and support. Quite a bargain, actually, and with the PM version one also gets access to another well-kept secret: the memoQ client API, which can be used to automate or simplify a number of project management processes. And of course with the PM edition one can create convenient "handoff packages", which provide convenient resource bundles for collaboration with other memoQ users with compatible versions of the translation environment tool.
But the memoQ PM edition is total overkill for someone who typically needs only individual language pairs for work and is faced only rarely with the need to manage multiple target languages from a source language. If there are just a few languages involved, it's probably not a big deal for someone with the memoQ Translator Pro edition to create several projects (one for each target language needed). There is, however, another option worth considering in some cases: using the Translator Pro edition to manage a multilingual project created with the PM edition.
If a multilingual project is created with the memoQ Project Manager edition, the individual target languages are available in the memoQ Translator Pro edition. A text imported with the target set to "All languages" is automatically put in every target language in the project; suitable bilinguals (XLIFF, RTF bilingual tables or TWB-/Wordfast-compatible unclean DOC) can be generated from each individual target language.
A downloadable example of a memoQ project backup to test for memoQ 2013R2 is here.
Using a project with multiple target languages in the Translator Pro edition requires, of course, that the original project be created by someone with the Project Manager edition. And the sophisticated functions for reporting, package creation, etc. are not available when the project is open in the Translator Pro edition. But translation memories, termbases, LiveDocs and other resources can in fact be managed for multiple target languages in the project. The work can be reviewed or prepared for external proofreading, target files can be created in all the languages, and a number of other simple management tasks can be performed. In many cases this may be enough.
Segmentation difficulties are often one of the most troublesome aspects of working with translation environment tools. Learning to configure segmentation rules correctly and applying that knowledge can save many hours of wasted time in alignments and translations and avoid filling translation memory resources with garbage from fractured translations of partial sentences with missing verbs, subjects and whatnot.
The usual alternative remedy for inadequately configured segmentation rules which lack the segmentation exceptions needed for abbreviations, for example, is to use the "join" function (Ctrl+J), and sometimes the split function (to manage very long, unwieldy clauses such as one might find in a patent text, and the join the parts again later).
There are situations where joining and splitting of segments is blocked. This is the case with any file which is part of a view, for example; the view must be deleted before segments can once again be joined or split. Segmentation changes are also not possible in a server project which has not been set up to allow them.
There are several options or documents available to project managers when setting up memoQ server project. But to enable translators to correct unfavorable segmentation, there is really only one choice:
If Desktop documents (no web translation) is selected, then on the dialog page which follows, changes in segmentation can be enabled:
If a project manager does not configure a project to allow this, for example because a document is being split between multiple translators (which does not allow for segmentation changes for technical reasons), the full responsibility must be assumed by the project manager for any segmentation issues. The imported documents should be examined carefully, and if any problems are observed, the segmentation rules should be modified and the documents re-imported. Doing otherwise may unavoidably result in garbage being written to the project's translation memory.
This is a very important point for memoQ trainers to emphasize when they are teaching users of the memoQ server to set up projects. Segmentation topics should be covered thoroughly, and the potential for bad results should be understood clearly if translators are given badly segmented documents they cannot fix. Project managers should also be encouraged to avoid restricting translators options in ways which are likely to harm the quality of the results and make parts of the translation unfit for later re-use.
A good rule of thumb is to choose the desktop documents option for projects always unless there are very urgent reasons not to do so. In this way, you will avoid upsetting your translators by forcing unmanageable, fractured sentence fragments on them, and you will be assured of better quality translation memory resources.
Some years ago I was relaxing at an informal occasion with one of Kilgray's directors, who expressed concern that the growing number of features might lead to confusion among users and obscure the basic simplicity of memoQ, which at the time was the company's only product. I think version 3.5 or 4.0 was the current release at the time of our chat. I disagreed with him at the time, because compared to other tools at the time, memoQ was easier to understand, more ergonomic than any of the leading tools. It still is.
But as most users of the software know, things have gotten a lot more complicated since then. As memoQ has taken a forward position in the market for translation environment tools, many features have been added (by necessity one could argue) to accommodate various interest groups. Some of these features I find very good and useful, others inspire a response that cannot be expressed in polite company, because they support server workflows which I personally find exploitative and offensive in the hands of some companies. But any tool can be used for good or bad purposes, and one of my favorite tools for planning my time accurately - the homogeneity analysis - is sometimes abused by Linguistic Sausage Producers to put further economic pressure on individual translators, yet I would not wish it to go away.
Many, many features to master for a wide range of work challenges. Even the so-called "experts" often don't have a clear overview. This problem is, of course, common to almost any popular software application: the situation with SDL Trados Studio is similar, and look at Microsoft Word, my God. An "expert" might understand 10% of Word's features.
Kilgray, it must be said, does try to go the extra mile and provide information to users in many ways so that they can work effectively and avoid frustration when navigating the sometimes tricky paths one must follow in a complex project. Each month the company offers free webinars, and recordings of these are available for later reference in most cases. There is also a knowledgebase (which is quite a challenge to keep up to date given the software's rapid pace of development). The company has also produced a number of shorter instruction videos. The Kilgray YouTube channel has a wide mix of material, including some recordings of past conferences, which are not always easy to understand but which contain a lot of interesting and useful material for some groups. There is also an extensive collection of user guides and white papers on the Kilgray site.
More recently Kilgray as taken its first steps with integrated e-learning, adopting the Moodle platform popular with many educational institutions. I think this is a very interesting new direction; since late spring I have been researching and testing such platforms myself, and I expect very good things to come of this in the future.
The first Kilgray e-learning course was a memoQ basics course, consisting of ten recorded PowerPoint lectures, each about 10 to 15 minutes long. There is a short review quiz at the end to give learners some feedback on what they have retained, and a certificate is offered for those who get a certain number of questions right. Although this course structure uses only a small part of the potential of the Moodle platform, it is easier to navigate and find particular information than it might be in a webinar, for example. The basics course is free to any memoQ user with a current support contract and is worth a look. Others can take the course for a fee of €90 (which is close enough to the cost of annual support that you might as well update your contract and enjoy the updates it includes). Feedback and suggestions should be sent to support@kilgray.com to help in the planning of further courses to help users.
More recently, another Moodle course was published for project managers working with the memoQ server. I know from my own experiences as a consultant and someone who occasionally has to deal with the frustrations of misconfigured server projects set up by my clients that there is a real need for better training for those who work with the memoQ Server. Many of my clients who have adopted this solution have had very little prior experience with CAT tools at all, and given the many pressures of a production environment, they may find visual media a more effective form of support than "RTFM".
The structure of the PM training course is similar to that of the memoQ basics course: ten recorded PowerPoint lectures in English. There is also a quiz at the end. The course is available free to all licensed memoQ server users, who should contact their Kilgray support representative to arrange access.
As the screenshot above indicates, Kilgray has moved its e-learning resources to Language Terminal, and along with all the other plans for that platform, there are many under consideration to expand the scope and quality of learning resources available, not only for Kilgray's products, but perhaps for other knowledge which can contribute to their successful use in the complex world of real projects.
What is your experience so far with Kilgray's training resources? What has worked for you? What has not? What kind of resources do you think would help you and those with whom you work to master the challenges of your daily routine?
Many corporate translation projects today are very complex. Fewer texts are based on paper documents, but all the more derive from web sites, software, databases, multimedia, engineering drawing files or publishing layouts, and they may often involve coordinated efforts for many languages for many formats. Project managers must work with specialists in a variety of fields such as translation, localization, software development and web design, advertising and commercial graphics. A roadmap is critical to cope with such challenges. Reliable roadmaps are based on grounded, practical knowledge of project management in general as well as the specifics relevant to localization.
Project management not only helps organize and define strategies, but also provides flexibility: the flexibility to refine something which works to work even better, and the flexibility to respond when things don’t go as expected. Good project management increases the probability of success and offers peace of mind, which increase customer satisfaction and provide opportunities for growth.
The workshop (in English) on November 4th and 5th in Wiesbaden, Germany will enhance your practical project management skills for translation and localization. It is designed for language service experts, corporate executives, project managers, heads of translation departments and translators interested in project management.
The workshop will be taught by Loctimize partners Angelika Zerfass and Martin Beuster. Ms. Zerfass is an independent trainer and consultant for translation technologies with more than a decade of experience in the field, a frequent speaker at localization conferences and university lecturer. Mr. Beuster is the managing director at Context (Ireland) and has over 25 years of success in the language services industry. As a training consultant, he offers services to corporate clients, professionals in multi-lingual environments and language service providers.
Further details and registration information are available here.
