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: (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"). ACOLAD uses 2-letter language codes from ISO 639-1 for identification of the languages.
Appendix 1 - Linguistic Quality check (LQC)
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: (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"). ACOLAD uses 2-letter language codes from ISO 639-1 for identification of the languages. 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 a...
Naming Convention. Proposals shall be limited to the following attachments identified by the Naming Convention and page limitations below. • System for Award Management (XXX) Certification – Attachment J.2 • Pre-Award Accounting System Questionnaire – Attachment J.3 • Contractor Information Spreadsheet - Attachment J.4 • Technical Proposal and Supporting Documentation – See Section 5.0 below for details System for Award Management (XXX) Certifications (Attachment J.2) Company_Name_CAGE_ SAM_Certs N/A Pre-Award Accounting System Questionnaire (Attachment J.3) Company_Name_CAGE_Acctg_Sys_Questionnaire N/A Contractor Information (Attachment X.4) Company_Name_CAGE_Contractor_Info 1 Technical Proposal & Supporting Documentation of Experience (see Section 5.0 below) Company_Name_CAGE_ Cover_Letter 1 Company_Name_CAGE_Signed_SF33 1 Company_Name_CAGE_Technical_Proposal 5 Company_Name_CAGE_Experience_ Supporting_Docs N/A Company_Name_CAGE_Subcontracting_Plan(if applicable) N/A Company_Name_CAGE_Non-Affiliate Certificate (ifapplicable) 1 *The Government will not consider any information presented beyond the last whole word within the PAGE LIMIT.
Naming Convention. The final ethics agreement or understanding shall be named using the employee’s name and initial(s), document type (i.e. Ethics Agreement or Ethics Understanding), and date the agreement was signed by the employee. Use hyphens or underscore between words. Do not include blank spaces in the file name.
Naming Convention. The interface source file’s naming convention is comprised of several nodes. An example of an interface source file name as well as an explanation of each of the naming convention nodes are described below. ECAPS_FR_TIMEI_AESS_20051101 ■ DOC_DEPT_CD – The second node is the two or three byte eCAPS department id (e.g. SH - Sheriff, FR – Fire, PB - Probation, etc…) ■ DOC_CD – The third node is the four or five byte eCAPS document code (TIMEI) ■ LEGACY78 – The fourth node is a maximum of eight bytes for the department legacy system identifier (e.g. CWTAPPS, CWPAY, AESS, etc…) or external scheduling system. ■ YYYYMMDD – The fifth node is the appropriately formatted date the interface source file is generated (20051101). This date should change depending upon the frequency of the interface. It is preferred that the date be coded as the system date. In the case where multiple files are sent on the same day, the file name should be unique.
Naming Convention. ROADWAY aa = Plan sheet type (will be more than two digits in some instances) ## = Number identifying the number of drawings of the same type, i.e., 01, 02, 03, ... (Minimum of two digits are necessary.) FILE FOLDER STRUCTURE CSJ _Hwy Subfolders This folder contains the .gpk file, all input files, output files and other files generated using the program.
Naming Convention. If the fiducial tags code a number, the use of the same tag number as the marker ID number is strongly recommended.
Naming Convention. Please assist us in maintaining our standards and ensure that any listing of our hotel’s name says “Viceroy Anguilla Resort & Residences” without exception.
Naming Convention. The Agreement duration agreed upon by the Parties is 5 years. The City and Owner agree to extend this agreement for an additional 5-year period upon mutual review and revision to this agreement. Nutrient Management Plans are not eligible for this Agreement. The NRCS practice names, practice code numbers, and practice acreages for the 5-year agreement are shown in Table 1 below. The Owner will be allowed to adjust which fields are in the cover crop program as necessary due to weather and other environmental conditions, given P credit reduction modeled in Snap Plus remains within 10% of the specified amount in the WQT plan, 210 P credits, and all fields remain within the watershed. Existing buffer strips removed for crop rotation shall be done only as approved by County and should be done in conjunction with cover crop rotation to comply with the requirement to be within 10% of the specified amount in the WQT plan. When buffer strips are reestablished in areas used for a rotational crop, new buffer strip should be treated as a new installation and reimbursed by the City per this agreement. Table 1 – Management Measure Practice Summary *This is a list of potential fields for the cover crop program for the duration of the agreement. It is not intended that cover crop will be planted on every field listed every year of the agreement. Cover crops: Cover crops shall be installed as approved by the County based on the seeding rate and dates recommended in Table 1. of the NRCS Wisconsin 340 Cover Crop Guidance Document provided in Attachment 1. If other installation methods are used, seeding rate and dates should be adjusted and approved by the County. Methods for seeding cover crops shall be approved by the County and shall include but are not limited to: • Broadcast • Drill • Aerial
Naming Convention. Under the 2023 QI Agreement, each QDD must separately qualify and be approved for QDD status. In applying for QDD status, the applicant must follow the naming convention described in section 2.63 of the 2023 QI Agreement on its application and, if approved as a QDD, on any other tax forms or other materials for which the QDD must be identified. This is the same naming convention that was previously described in an FAQ #13 – Certifications and Periodic Reviews for the 2017 QI Agreement.
