Showing posts with label Sodrat Suite. Show all posts
Showing posts with label Sodrat Suite. Show all posts

Sep 16, 2012

Equivalent Rates in Translation Billing

This article appeared in its original form in September 2008 on an online translation portal. It has been moved here for better maintenance of the content and links. The original text has been modified  slightly and the link to the quotation tool updated. The rate equivalence calculator is part of the Sodrat Suite for Translation Productivity. An older post on this topic includes links to other tools for calculating rate equivalency.


*****

Billing questions are seen very frequently in the forums of popular translator portals or professional association sites. Often these concern whether translations should be billed by the word or agglomerated words (thousands or hundreds), lines, pages or other units in the source or target text. The answers to these questions reveal a wide range of approaches, which are often dictated by local convention, habit or simple fear. Often it is claimed that a particular method "does not make sense" because of compound word structures or other issues (which is frequently claimed for my language pair, German to English, for example). These claims are interesting, because other successful translators with the same language combinations often view things very differently. Who is right?

Before answering that question, let’s ask what sort of an answer can be trusted most. Would you stake your business on a “gut feeling” recommendation of another translator or translators when many others argue just as vehemently without evidence? Or would you feel more secure using a mysterious online calculator on an agency web site which purports to be based on a large body of text in the respective languages? Or would you prefer to see hard numbers based on your own translations that you have carried out in a number of different fields for various customers? Which approach do you think would give you the best basis for making your business decisions and protecting yourself against getting shortchanged in pricing?

I prefer to deal with real data from my own work. It not only reflects what I have been translating but also what I am likely to be translating in the next year or two. If I make a radical change I can quickly check and make sure that my pricing model is still “safe”.

To answer my own pricing questions, I created a spreadsheet in Microsoft Excel, which allows me to enter the actual data from individual projects and see what the relationship between target and source text pricing would be for words, lines and pages. You can have a copy of this spreadsheet to use yourself by downloading it here.

Because the true measure of price appropriateness is reflected in what one actually earns for the time spent working, a tracking calculator for the hourly earnings on each job was included in that spreadsheet to serve as a "control", but here I would like to focus on the relationship between different unit costing approaches and how to “adjust” prices to the units your prospect or customer is most comfortable with.

When I entered actual data from two types of translation work that I do (one specialized, the other a general category), I discovered some interesting things. I set up my spreadsheet to calculate the relative standard deviations (RSD) of the data, and what I found was that these were generally under 5%. What does this really mean? It means that if the data for your translation jobs is normally distributed, about 60% of the time the “actual” price relationship between two methods will fall in a “band” of plus or minus one RSD around the average, 95% of the time the actual relationship will be plus or minus two RSDs and 99% of the time it will be plus or minus 2.5 RSDs.

Still confused? Here’s a specific example from the downloadable spreadsheet:

If I want to earn € 0.15 per target word for a chemistry translation but the customer I am dealing with wants me to bill in source lines (allowing a “fixed price” to be calculated in advance – line rates are also common in Germany), I enter my desired rate in the little calculator table in cell B20. In cell E20 I see that I need to charge about € 1.27 per source line of 55 characters. How reliable is that figure? The relative standard deviation of the source line to target word ratio is just under 5% (some versions of the calculating spreadsheet in circulation do not include this figure, but it is accurate). This means that 99% of the time if you use this pricing, the “worst “real target word rate you achieve will be about 13.1 euro cents and the “best” you’ll do will be about 16.9 euro cents. If you work consistently with this pricing strategy your average earnings will be 15 euro cents per word. In many cases the bandwidth of variation will be much narrower than the example I have presented here. Compile your own data and see.

But what about the “exception” the fearful translator might say? One indicator of trouble for my language pair if I am using a source word pricing strategy might be an unusually low source word to source line ratio, which would indicate the likely presence of very long compound words in German. What do you do in a case like this? Raise your price if you feel like it. Use real data to show that this text really is different and must be priced differently from other work. Not everyone will agree with this idea, but you may have more success with it than you would expect. The important point here is that, by tracking actual data from your own work, you have a much clearer understanding of when rates may need adjusting. 

When you examine your own data you will find that the actual variation in earnings between the calculation methods presented is small in most cases, at least for European languages. If this is not the case for your language, then you will have hard numbers to use in your quotation. Negotiations based on fact often work better, though all this can be greatly outweighed or offset by psychological factors.

By using the rate equivalence spreadsheet or creating your own similar tool, you can navigate the hazards of various quotation methods with greater confidence, quickly determining equivalent rates in the units expected by prospects and customers. This will ensure that you reach your average earning targets and achieve the same average hourly earnings as with your familiar unit pricing. You’ll know how much you have to raise your word price or how much margin you have to reduce it if you are asked to quote by source word instead of target word or vice versa. Now get down to business.

The Sodrat Suite: delimited text to MultiTerm

The growing library of tools in the Sodrat Suite for Translation Productivity now includes a handy drag & drop script sample for converting simple tab-delimited terminology lists into data which can be imported directly into the generations of (SDL) Trados MultiTerm with which we've been blessed for more than half a decade.

Many people rightly fear and loathe the MultiTerm Convert program from SDL and despite many well-written tutorials for its use, intelligent, competent adult translators have become all too frequent callers on the suicide hotline in Maidenhead, UK.

Thus I've cast my lot with members of an Open Source rescue team dedicated to squeezing a little gain for the victims of all this pain and prescribing appropriate remedies for what ails so many of us by developing the Sodrat Software Suite. The solutions here are quick, but they aren't half as dirty as what some pay good money for.

The script below is deliberately unoptimized. It represents less work than drinking a cup of strong, hot coffee on a cold and clammy autumn morning. Anyone who feels like improving on this thing and making it more robust and useful is encouraged to do so. It was written quickly to cover what I believe is the most common case for this type of data conversion. An 80 or 90% solution is 100% satisfactory in most cases. Copy the script from below, put it in a text file and change the extension to VBS, or get the tool, a readme file and a bit of test data by clicking the icon link above.

To run the conversion, just put your tab delimited text file in the folder with the VBS script and then drag it onto the script's icon. The MultiTerm XML import file will be created in the same folder and use the name of the original file with terms as the basis of its name.

Drag & Drop Script for Converting Tab-delimited
Bilingual Data to MultiTerm XML

ForReading = 1
Set objArgs = WScript.Arguments
inFile = objArgs(0) ' name of the file dropped on the script

Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.OpenTextFile(inFile, ForReading)

' read first line for language field names
strLine = objFile.ReadLine
arrFields = Split(strLine, chr(9))

outText = "          "UTF-16" & chr(34) & "?>" & chr(13) & "" & chr(13)   
   
Do Until objFile.AtEndOfStream
 strLine = objFile.ReadLine
 if StrLine <> "" then
  arrTerms = Split(strLine, vbTab)
   
  outText = outText & "" & chr(13)
      for i = 0 to (UBound(arrTerms) )
        outText = outText & chr(9) & "" & chr(13) & chr(9) & chr (9) _
                   & "" & chr(13)
        ' write the term
        outText = outText & chr(9) & chr (9) & chr (9) & "" & _
               arrTerms(i) & "
" & chr(13) & chr(9) & "
" & chr(13)
      next
  outText = outText & "
" & chr(13)
 end if
Loop

outText = outText & "
"
objFile.Close
outFile = inFile & "-MultiTerm.xml"

' second param is overwrite, third is unicode
Set objFile = objFSO.CreateTextFile(outFile,1,1)
objFile.Write outText
objFile.Close


Nov 20, 2008

Calculating equivalent rates for translation billing

Many of us who have dealt with an international clientele have encountered different approaches to counting text for charging translations. Charging by the word is probably the most common practice, but in various places one might encounter calculations per hundred words (Australia), thousand words (UK), "lines" (common in the German-speaking countries), "standard" pages or other units. Then, of course, there is the matter of charging by the source text count or by the target text count.

These issues are discussed at great length and with great passion by many translators, some of whom are convinced that only certain methods protect one against being "cheated" with particular language combinations. I can't judge the validity of this belief for every language, but when I hear that opinion expressed for the language pair I work in, I know it is nonsense. In September 2008, I published an article on a translator's portal (since removed and found here) as well as a spreadsheet tool to help inject a little quantitative thinking into the debate.

Careful analysis of various types of documents show that the rates can be converted between all the common methods of calculation with very low standard deviations. Thus if you calculate the conversion factors between different methods (for example source words versus target lines), on the average (i.e. after doing a number of jobs) your earnings will be pretty much the same as if you had calculated using your familiar method. Individual jobs may be a bit more or a bit less, but it's important - unless you are looking at a one-off job for a client whom you will never deal with again - to take a long-term perspective and accommodate client requests if a quotation by a particular method is requested. I usually charge by source lines off 55 characters each (including spaces); if a British customer asks for a quotation in GBP per 1000 words, that's not a problem. (Well, given the rapidly dropping pound it might be, but currency exchange is another kettle of fish altogether. Maybe I'll deal with that another day.)

The Excel spreadsheet I put together is designed to make rate comparisons between two types of texts and to track hourly earnings on individual jobs. After all, what is most important isn't the rate per word/line/page/etc. but how much you earn for a given amount of your time.

Alessandra Muzzi of Amtrad Services in Italy has put together a very nice online fee conversion calculator (as well as a downloadable spreadsheet). This has been around for a number of years and is much more user-friendly than my spreadsheet, but comparisons between text types are more difficult (you have to enter data in two different workbooks) and there is no tracking feature for hourly earnings. Still, for getting a quick idea of how one calculation method can be converted to another, her tools are quicker and easier to use than mine.

Update September 16, 2012: After realizing recently that this tool has been unavailable for a longer period after a domain change, I reviewed it for current relevance and decided to add it to the growing Sodrat Suite for Translation Productivity, part of an Open Source resistance movement to the abusive complexities of ill-conceived technology in the translation profession.

Nov 16, 2008

The "Target Price Defense Tool" (updated)

Some time ago, after reading the millionth online discussion of the evils of CAT discount schemes and how to counteract them, I decided to add a more quantitative tone to the discussion. I do not share the blanket objections that some have to discount schemes of any sort; if I have an easy text to do that consists of 50% repetition, I am open to discussing the rate for the repeated content. However, I do find some of the CAT schemes proposed by agencies to be beyond ridiculous, and anyone who is serious about paying nothing or a few percent for matches and repeats will be greeted with a hearty, spontaneous laugh for starters.

Clearly, in many cases there is a need to look closely at proposed CAT schemes and consider alternative schemes or word price increases to achieve fair overall compensation. With that in mind, I created an Excel spreadsheet I call the Target Price Defense Tool to help translators (or other service providers) evaluate alternatives. It is available here.

Update September 16, 2012: After realizing recently that the tool has been unavailable for a long time after a domain change, I reviewed it and decided to add it to the growing Sodrat Suite for Translation Productivity, part of an Open Source resistance movement to the abusive complexities of ill-conceived technology in the translation profession.