But how are Localization Engineering hours invoiced? Are they cheating me?
For those of us who enjoy TV shows, we are incredibly fortunate; there are numerous outstanding shows available, more than enough to occupy our time. However, even with this paradox of choice, when I finish watching a great series, a void emerges within me... and now what? Which TV show should I become engrossed in next?
Breaking Bad evoked that sentiment in me.
Over the course of five captivating and frenetic seasons, I was completely engrossed. I appreciated Vince Gilligan's work so much that when Better Call Saul was introduced, I held reservations about its necessity. Prequels, sequels—I usually feel a sense of tedium when I hear these terms.
Yet, with Better Call Saul, I was mistaken. It is an exceptional show! Within it, we witness Jimmy's transformation into Saul, the morally flexible lawyer we encounter in Breaking Bad. Strangely, the other day, a scene reminded me of a situation I have occasionally encountered in our realm of Localization...
In this scene, Jimmy concocts "a budget" for his "services rendered." He delineates multiple tasks of questionable credibility in order to reach a specific monetary goal. As he explains his process, it sounds inauthentic, utterly contrived.
However, in the end, he has his budget, complete with generic tasks that come across as deceptive. In our industry, a parallel to such a budget might be... the hours of Localization engineering. Not because they are false, not because they lack authenticity, not because they lack importance, but simply because clients or individuals less familiar with the world of localization will seldom grasp the true significance of those hours.
The hours of a localization engineer are crucial for the success of a Globalization project. However, due to a lack of understanding about their role, these budgets often resemble the kind that Jimmy creates in Better Call Saul to account for his questionable activities.
Hence, the focus of my post this week is to shed light on what one might encounter in an invoice that includes hours of localization engineering. These activities aren't just lacking in authenticity; they are undeniably and authentically essential for achieving successful outcomes in a localization project!
When we examine a Localization invoice and notice a cost beyond the translation rate multiplied by the word count, along with any additional project management fees at the end, it triggers a sense of suspicion, almost like detecting something fake.
For this very reason, let's begin by elucidating the responsibilities of a localization engineer and delving into the reasons behind compensating them!
Localization engineering tasks can vary depending on the company, but in general, a localization engineer is responsible for performing a range of tasks required to set a translator in motion for a project. Through various tools and processes, they essentially isolate the content that requires translation, subsequently reintegrate it, and ensure it's ready for client delivery. This isolation isn't a simple undertaking and can be broken down into the following sequence of steps:
Before Starting Translation:
Identify and analyze all files containing content to be translated, including text files and even images with embedded text. This phase involves retrieving the source files from the client and conducting an analysis.
During this stage, they might also initiate the Internationalization phase. Not sure what that entails? Read my post HERE where I delve into this initially challenging term 🙂
Content Formatting: Frequently, the format of source files lacks consistency and can encompass a wide range of formats—RC, RC2, EXE, DLL, PDFs, Word, RTF, VBS, HTML, and more. Executing pre-formatting work is essential to create optimal conditions for translators to work their magic in bridging cultures through their words... how poetic!
During the Translation:
This phase revolves around being present and readily available to address translator inquiries. Whether it's a problem with accessing the TMS, aligning memory, or formatting tags, the localization engineer steps in as the troubleshooter. Localization engineering to the rescue!
After the Translation:
This phase focuses on assembling the final product. All the preliminary efforts to make the translators' work smoother now come together. This entails building and verification. What's being verified? Essentially, the localization engineer ensures there are no missing tags, placeholders are correctly positioned, markup isn't deleted, and paired languages are processed accurately.
At this juncture in the post, I hope we're gaining a better grasp of a localization engineer's role. Now, let's dive into the details.
How is their work charged? Basically, there are three scenarios:
Included in the Unit Price: This is the ideal scenario for clients but a challenge for Language Service Providers (LSPs). Unless files are impeccably prepared and ready for translators, it tends to be an unprofitable setup for service providers.
Price per Hour: Likely the most common and ultimately the fairest approach. What's encompassed within that hourly rate? As mentioned earlier—both pre-translation and post-translation tasks. However, it usually excludes localization engineering tasks conducted directly within the Translation Management System (TMS) or troubleshooting support for translators. Such tasks are typically covered by the final project management fee added in the invoice's summary section.
Microscopic-Level Breakdown: This is the least common type of invoice but necessary for complex projects. If, for instance, we're tasked with translating a 12-language website, this level of detail proves invaluable. Similarly, for projects involving translating e-learning content into multiple languages, a detailed breakdown is essential. In these complex situations, the general hourly estimation might not be sufficient. Consequently, invoices may display a detailed breakdown of costs for items such as:
a. Pages per Hour
b. Glossary Development
c. Graphics Extraction
d. Desktop Publishing (DTP)
e. Cultural Assessment
f. Pseudo-localization Checks
Software localization is a more intricate endeavor than it appears. And if it ever seems easy at any point, it's precisely because localization engineers have diligently prepared everything to make it seem effortless! Hidden behind a well-executed translation are numerous complexities, often unnoticed. However, when they do become evident in an invoice, they might appear artificial, inauthentic—much like the billing practices of Jimmy McGill in Better Call Saul.
I hope you find this post insightful—whether you've learned something new about the tasks undertaken by localization engineers or you've received a TV show recommendation 🙂
Wishing everyone a productive localization-focused week ahead!
As always, your comments and feedback are greatly appreciated. Let's maintain the dialogue by sharing your thoughts below!
@yolocalizo
Transitioning from one job to another can be an enriching experience, or it can be a nightmare.
I have detected in my different movements, and after seeing many colleagues making transitions, that there are a series of usually effective tips.