* Automatic ("rough" in kbabel terms) translation. Pure machine translation is a joke. All machine-made translations must be verified by human (and let it be a translator rather than a user).

* Automatic ("rough" in kbabel terms) translation. Pure machine translation is a joke. All machine-made translations must be verified by human (and let it be a translator rather than a user).

−

Why? because sometimes one english string may have two or more different translations depending on the context.

+

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, when, if the message is already translated somewhere else, it suggests the translations (several, not one!) and displays them in the helper window. translator then may 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 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).

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 the smarter way :). After or during the summer.

Character selection tool integration (kdelibs rule); sort by the frequency

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

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?)

Automatic comparisons and statistics of POT and PO files for a quick overview which and how many files are translated (or not) and which files may be obsolete + [Kross (project) action] that merges translations with updated template

PO File Header change [Kross action (+triggered on saving)]

Printing of selected messages (eg fuzzy ) [Kross action]

KBabel features NOT to be implemented

Automatic ("rough" in kbabel terms) translation. Pure machine translation is a joke. All machine-made translations must be verified by human (and let it be a translator rather than a user).

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).