Estimate Requirements

How to estimate translation costs

Language TranslationRequirements to generate a spec and estimate

Before our staff can generate a spec and an estimate for you, you first need to identify your localization requirements by following the below:

  1. Websites
  2. Marketing Collateral
  3. Miscellaneous documents
  4. Manuals
  5. Help
  6. Software/GUI

Disclaimer

Website

  1. Identify the countries and languages of interest. Keep in mind that many countries can share the same languages.
  2. Determine your budget. On average a web site will have 100 pages with about 150 words per page to translate. The cost of a typical web site is around $5,000 US per language. This includes translation, review by a second translator, formatting and quality assurance (QA). But actual costs will depend on the language, the number of words, the number of graphics and the number of pages to format and QA. Also, any additional requirements such as the translation of PDFs or other documents can add substantially to the costs.
  3. Identify the web pages that require translation
    1. Keep in mind that the more text needing translation the higher the costs will be, so you want to start with the minimum requirements like the top 1-3 levels of pages.
    2. Pages related to local events and jobs can be eliminated
    3. Pages that are better re-written for the local markets are to be avoided
    4. Decide if you want PDFs, or other documents linked to your web site, localized. You may want to start without them, since they tend to increase the costs.
    5. Decide if you want any intranet pages translated.
  4. Document your requirements and collect all source files needing translation and provide to us to generate a complete spec and estimate. This should include all HTM, ASP, JS, graphics, database, etc. We can offer you an ftp server link to upload the compressed files on.
  5. Indicate deadlines and desired release schedules.

Marketing Collateral

  1. Identify the countries and languages of interest. Keep in mind that many countries can share the same languages.
  2. Determine your budget. On average a single page of Marketing Collateral will have 400 words to translate and is published in InDesign or the like. The cost of a typical page is around $140 US per language. This includes translation, review by a second translator and professional typesetting. But actual costs will depend on the language, the number of words, the number of graphics and pages to format.
  3. Identify the pieces that require translation. These can include your datasheets, brochures, white papers, press releases, PowerPoint presentations, etc. Keep in mind that the more pages needing translation the higher the costs will be, so you may want to start with minimum requirements.
  4. Document your requirements and collect all source files needing translation and provide to us to generate a complete spec and estimate. The source files should include all InDesign, QuarkXPress, MS Publisher, PowerPoint, fonts, graphics and PDFs. If source files are not immediately available, PDFs will be acceptable for estimate only. Source will be needed before actual work is to start. We can offer you an ftp server link to upload the compressed files on.
  5. Indicate production deadlines and other schedules.

Miscellaneous documents

  1. Identify the countries and languages of interest. Keep in mind that many countries can share the same languages.
  2. Determine your budget. In general a single spaced page contains 250 words to translate and is published in MS Word or the like. The cost of a typical page is around $80 US per language. This includes translation, review by a second translator and basic formatting. But actual costs will depend on the language, the number of words, the number of graphics and the number of pages to format.
  3. Identify the pieces that require translation. They can include any business documents.
  4. Document your requirements and collect all source files needing translation and provide to us to generate a complete spec and estimate. The source files should be provided in MS Word or like formats. If source files are not immediately available, PDFs will be acceptable for estimate only. Source will be needed before actual work is to begin. We can offer you an ftp server link to upload the compressed files on.
  5. Indicate desired delivery schedules.

Manuals

  1. Identify the countries and languages of interest. Keep in mind that many countries can share the same languages.
  2. Identify the manuals that require translation. These can include any manuals desktop published in FrameMaker, PageMaker, QuarkXPress, InDesign, MS Publisher, MS Word, or the like.
  3. Determine your budget. You can do so by calculating the total word count in the manual and dividing by three to come up with a per language cost in US $. This includes translation, review by a second translator and professional formatting. But actual costs will depend on the language, the number of words, the number of graphics and the number of pages to format.
  4. Document your requirements and collect all source files needing translation and provide to us to generate a complete spec and estimate. The source files should be provided in their source formats. If source files are not immediately available, PDFs will be acceptable for estimate only. Source will be needed before actual work is to start. We can offer you an ftp server link to upload the compressed files on.
  5. Indicate printing deadlines and other schedules.

Help Files

  1. Identify the countries and languages of interest. Keep in mind that many countries can share the same languages.
  2. Identify the Helps that require translation. These can include any web based or document based help such as RTF, HLP, HTM, CHM, WebHelp, DivaHelp, Oracle Help, or the like.
  3. Determine your budget. You can do so by calculating the total word count in the help files and dividing by three to come up with a per language cost in US $. This includes translation, review by a second translator, professional formatting and QA. But actual costs will depend on the language, the number of words, the number of graphics and the number of pages to format.
  4. Document your requirements and collect all source files needing translation and provide to us to generate a complete spec and estimate. The source files should be provided in their source formats. If source files are not immediately available, compiled help like CHM files will be acceptable for estimate only. Source will be needed before actual work is to start. We can offer you an ftp server link to upload the compressed files on.
  5. Indicate release deadlines and other schedules.

Software Files/GUI

  1. Identify the countries and languages of interest. Keep in mind that many countries can share the same languages.
  2. Identify the software modules that require translation. These can include most ASCII or binary based formats such as RC, String Tables, Message Files, DAT, DLL, EXE, OCX, ASP, XML, PHP, Java, XRES, RES, MDB…
  3. Determine your budget. You can do so by calculating the total word count to translate in the software files and dividing by two to come up with a per language cost in US $. This includes translation, review by a second translator, engineering and QA. But actual costs will depend on the language, the number of words, the number of graphics, the number of files and the number of dialogs or forms to resize.
  4. Identify any character size restrictions or other requirements for build or Quality Assurance. Build and post compilation QA is quoted separately and will depend largely on your test plans.
  5. Document your requirements and collect all source files needing translation and provide to us to generate a complete spec and estimate. The source files should be provided in their source formats. If source files are not immediately available, binary files such as DLL or EXE may be acceptable. Source will be needed before actual work is to start. We can offer you an ftp server link to upload the compressed files on.
  6. Indicate release deadlines and other schedules.

Disclaimer: The budgetary figures provided above are first order approximations and can vary substantially. It is always recommended that you provide the source files and the requirements to get an accurate cost estimate. GlobalVision guarantees its estimate after receiving final source files.

Please Share!   Facebooktwittergoogle_plusredditpinterestlinkedinmail