Translate Toolkit & Pootle

Tools to help you make your software local

User Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

pootleoffline [2006/07/12 06:32]
dwaynebailey2 Reword
pootleoffline [2006/07/12 08:06] (current)
dwaynebailey2 Revised
Line 14: Line 14:
   * Existing Pootle programmers might be more available to help people get up to speed.   * Existing Pootle programmers might be more available to help people get up to speed.
   * We don't need to manage another project (test, package, release, etc.)   * We don't need to manage another project (test, package, release, etc.)
-  * Bugs ony need to be fixed in one place.+  * Bugs ony need to be fixed in one place.
   * No need to somehow get our storage classes to work with another editor, as we already make it work in Pootle.   * No need to somehow get our storage classes to work with another editor, as we already make it work in Pootle.
   * We don't need to keep track of which editor supports which features, etc.   * We don't need to keep track of which editor supports which features, etc.
-  * We are as crossplatform as HTML and HTTP is.+  * We are as crossplatform as HTMLHTTP and Python are.
   * No extra work in localising another editor or to ensure that it displays and works well on other platforms.   * No extra work in localising another editor or to ensure that it displays and works well on other platforms.
 +  * Means we wouldn't need to compete with other translation editors (poEdit, gtranslator, kbabel, OmegaT, etc)
 +  * Integration or TM and Glossary would work live and offline.
 +  * The webs simplicity would make us have to focus on making the interface simple (which does not mean it would not be a rich interface)
 +  * SVN & CVS access is already integrated
 +  * Any development in distributed Pootle will work with offline and online and allow much better debugging of that avenue of code
 +
 +===== Disadvantages =====
 +
 +  * HTML implementations can be inconsistant
 +  * HTML coding can be difficult (perhaps more difficult than learning a new toolkit)
 +  * Doesn't have the look of a native application
 +  * Limited by the web paradigm
  
 ===== Required ===== ===== Required =====
Line 29: Line 41:
  
 ==== Things to disable for offline use ==== ==== Things to disable for offline use ====
 +
   * Account registration, activation, login and administration   * Account registration, activation, login and administration
   * Rights management and administration   * Rights management and administration
Line 34: Line 47:
  
 ==== Things to add for offline use ==== ==== Things to add for offline use ====
-  * More flexibility as to where files are stored+ 
 +  * More flexibility as to where files are stored ie across filesystem not just in one place
   * Only available to local machine   * Only available to local machine
 +  * Some concept of browsing the filesystem
 +  * Makeing project setup simpler
 +  * Checking on how we detect projedct styles (KDE layout vs GNU)
 +
 +==== Things that are shared ====
 +
 +  * Goal setting
 +  * Error checking (pofilter)