Dear all,

be notified that the next payments will be released on January, 17.
Reason: As we are located in Israel, tomorrow - January, 15 - is already the start of our weekend. We are back on Sunday.

Reminder: Don’t forget to request your payment as withdrawal on the site and send us the invoice.

Thanks for all the work done,
Ursula

Hi all,

before addressing the new version, I simply must use this opportunity to point out some of the most common mistakes done by translators. Mistakes that cause us a lot of problems and consume a lot of our time and energy:

1.) Missing parts in translations:
It happens over and over again that you miss out on parts of the translation. One reason - you simple do not scroll down to the end of a text that was entered in the plain text area.

2.) Spelling mistakes!
Our customers are entitled to receive even the shortest translation without spelling mistakes. Therefore - just as mentioned on the website - do not make your translations directly in the translated text area. Always use MS Word or any other application that has a spellchecker.

Regards,
Ursula

Dear all,

one function of our system needs clarification: Uploading your translation as a file.

The main point is that uploading the file still doesn’t submit the translation!

You still have to click the “Submit Translation” button to complete your translation.

Dear all,

Large parts of Babylon, including the accounting department, will be on vacation between 11-19th of December.

Therefor we will have the Mid-December (usually scheduled for 15th of December) already on 10, December 2009. All invoices and withdrawal requests reaching us later will enter the End-December round.

Don’t forget: We need both an invoice by email (to: ursula@babylon.com) and a withdrawal request through the website.

Regards - Ursula

Hi all,

please when sending us an invoice per email, make sure that you also request the withdrawal of the same amount at the website: My Profile -> My Transaction -> lower part of the page.

Only like this your payment request gets document by our system.

Thanks for your attention,
Ursula

Dear team members,

please pay attention that with the change of the URLs from LingoZ to BHT (Babylon Human Translation) also the no-reply sender of the job offers changed to: noreply@translator.babylon.com.

Make sure that this sender: noreply@translator.babylon.com is added to your approved sender list.

With best regards,
Ursula

Hi all,
In answer to a question placed by Anna M. please notice that I have no possibility to make a job available to a translator again after “Decline job” was clicked.

Actually (tell me if you think otherwise) I am about to instruct our programmers to remove this function completely. It seems more a source for misunderstanding than to data input I can work with. If - after looking at a job - you don’t want to take it out of a very specific reason (e.g. wrong language has been enter by the customer, word count seems to be wrong) - just don’t accept it and send me an email about the problem.

Best regards,
Ursula

Hi all,

we temporarily had to close the language pairs Japanese to English due to a wrong word count.
We corrected and implemented the same word count algorithm used by MS Word, which is a benchmark in the industry.

Thanks for your attention,
Ursula

Hi all,

finally I have a complete list of all emails sent out to translators since we started our service.
By this I am able to recheck cases of translator, saying that they never ever got any job offers (as different to those that got offer but were not able to pick it up).
I have several emails and names from the comments of cases to check, anyone that would like his/her case to be checked too - drop me an email.
Furthermore the new list I got will keep me busy in finding new ways to make the sending of email notification more satisfying. I will update you after my weekend.

Thanks also for all the nice remarks on the last post.
Best -
Ursula

Dear colleagues,

please note that with the experiences we made during the first month we amended the payment procedures in the following: