Common use of Naming Convention Clause in Contracts

Naming Convention. ‌ It is not allowed to change the name of the translated file, except for adding the ISO 639-1 target language code according to the following format: [ORIGINAL NAME]_[TARGET LANGUAGE CODE].[FORMAT] (For example: “title_EN.doc” for a Word document translated into English). If revision or review is performed, “rev” (for revision) or “rwd” (for review) is added between the language code and the format (“title_ENrev.doc or “title_ENrwd.doc”). AMPLEXOR uses 2-letter language codes from ISO 639-1 for identification of the languages. Annex 1 – Linguistic Quality check (LQC)‌ Specification Description File can be opened No corruptions, garbled characters due to tag integrity, etc. are found No unintentional blank pages are left Correct target language Check for correct language locale File names File names are not altered and are consistent with client instructions Full set of files/batch All files/batches are accounted for; translated files are available in the Output Package/Delivery folder Client and project-specific rules and instructions Verify that STA, style guide, glossaries, references and instructions have been followed Open queries and answers Make sure all questions are answered and answers implemented in the translation Comments/remarks added to the translation Any necessary remarks are appropriate both in terms of format as well as wording Process full tag check Used tag checker in the CAT tool Process spellcheck Used spellcheck in CAT tool or Windows spellchecker Process termcheck Used termverifier integrated in the CAT tool Unedited fuzzy matches Used QA checker in CAT tool Consistency checks Used QA checker in CAT tool General layout Clean files Verify that no tag issues, etc. remain in target file; Check for text irregularities Make sure no words are cut-off Check for suspicious capitalizations in mid-sentence Punctuation Follow the source punctuation whenever is appropriate and does not interfere with target language rules Ensure there are no missing or additional punctuation marks Check that bulleted/numbered lists follow source (or are consistent with language requirements) Spaces Verify that there are no double spaces or missing spaces between words, after trademark symbols, etc. Verify that space between number and unit are consistent based on language rules Check consistency in spaces before degree symbols based on language rules Hyphenation Check for cut-off words, suspicious line breaks, etc. and verify that hyphenation was enabled and hyphenation was correctly applied Table format Ensure table, row and column dimensions are adapted to source and target language requirements as applicable in file format Check in target language whether row span was kept in same format as source which could then lead to words cut off or other issues Symbols (#, &, %, <, >) Are there the same symbols in the source text? Are they handled consistently in the languages? Pay particular attention to symbols when used in software strings. These may have different role/meaning than usual Parentheses, brackets Check for complete set (opening/closing, consistent format) Quotation marks Verify that language-specific quotation marks are used consistently within language. Display Images Ensure graphics, callouts, screenshots etc. are correctly displayed Are they localized correctly when this is the client requirement? Check as applicable in file format Make sure text linked to images matches Formatting Verify that source and target are consistent (font in italics, bold, underline, indentation, etc.) Capitalization Examples may include titles, headers, words within sentences (e.g. SMART) Check that they are handled according to language requirements Table of Content (TOC) Index Entries and page numbers match source Entries match corresponding headers Hyperlinks work properly and link to correct language/location (if applicable and can be checked in final format) Index is sorted properly and in alphabetical order Please perform spot checks Page numbers Make sure page numbers and page counts are consecutive and accurate Source text not left Check for any elements left in source language Ensure all content is included in target language(s)

Appears in 1 contract

Sources: General Terms and Conditions

Naming Convention. ‌ It is not allowed to change the name of the translated file, except for adding the ISO 639-1 target language code according to the following format: [ORIGINAL NAME]_[TARGET LANGUAGE CODE].[FORMAT] (For example: “"title_EN.doc” " for a Word document translated into English). If revision or review is performed, “"rev” " (for revision) or “"rwd” " (for review) is added between the language code and the format (“"title_ENrev.doc or “"title_ENrwd.doc”"). AMPLEXOR ACOLAD uses 2-letter language codes from ISO 639-1 for identification of the languages. Annex 1 – Linguistic Quality check (LQC)‌ Specification Description Fundamental checks File can be opened No corruptions, garbled characters due to tag integrity, etc. are found No unintentional blank pages are left Correct target language Check for correct language locale File names File names are not altered and are consistent with client instructions Full set of files/batch All files/batches are accounted for; translated files are available in the Output Package/Delivery folder Client and project-specific rules and instructions Verify that STA, style guide, glossaries, references and instructions have been followed Open queries and answers Make sure all questions are answered and answers implemented in the translation Comments/remarks added to the translation Any necessary remarks are appropriate both in terms of format as well as wording Automated process completed Auto QA Process full tag check Used tag checker in the CAT tool Process spellcheck Used spellcheck in CAT tool or Windows spellchecker Process termcheck Used termverifier integrated in the CAT tool Unedited fuzzy matches Used QA checker in CAT tool Consistency checks Used QA checker in CAT tool General layout Clean files Verify that no tag issues, etc. remain in target file; Check for text irregularities Make sure no words are cut-off Check for suspicious capitalizations in mid-sentence Punctuation Follow the source punctuation whenever is appropriate and does not interfere with target language rules Ensure there are no missing or additional punctuation marks Check that bulleted/numbered lists follow source (or are consistent with language requirements) Spaces Verify that there are no double spaces or missing spaces between words, after trademark symbols, etc. Verify that space between number and unit are consistent based on language rules Check consistency in spaces before degree symbols based on language rules Hyphenation Check for cut-off words, suspicious line breaks, etc. and verify that hyphenation was enabled and hyphenation was correctly applied Table format Ensure table, row and column dimensions are adapted to source and target language requirements as applicable in file format Check in target language whether row span was kept in same format as source which could then lead to words cut off or other issues Symbols (#, &, %, <, >) Are there the same symbols in the source text? Are they handled consistently in the languages? Pay particular attention to symbols when used in software strings. These may have different role/meaning than usual Parentheses, brackets Check for complete set (opening/closing, consistent format) Quotation marks Verify that language-specific quotation marks are used consistently within language. Display Images Ensure graphics, callouts, screenshots etc. are correctly displayed Are they localized correctly when this is the client requirement? Check as applicable in file format Make sure text linked to images matches Formatting Verify that source and target are consistent (font in italics, bold, underline, indentation, etc.) Capitalization Examples may include titles, headers, words within sentences (e.g. SMART) Check that they are handled according to language requirements Table of Content (TOC) Index Entries and page numbers match source Entries match corresponding headers Hyperlinks work properly and link to correct language/location (if applicable and can be checked in final format) Index is sorted properly and in alphabetical order Please perform spot checks Page numbers Make sure page numbers and page counts are consecutive and accurate Source text not left Check for any elements left in source language Ensure all content is included in target language(s)

Appears in 1 contract

Sources: General Terms and Conditions for Linguistic Services Provision