1. Okapi Framework Avatar Okapi Framework
  2. Okapi and localization
  3. Okapi

Wiki

Clone wiki

Okapi / Roadmap

View History
  • HTML: basic parser mid-Sep
  • Segmenter: mid-sep (for simple languages & CJK)
  • Alignment (basic with ID): end-sep
  • WB + Okapi-TKit? (maybe PO-Tkit): TKit mid-sep

Roadmap (more un-ordered parts for now)

Filters

  • Filters library (The components that provide read and write access to the translatable content of different types of source material)
    • Filter API
    • Segment/Translation-Unit API and implementation
    • Item provider API (the abstracted input model that feeds any action/utility)
    • Filter access mechanism (gather plugin/updater info, instantiate filter objects, etc.)
    • Filter Implementation for Properties
    • Filter Implementation for JSON
    • Filter Implementation for XML (using ITS)
    • Filter Implementation for HTML
    • Filter Implementation for Regex-based data
    • Filter Implementation for OpenDocument (? or one of the XML variants)
    • Filter Implementation for wiki pages (?)
    • Filter Implementation for database
    • Filter Implementation for tables (CSV, tab-delimited files, etc. maybe a variant of the database filter?)
    • Filter Implementation for Windows RC
    • Filter Implementation for .NET ResX (This will lead to implementing some kind of bridge to .NET-specific component)
    • Filter Implementation for database

Segmentation

  • Segmentation Engine
    • Segmenter API and implementation
    • SRX support
  • Segmentation Rules Editor

Project Manager

  • Project Manager Engine (The server-side engine that takes care of storing project data and carries out the various workflow actions on them (manage updates, create translation packes, etc.)
  • Project Manager client (The client that interact with the Project Manager Engine)

Translation Packages

  • Translation package library (The component that generates translation packages)
    • The package writer and reader API
    • Package access component (gather plugin/updater info, instantiate package writer, etc.)
  • Translation Package (The components carry a set of data to localize from one step to another. Carries also the information to plug addin to the Translation Editor through an extensions mechanism).
  • Translation package creator for OmegaT (implements package writer and reader API for OmegaT projects)
  • Translation package creator for TTX (implements package writer and reader API for TagEditor projects)

Translation Editor

  • Translation Editor (The client that opens translation packages generated by the project manager, query translation resources, and use various extension (editors, QA, etc.) to produce a translated/edited package.

TM Server

  • TM Server (The server-side engine that store TM data and provide query access to them.)
  • TM Connector to the TM Server (Implements the TM query/update API for the TM Server)

Translation Resource Access

  • Translation Resource query and update engine (The components that allow query of TM, Termbases, and MT engines, in a comprehensive manner, as well as the updates of the data when needed).
    • TM query and update API
    • MT query and update API
    • Terminology query and update API
  • TM Connector for Trados (implements the TM query/update API for Trados TMs)
  • MT Connector for Google translate (Implements the MT quey/update API for Google translate )
  • TM Connector for TinyTM (?needed? Implements TM query/update API for TinyTM server http://tinytm.sourceforge.net/)
  • TM Connector for myMemory (?needed? Implements TM query/update API for myMemory server http://mymemory.translated.net/doc/)
  • Translation Memory Editor

Confgurable Workflow Engine

  • Many open source alternatives. Top contender is JBOSS jBPM. Alfresco uses this engine for it's document workflows. Has a Eclipse-based workflow editor.

Updated