Shaforostoff (Talk | contribs) (→Current state) |
Shaforostoff (Talk | contribs) (→Ideas) |
||
| Line 44: | Line 44: | ||
Not for KDE: | 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. | * 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 | + | * Make nice windoze package for the windowzerz |
| + | |||
| + | ==KBabel features to be implemented== | ||
| + | ...in the smarter way :). After or during the summer. | ||
| + | * Showing source code by references in message comments | ||
| + | * Character selection tool integration (kdelibs rule) | ||
| + | * Sending the file using email (kdepimlibs rule) | ||
| + | * persistent bookmarks for messages in a file | ||
| + | * A plugin framework for validation tools for consistency checks (again kross) | ||
| + | * Automatic syntax check with msgfmt when saving and if an error occured easy navigation to messages, which contain errors | ||
| + | * Integrated basic CVS and SVN support | ||
| + | * extended marking of .po and .pot files (e.g. translator that currently works on the file) | ||
| + | * 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 | ||
| + | * Syntax check (msgfmt --statistics) for existing files to control if the translated files will compile and, accordingly, work when distributed | ||
| + | * Search/Replace functions in multiple files at once. | ||
| + | * Spellchecking of multiple files at once. | ||
==Setup== | ==Setup== | ||
Contents |
Already has:
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 kde-devel@localhost kaider
Further work:
Not for KDE:
...in the smarter way :). After or during the summer.
This is how a TBX glossary looks like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE martif PUBLIC "ISO 12200:1999A//DTD MARTIF core (DXFcdV04)//EN" "TBXcdv04.dtd">
<martif type="TBX" xml:lang="en">
<martifHeader>
<fileDesc>
<titleStmt>
<title>KDE Russian Team Glossary</title>
</titleStmt>
</fileDesc>
</martifHeader>
<text>
<body>
<termEntry id="1">
<descrip type="subjectField">Security</descrip>
<descrip type="relatedConcept">authorization</descrip>
<langSet xml:lang="en">
<ntig>
<termGrp>
<term>authentication</term>
<termNote type="partOfSpeech">noun</termNote>
</termGrp>
<descrip type="context">.</descrip>
</ntig>
</langSet>
<langSet xml:lang="ru">
<ntig>
<termGrp>
<term>идентификация</term>
<termNote type="partOfSpeech">сущ.</termNote>
</termGrp>
</ntig>
</langSet>
<langSet xml:lang="ru">
<ntig>
<termGrp>
<term>подтверждение подлинности</term>
<termNote type="partOfSpeech">сущ.</termNote>
</termGrp>
</ntig>
</langSet>
</termEntry>
<termEntry id="2">
<descrip type="subjectField">Security</descrip>
<descrip type="relatedConcept">authentication</descrip>
<langSet xml:lang="en">
<ntig>
<termGrp>
<term>authorization</term>
<termNote type="partOfSpeech">noun</termNote>
</termGrp>
<descrip type="context"></descrip>
</ntig>
</langSet>
<langSet xml:lang="ru">
<ntig>
<termGrp>
<term>определение прав</term>
<termNote type="partOfSpeech">сущ.</termNote>
</termGrp>
</ntig>
</langSet>
</termEntry>
</body>
</text>
</martif>