KAider is a computer-aided translation system that focuses on productivity and performance. Translator does only creative work (of delivering message in his/her mother language in laconic and easy to understand form). KAider implies parapgraph-by-paragrah translation approach (when translating documentation) and message-by-message approach (when translating GUI). See KAider/Introduction
- syntax highlighting
- spellcheck (problems with dividing filter:doesnt check the last word; sonnet::configwidget crashes kaider)
- search-n-replace, ignoring accel marks
- formats .po file output better so less diff is generated by scripty
- small features like quick tag insert, placing text cursor right after the tag in the beginning (e.g. '<qt>|foobar</qt>' where "|" is a cursor), entry bookmarks
- viewer of the difference between current msgid and previous one (i.e. msgid translation of which current msgstr really is -- for fuzzies generated with --previous gettext option)
- merge mode for editors (QA) or when several translators work on the same file screenshot
- basic projectmanager functionality screenshot
- Translation Memory (threaded) with shortcuts for inserting suggestions into current 'msgstr', scores are computed based on common/total length ratio, removed+added length, and count of removed+added parts screenshot
- for difference representation in all places word-by-word algorithm is used (based on the Longest Common Sequence o(n*n) algorithm and my own experience)
- glossary with basic tbx format support. KAider displays relevant entries on-the-fly and provides shortcuts to insert them. also, you can add new glossary terms via context menu of the glossary screenshot
- webquery view, flexible thanks to kross
After you set kde env up (compiling kdelibs is enough):
cd trunk svn up playground/devtools/kaider su kde-devel mkdir playground/devtools/kaider/build cd playground/devtools/kaider/build cmakekde ..
as a root, run sshd and then from the usual shell:
ssh -XC [email protected] kaider
- [basic framework DONE] project management+scripting API -- 2 weeks
- [DONE] context glossary -- 0.5-1 week
- [DONE] translation DB (QtSql) -- 2 weeks
- [DONE] mode for merging translations for editors (QA) -- 1 week
- [DONE] sipping on google translate for live glossary (kross) - 2 weeks
- the remaining time is for perfection/polishing/small improvements and xliff+qt-linguist support (see KBabel features to be implemented)
What i'm doing these days
- search/replace in multiple files
- impovements on ProjectView (dbus, etc), Glossary
- WebQuery for twin languages (like ukrainian and russian)
- Majority of actions must be accessible via keyboard (because it is faster to press a shotcut than to be frustrated with a mouse)
- Do automatization _everywhere_ it possible
- Focus on quality. This is open source -- so source code is available (for change)
- project-wise and program-wise: webquery scripts, glossaries, TMs
- Glossary editing usability
- ... (more on papers around my table :)
- Automatic Glossary building
- Tighten SVN support: svn diff-like feature
- Research on dividing into sentences rules (e.g. srx)
- Automate submitting translation suggestions to translate.google.com [Kross action]
- back-checking, to see whether a term/string in the target language has been used as translation for different things, not just that one source has the same translation everywhere.
- [Kross (project) action] that merges translations with updated template
Not for KDE:
- Be complete computer-aided translation system by providing e.g. actions to import+export openoffice, txt and documents of other formats by calling appropriate scripts/commands. Define for that general kross actions interface.
- Make nice windoze package for the windowzerz
KBabel features to be implemented
...in a smarter way :). After or during the summer.
- persistent bookmarks for messages in a file saved in the project
- extended marking of .po and .pot files (e.g. translator that currently works on the file and cince when) saved in the project
- Search/Replace functions in multiple files at once.
- Spellchecking of multiple files at once.
- Opening source code by references in message comments [Kross action]
- A plugin framework for validation tools for consistency checks [Kross action triggered on saving]
- Sending the file using email [Kross (project) action]
- Automatic syntax check with msgfmt when saving and, if an error occured, easy navigation to messages, which contain errors. == Syntax check (msgfmt --statistics) for existing files to control if the translated files will compile and, accordingly, work when distributed [Kross (project) action]
- CVS and SVN support [Kross project action] (is 'svn ci' so hard?)
- PO File Header change [Kross action (+triggered on saving)]
- Printing of selected messages (eg fuzzy ) [Kross action]
- msgid-diff-msgstr from  (features for all other commands are already implemented, if you haven't noticed this)
KBabel features NOT to be implemented
- Character selection tool integration, sort by the frequency
Why? Better improve system-wide charselect tool, OR... modify your xorg keyboard layout!
- Automatic ("rough" in kbabel terms) translation.
Why? because sometimes one English string may have two or more different translations depending on the context.
What I'm going to do is implement _interactive_ (or message-by-message) rough translation. If the message is already translated somewhere else, it suggests the translations (several, not one!) and displays them in the helper window. Translator may then choose one of the translation suggestions by pressing ctrl+1, ctrl+2, .. or ctrl+9, which will immediately insert it into msgstr (replacing the old translation if it exists).
What old rough translation didn't provide is the ability to choose.
UPDATE: ok, i'll probably allow translator to autopopulate catalog with:
- one-choice suggestions (e.g. if there are only one 100% suggestion), optionally mark fuzzy
- the most recent suggestions for the cases of several 100% items, mark fuzzy
- Create project, saving *.ktp file to l10n-kde4/<LangCode>
- Populate Glossary via GlossaryView context menu (.tbx file will be created automatically for you on the first entry addition).
- Populate Translation Memory by dropping .po files onto TM View