G11NToolKit Roadmap

Roadmap for Future Development of G11NToolKit Function.

Current Release

G11NToolKit 1.6.0 - 2005/08/22

G11NToolKit 1.7.0

  • Target delivery not scheduled yet.
  • Estimate 3-4 months elapsed time to complete with 1.5-2.0 man months of effort.
  • See process diagram for graphic display of functions that may be implemented in this release. This is the direction we are headed, not necessarily the end goal.
  • TMX format export of XLIFF Str file can be used for reference purposes when sending out work for translation.
  • HTML Parser integrated with G11NToolKit Token, StrFile, and TokFile classes. HTML Parser needs to use these classes to be consistent with the rest of the tools in format of output and other uses of the classes.
  • JavaScript Tokenizer - Needs to be fully tested in conjunction with HTML Parser and adjusted as needed. Needed to create an XLIFF file if possible. The JavaScript extractor is currently using the logic from G11NToolKit 0.0.1 since there are some major issues with the HTML Parser's handling of these files.
  • Make a permanent fix for handling empty strings in Detok.
  • Continue to update documentation for new features and clarification of existing features.

Return to:   Top of page

G11NToolKit 1.8.0

  • Target delivery not scheduled yet.
  • Estimate 6-7 months elapsed time to complete with 3.0-3.5 man months of effort.
  • See process diagram for graphic display of functions that may be implemented in this release. This is the direction we are headed, not necessarily the end goal.
  • XLIFF database to contain the extracted strings with their translations.
  • TMX ex/import for XLIFF database to be used to deliver files for use as TM to any translator who needs it.
  • XLIFF editor changes to support database query/update. This will only allow matching at 100% match in string and/or context. The editor could be used by the translator to add translation to XLIFF Str file. Optionally, the XLIFF Str file could be split into xlation yes and no files so that xlation yes file could be sent out for translation. Translators would be free to use whatever translation tool they want to do the work.
  • L10NProcess Ant files changes will be needed to support the new and changed functions.
  • Continue to update documentation for new features and clarification of existing features.

Return to:   Top of page

G11NToolKit 1.9.0

  • Target delivery not scheduled yet.
  • Estimate of elapsed time and effort are not available.
  • See process diagram for graphic display of functions that may be implemented in this release. This is the direction we are headed, not necessarily the end goal.
  • Fuzzy match support for XLIFF editor.
  • Continue to update documentation for new features and clarification of existing features.

Return to:   Top of page

by Bill Rich