L10N Estimator

FrameMaker Localization

Comprehensive guide for localizing Adobe FrameMaker documents

Metrics

Revision Rounds:

2 revision rounds

File Preparation:

  • • Pages: 100 pages/hour (DTP Prep)

Breakdown:

  • Desktop Publishing (pages/hour): Latin = 20, Asian = 15, BIDI = 10
  • Desktop Publishing: Graphics (Editable) = 10 graphics/hour, Graphics (Uneditable) = 5 graphics/hour
  • Revision 1 (pages/hour): Latin = 40, Asian = 30, BIDI = 20
  • Revision 2 (pages/hour): Latin = 80, Asian = 60, BIDI = 40
  • Word Count: 350 words per page, 30 words per graphic

Source Material

Required files and assets from the client:

  • FrameMaker source files: .FM, .MIF, or .BOOK files (preferred format for best localization results)
  • Editable graphics: Source files for all graphics (.PSD, .AI, .SVG, .EPS) that contain text or need localization
  • Fonts: All fonts used in the document, including custom or licensed fonts, or links to font sources
  • Reference materials: Style guides, glossaries, terminology databases, and any previous translations for consistency
  • Graphics inventory: List of graphics that need localization vs. those that are universal
  • Screenshots: If screenshots need replacement, provide source application access or replacement images
  • PDF reference: Final output PDF for layout reference and quality assurance

Best Practices

  • Use structured documents: FrameMaker structured documents with EDD (Element Definition Document) provide better control over formatting and ensure consistency across languages
  • Extract text for translation: Export translatable content to XLIFF or other translation formats to maintain formatting and context
  • Handle graphics separately: Extract text from graphics and translate separately, then update source graphics or recreate localized versions
  • Manage paragraph styles: Use paragraph and character styles consistently to ensure proper formatting in target languages, especially for text expansion
  • Test text expansion: Account for text expansion (typically 20-30% for European languages, 50%+ for Asian languages) by testing layouts early
  • Preserve conditional text: Maintain conditional text markers and ensure they work correctly in localized versions
  • Handle cross-references: Verify that cross-references, hyperlinks, and bookmarks update correctly after translation
  • Maintain table formatting: Tables may need adjustment for text expansion; use flexible table formats when possible
  • Check special characters: Ensure proper encoding and font support for special characters, diacritics, and symbols in target languages

Things to Consider

  • Text expansion: FrameMaker documents can expand significantly in some languages (German, Finnish, Russian), requiring layout adjustments and potentially more pages
  • BIDI languages: Right-to-left languages (Arabic, Hebrew) require special handling of text direction, alignment, and reading order
  • Font availability: Ensure target language fonts are available and properly licensed; some languages require specific font families
  • Graphics localization: Graphics with embedded text require separate localization workflow; uneditable graphics may need recreation
  • Master pages: Headers, footers, and page numbering may need adjustment for different languages and text lengths
  • Index generation: If the document includes an index, it must be regenerated after translation with proper sorting for the target language
  • Table of contents: TOC entries may change length and require formatting adjustments
  • Version compatibility: Ensure FrameMaker version compatibility between source and target systems
  • Conditional text: Verify that conditional text settings work correctly for different language versions

Workflow

  1. File Preparation (DTP Prep): Analyze source files, extract translatable content, identify graphics requiring localization, and prepare files for translation (1 hour per 100 pages)
  2. Content Extraction: Export text content to translation format (XLIFF, RTF, or XML) while preserving formatting and structure
  3. Translation: Translate content using CAT tools, maintaining terminology consistency and following style guides
  4. Graphics Localization: Extract text from graphics, translate, and update source graphics or create localized versions (1 hour per 10 editable graphics, 1 hour per 5 uneditable graphics)
  5. Desktop Publishing (Round 1): Import translated content back into FrameMaker, apply formatting, adjust layouts for text expansion, and update graphics (20 pages/hour for Latin, 15 for Asian, 10 for BIDI)
  6. Screenshot Replacement: Replace screenshots with localized versions if required
  7. Quality Assurance: Review layout, formatting, text flow, and ensure all elements are properly localized
  8. Revision 1: Implement client feedback and corrections (40 pages/hour for Latin, 30 for Asian, 20 for BIDI)
  9. Revision 2: Final corrections and refinements (80 pages/hour for Latin, 60 for Asian, 40 for BIDI)
  10. Final Output: Generate PDF or FrameMaker output files, verify all cross-references, TOC, and index are correct