{"id":10507,"date":"2023-08-29T12:48:19","date_gmt":"2023-08-29T10:48:19","guid":{"rendered":"https:\/\/www.europatrad.eu\/general-vendor-guidelines\/"},"modified":"2026-04-10T16:28:23","modified_gmt":"2026-04-10T14:28:23","slug":"general-vendor-guidelines","status":"publish","type":"page","link":"https:\/\/www.europatrad.eu\/en\/general-vendor-guidelines\/","title":{"rendered":"General Vendor Guidelines"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

General Vendor Guidelines<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

TRANSLATION \u2013 PROOFREADING \u2013 FULL POST-EDITING \u2013 LIGHT POST-EDITING.<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

1. TRANSLATION<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
Requirements for translation work:<\/u><\/div><\/div>
<\/div><\/div>
  1. Commitment not to use machine translation engines.<\/span> <\/span><\/li>
  2. Observance of client and\/or project manager instructions, if any.<\/span> <\/span><\/li>
  3. No mistranslations, inaccuracies or omissions vs. the source text.<\/span> <\/span><\/li>
  4. Correct spelling, figures, names, typography, syntax and grammar.<\/span> <\/span><\/li>
  5. Appropriate and consistent terminology:\u2013 ensure that key terms, titles or roles\/positions are always translated in the same way in all documents pertaining to a project (unless otherwise required by the context).<\/em>\u2013 if a TM is provided, check whether the term has already been translated so that it can be reused (if you have doubts about the existing translation for a key term, please advise the project manager).<\/span><\/span> <\/span><\/em><\/li>
  6. Appropriate style:\u2013 make sure the style suits the context and purpose. Feel free to reword and\/or reformulate sentences according to the nature and purpose of the documents. For example, a marketing copy, a newsletter or a published article will probably need to be reworked more in detail.<\/span><\/span>.<\/em><\/li>
  7. Formatting (tags in Trados Studio, bold, italics, etc.).<\/span> <\/span><\/li>
  8. Questions and comments:– If you have questions, please forward them to the project manager as early as possible before delivery.<\/em>– If you have inserted comments in the Studio file, please inform the project manager upon delivery.<\/em><\/li><\/ol><\/div><\/div><\/div><\/div><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
    \n\t\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t

    2. PROOFREADING<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    At EuropaTrad, the overarching term \u201cproofreading<\/span>\u201d encompasses the concepts of revision, editing and proofreading<\/u><\/span>.<\/p>

    Proofreading<\/span> means checking the quality of a translation in every aspect (in substance and in form)<\/span> based on several criteria, including but not limited to the following:<\/p><\/div><\/div><\/div>

    1. Observance of client and\/or project manager instructions, if any.<\/span> <\/span><\/li>
    2. No mistranslations, inaccuracies or omissions vs. the source text.<\/span><\/li>
    3. Correct spelling,<\/span>figures, names, typography, syntax and grammar.<\/span><\/li>
    4. Appropriate and consistent terminology:<\/span>\u2013 ensure that key terms, titles or roles\/positions are always translated in the same way in all documents pertaining to a project (unless otherwise required by the context).<\/em>if a TM is provided, check whether the term has already been translated so that it can be reused (if you have doubts about the existing translation for a key term, please advise the project manager).<\/em><\/li>
    5. Appropriate style:\u2013 make sure the style suits the context and purpose. Feel free to reword and\/or reformulate sentences according to the nature and purpose of the documents. For example, a marketing copy, newsletter or published article will probably need to be more thoroughly reworked.<\/span><\/span><\/em> <\/span><\/li>
    6. Formatting (tags in Trados Studio, bold, italics, etc.).<\/span><\/li><\/ol>

      With a view to continuous improvement, upon delivery of the<\/span>proofed texts<\/span>, please rate the quality of the original translation<\/span>by filling in the rating grid below.<\/span><\/span><\/p><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t
      \n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tDownload the rating grid<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
      \n\t\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t

      \n3. FULL POST-EDITING<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      <\/span>Full<\/span><\/span> post-<\/span>e<\/span>ditin<\/span><\/span>g <\/span><\/span><\/span> means<\/span> <\/span>making all the necessary changes and modifications <\/u><\/span><\/span><\/span> <\/strong>to the<\/span> \n MT engine<\/span>raw output<\/span>provided<\/span><\/span>to make the finalised target text correct and appropriate in terms of meaning, terminology (including consistency) and style.\n <\/span><\/span><\/p>

      Requirements for full post-editing works:<\/u><\/p><\/div><\/div><\/div>

      1. Observance of client and\/or project manager instructions, if any.<\/span> <\/span><\/li>
      2. No mistranslations, inaccuracies or omissions vs. the source text.<\/span> <\/span><\/li>
      3. Correct spelling, figures, names, typography, syntax and grammar.<\/span> <\/span><\/li>
      4. Correct<\/span>and consistent<\/span> terminology:<\/span>\u2013 ensure that key terms, titles or roles\/positions are always translated in the same way in all documents pertaining to a project (unless otherwise required by the context).<\/em>if a TM is provided, check whether the term has already been translated so that it can be reused (if you have doubts about the existing translation for a key term, please advise the project manager).<\/em><\/li>
      5. Appropriate style:\u2013 make sure the style suits the context and purpose. Feel free to reword and\/or reformulate sentences according to the nature and purpose of the documents. For example, a marketing copy, newsletter or published article will probably need to be more thoroughly reworked.<\/span><\/span> <\/span><\/em><\/li>
      6. Formatting (tags in Trados Studio, bold, italics, etc.).<\/span> <\/span><\/li>
      7. Questions and\/or comments:– If you have questions, please forward them to the project manager as early as possible before delivery.<\/em>– If you have inserted comments in the Studio file, please inform the project manager upon delivery.<\/em><\/li><\/ol><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t

        \n4. LIGHT POST-EDITING\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        <\/span>Light<\/span><\/span> post-<\/span>e<\/span>ditin<\/span><\/span><\/strong>g \n \n <\/span><\/span><\/span> means<\/span> <\/span>making making only the relevant and absolutely necessary corrections and changes<\/u><\/span><\/span><\/span> on <\/span>MT engine<\/span>raw output<\/span> provided<\/span>. in order to<\/span><\/span> make<\/span><\/span>the finalised target text<\/span>understandable and fit for purpose<\/span>.<\/u><\/span><\/span><\/span><\/span><\/p>

        Requirements for light post-editing works:<\/u><\/p><\/div><\/div><\/div>

        1. Observance of client and\/or project manager instructions, if any.<\/span> <\/span><\/li>
        2. No mistranslations nor omissions vs. the source text.<\/span> <\/span><\/li>
        3. Correct spelling, grammar, figures and names.<\/span> <\/span><\/li>
        4. Acceptable and consistent terminology:<\/span> <\/span><\/span>\u2013 ensure that key terms, titles or roles\/positions are always translated in the same way in all documents pertaining to a project (unless otherwise required by the context).<\/em>if a TM is provided, check whether the term has already been translated so that it can be reused (if you have doubts about the existing translation for a key term, please advise the project manager).<\/em><\/li>
        5. Formatting (tags in Trados Studio, bold, italics, etc.).<\/span> <\/span><\/li>
        6. Questions and\/or comments:– If you have questions, please forward them to the project manager as early as possible before delivery.<\/em>– If you have inserted comments in the Studio file, please inform the project manager upon delivery.<\/em><\/li><\/ol><\/div><\/div><\/div><\/div>

          Aspects not to focus on in light post-editing jobs:<\/u><\/p>