| Pages in topic: [1 2] > | Extended task for same rate Thread poster: Åsa_Maria K
|
|---|
Åsa_Maria K 
Sweden
Local time: 06:33
English to Swedish
Hello,
I have cooperated with an agency for quite some time and have always been on good terms with the PMs. I have regularly translated for a certain end-client. One day I get the message that all jobs for this end client from now on shall not only be carefully translated, spell checked and delivered as bilingual files (as always), but are also to be returned to me as a Word document to be checked for the following:
“Run the speller in Word and have a final check on... See more Hello,
I have cooperated with an agency for quite some time and have always been on good terms with the PMs. I have regularly translated for a certain end-client. One day I get the message that all jobs for this end client from now on shall not only be carefully translated, spell checked and delivered as bilingual files (as always), but are also to be returned to me as a Word document to be checked for the following:
“Run the speller in Word and have a final check on the file, in its context. Make sure that there are no errors and typos in the file and check the following:
-Brand/product names are consistent with the source.
-Numbered lists have correct numbers/letters in the file.
-Punctuation is consistent in all numbered and alphabetical lists.
-There are no double spaces in the translation
-There are only one blank space after colons and after number in lists.
-Placeholders are the same as in source text.
-Decimals are written with comma.
-The file title/header format is consistent with the source
-CAUTION, NOTE, and WARNING statements are consistently translated.
-Check numbers using consistency
-Any change should be implemented in the bilingual file.”
I think the list above is quite an extensive task to be included for the same rate as was earlier paid for translation only. The translators of the other language combinations seem to accept this. Today I received a 7600-word job and I am beginning to feel it is becoming quite a lot of unpaid work. Would it be wrong to question this procedure? Rhetoric question, I know, but I guess I need some feedback. ▲ Collapse
| | | | | This isn't extra work! | Jan 12, 2011 |
These are things which should be taken for granted in any translation.
| | | | Kevin Fulton
United States
Local time: 00:33
German to English
| These are standard requirements | Jan 12, 2011 |
I'm with Phil. Before submitting a translation I perform a spell check on the bilingual file as well as the target file. Using XBench will identify many inconsistencies in the translation. Numbers should always match. These are standard QA procedures that every translator should perform prior to submitting a finished project.
Extensive formatting, DTP or editing of graphics, however, fall outside the normal purview of the translation activity, but your client isn't asking for that.
| | | | NMR (X)
France
Local time: 06:33
French to Dutch
+ ...
You asked for feedback, so here it is. In my opinion this is not an extended task. Carefully translated and proofread translations should not contain this kind of errors. As for myself, I always proofread and check at least two times, on the screen and on paper, and always deliver a file which is ready to be printed.
But I know, there are more and more people who think that translation is only typing in another language and who deliver their first rough translation. That's why you r... See more You asked for feedback, so here it is. In my opinion this is not an extended task. Carefully translated and proofread translations should not contain this kind of errors. As for myself, I always proofread and check at least two times, on the screen and on paper, and always deliver a file which is ready to be printed.
But I know, there are more and more people who think that translation is only typing in another language and who deliver their first rough translation. That's why you received this. ▲ Collapse
| | |
|
|
|
| Not extra work but responsibility | Jan 12, 2011 |
philgoddard wrote:
These are things which should be taken for granted in any translation.
It is our responsibility to deliver our translations proofread and checked for compliance with client's specifications such as terminology, brand names, style, cultural preferences, etc. The closer you follow the specifications the less "returned" Word document you will receive.
| | | | Andrea Piu
Italy
Local time: 06:33
English to Italian
+ ...
If I have to be honest, I can not see any extra task in the list you posted. I always use a spell checker and go through the document to be sure the template is not changed somehow.
I would also point out the importance of a correct localization when you deal with punctuation, decimals and units of measurement, as certain languages use a different styles and/or comas instead of dots.
Moreover, brand names are logically the same in English, Italian, Spanish, etc. unless there are dif... See more If I have to be honest, I can not see any extra task in the list you posted. I always use a spell checker and go through the document to be sure the template is not changed somehow.
I would also point out the importance of a correct localization when you deal with punctuation, decimals and units of measurement, as certain languages use a different styles and/or comas instead of dots.
Moreover, brand names are logically the same in English, Italian, Spanish, etc. unless there are different names for different nations but, as far as I know, for example, McDo****'s is the same in every nation. ▲ Collapse
| | | | LEXpert
United States
Local time: 23:33
Member (2008)
Croatian to English
+ ...
| Well, if the file has been out of your hands in the meantime... | Jan 12, 2011 |
As Phil has stated, these are normal considerations for any translation, as is following whatever style guide is mandated by your client. Surely you are paying careful attention to them anyway as you translate.
However, Asa, I understand from your post that so far your deliverable has been the bilingual file. Now you are additionally being returned the clean Word file to check. Since it has been out of your hands, potentially heaven-knows-what has been done to it by any number of p... See more As Phil has stated, these are normal considerations for any translation, as is following whatever style guide is mandated by your client. Surely you are paying careful attention to them anyway as you translate.
However, Asa, I understand from your post that so far your deliverable has been the bilingual file. Now you are additionally being returned the clean Word file to check. Since it has been out of your hands, potentially heaven-knows-what has been done to it by any number of people before getting back to you. In that case, you have to re-check all of these things again, which is basically an additional proofing job, compared to your previous arrangement (deliverable=bilingual file). I ran into a similar situation where I was asked to edit/proof a ttx, and return the ttx. After the job, client sends me the pdf generated from the ttx to proof - again. I felt this requirement should have been stated up front or treated as an adder to the job. In the end - decent client, and the adder was minor in relation to the entire scope of work, so I ended up not pressing the issue, but still feel a little taken advantage of.
In any case, I hope I am correct in assuming that issue is not that you are being asked to DO these checks, but (essentially) to REDO them after getting the cleaned file back.
If you feel it is costing you extra time, you can adjust your rate, I suppose.
[Edited at 2011-01-12 19:21 GMT] ▲ Collapse
| | | | Robert Forstag
United States
Local time: 00:33
Spanish to English
+ ...
| This is nothing more than a standard list of specifications.... | Jan 12, 2011 |
...as others have already said. No cause for complaint or indignation here, as far as I can see.
| | |
|
|
|
Samuel Murray
Netherlands
Local time: 06:33
Member (2006)
English to Afrikaans
+ ...
| There is nothing wrong with a good checklist | Jan 12, 2011 |
Åsa_Maria K wrote:
One day I get the message that all jobs for this end client from now on shall not only be carefully translated, spell checked and delivered as bilingual files (as always), but are also to be returned to me as a Word document to be checked for the following: ...
Are any of the items in the checklist unreasonable?
Do you keep a comments file for each client that you consult before doing any work for that client, in which you write any special requirements that they have? It's a good idea... then you'll notice in the comment file that this client wants you to do stuff like delete double spaces, etc.
I think the list above is quite an extensive task to be included for the same rate as was earlier paid for translation only.
Yes, well, I guess the client realised that using a bilingual format has its drawbacks, and one of the biggest drawbacks is that the translator can't see what his translation looks like until the final file is created, and by that time the translator may be unwilling to go back to the bilingual file to make a tonne of small corrections.
My attitude is that if the client wants me to use a bilingual format, then the bilingual format is the final file, and if he wants me to tweak it so that the exported file looks nice, then that is charged extra. If the client doesn't care about the bilingual format but cares only about the final product, then he gets a good final product, with tweaks and all, for the same price. I think the concept of bilingual files is stupid, stupid, stupid, but if a client wants me to use it, then I'll do it, as long as the client realises that he takes the blame for deficiencies created by the bilingual format.
Unfortunately I have no spine, so while this is my attitude, it isn't my practice.
| | | | | Before delivery requirements | Jan 12, 2011 |
Åsa_Maria K wrote:
“Run the speller in Word and have a final check on the file, in its context. Make sure that there are no errors and typos in the file and check the following:
-Brand/product names are consistent with the source.
-Numbered lists have correct numbers/letters in the file.
-Punctuation is consistent in all numbered and alphabetical lists.
-There are no double spaces in the translation
-There are only one blank space after colons and after number in lists.
-Placeholders are the same as in source text.
-Decimals are written with comma.
-The file title/header format is consistent with the source
-CAUTION, NOTE, and WARNING statements are consistently translated.
-Check numbers using consistency
-Any change should be implemented in the bilingual file.”
Those are things that should be done before delivery of the job. By getting an opportunity to check after cleanup, you are getting a second chance to pick up on small things you might have let slip.
| | | | Laurent KRAULAND (X)
France
Local time: 06:33
French to German
+ ...
A question: what was your standard procedure for that end client before you were sent this checklist?
| | | | Henry Hinds
United States
Local time: 22:33
English to Spanish
+ ...
In memoriam
For my work all those requirements mentioned are standard because I impose them on myself. I could not think of delivering less.
| | |
|
|
|
I agree with Kevin that it is no more than QA procedures that you can do within trados before sending your bilingual file.
Once you do that you can confirm your client that it is not necessarily doing it again in the word file.
I will do that, if I were you...
Good Luck
| | | |
It depends... If your client asks you to perform these checks on a file which is different form the one you sent you should be paid for the job. I very often work on complex manuals, with plenty of tables, graphs and pictures, and the client sends me ttx files to be translated with TagEditor. Then the client creates a pdf from the translated file and sends it back to me to check: I get paid for this extra job at my proofreading rate.
Alessandra
| | | | Nikita Kobrin
Lithuania
Local time: 07:33
Member (2010)
English to Russian
+ ...
| I don't see anything extra or 'extended' | Jan 13, 2011 |
Åsa_Maria K wrote:
“Run the speller in Word and have a final check on the file, in its context. Make sure that there are no errors and typos in the file and check the following:
-Brand/product names are consistent with the source.
-Numbered lists have correct numbers/letters in the file.
-Punctuation is consistent in all numbered and alphabetical lists.
-There are no double spaces in the translation
-There are only one blank space after colons and after number in lists.
-Placeholders are the same as in source text.
-Decimals are written with comma.
-The file title/header format is consistent with the source
-CAUTION, NOTE, and WARNING statements are consistently translated.
-Check numbers using consistency
-Any change should be implemented in the bilingual file.”
I don't see anything extra or 'extended' in the above listed requirements: just normal procedure that any of us should always follow even without a special reminder. I do everything mentioned above with any project I deliver.
| | | | | Pages in topic: [1 2] > | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Extended task for same rate | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
| | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news
