I should have increased my quote. I can only blame myself I didn’t…




  • Greater than 2 minutes, my friend!

    Before you read the story, please accept my apologies for a missing screenshots. My customer does not want me to show his job in any way.

    I did a small job (3000 words) and as I knew the customer, I just made a quote using a word count tool on my phone. Turned out the job was way more difficult than I thought it would be. I spent more than 2 days on this small job…

    As I’m co-owner of a company that created a tool to make a source analysis, I feel very bad about this. So I checked if our tool (Fair Trade Translation) would have seen this job was going to be trouble.

    Our translation tool only supports English into FIGSP for now, but I could have used the source text analysis as my source was English anyway. This is what Fair Trade Translation saw when it was too late:

    DomainIdentification

    It should have been “Automotive”. Our system not being able to tell what the text is about, should have been a first warning.

    EstimatedTranslationDifficulty

    I know this estimate is not always right, because it is based on various source text properties and on machine translation performance (we compare how machine translation engines perform on the text), and that doesn’t tell something about my own skills as a translator. But when our tool says it will probably be difficult … I should have taken a closer look.

    SentenceLength

    Many long sentences. Maybe the writer was not a professional writer. There were indeed a lot of long sentences with complex subclauses.

    I also checked the Suggested Terms (the list I cannot show you – once more I’m sorry). That is a list of terms extracted from the source but the terms are also translated into context. As Dutch translation is not yet supported, I hardly ever use this feature myself. But it is good to take a look at the list anyway: about one third of the extracted terms was not really what I would call a term – so be it – but another third were terms I did not know at all… Half of those were not in any free online dictionary — Good to see that Linguee, a service we link the extracted terms to, did find at least some partial hits for some terms.

    The Suggested Terms list could have been the main reason for me not to accept the job, or to the raise my quote. A pitty I didn’t check it before submitting it.

    TextReUse

    Last but not least: the text-reuse… Almost no reuse, even not on subsegment level. Every sentence was indeed hard work…

    The Fair Trade Translation analysis was right, and it probably won’t be right all the time. After all, it is also based on NLP technology — we all know translators still out-rank machines by far. But if the tool indicates, in one or more reports, that a job isn’t low hanging fruit, a more careful approach may be very rewarding.

    Another lesson learned…

    (Also read: Back to basics – how does it feel to translate naked?)

    Gert Van Assche

    About Gert Van Assche

    Skeptical technology lover, testing a lot of translation tools. Occasionally I translate and develop software myself as well. I help LSPs through Datamundi, translators through Fair Trade Translation.

    7 thoughts on “I should have increased my quote.

      1. Thanks Silvia. It was something our translators requested. We had our doubts, but turns out it is something they use almost as much as our MT qualifier. Glad we made it.

    1. Hi Gert!
      Nice approach, will follow up.
      BTW: The link to “Back to Basics” simply redirects here … too bad as it is certainly worth reading.

    2. Thank you so much for sharing, Gert! Long time no see! Glad to have you back on The Open Mic :) How are things with FTT. Is it growing steadily? Are you developing any new features? Any plans to add more languages? :)

      1. I’ve been busy lately indeed. FTT is still growing : more features, more users, more questions and feature requests… A lot of work. Still only 5 language pairs for translation, but we’re considering to add some more this year. We’ll see. It’s an adventure.

    3. Good article, Gert! The tool seems to do a good job parsing the difficulty of any given text. Thanks for sharing your experience — not all texts are created equal and therefore should be quoted differently. I will definitely check out the tool you mentioned.

    Leave a Reply