start

## David Fraser's TODO

This is my scratch pad of tasks ... if you want me to do something ask me rather than changing this We’ve now taken to having weekly meetings, so this stuff actually sometimes happens (and should at least get updated...)

### Weekly Tasks

#### Week of 2006-06-05

- Work out dtd escaping
- Apply remaining escaping patches to 0.9 branch
- File bugs with Mozilla on invaild escapes in calendar and p3p source
- Fix .ts xml problem
- Write up analysis on metadata
- Write up proposal on using database for metadata
- Continue locking and base classes migration in branch
- caching - look at testing memory consumption with file parsing
- Get translations into jToolkit CVS

#### Week of 2006-05-30

- Look at Mozilla Official l10n process
- Planning meeting, discussion on locking, base classes, etc
- Write up discussion and issues from today’s meeting for Wordforge
  - Meta data DB, also create actions
  - caching - look at testing memory consumption
- Refactor Pootle’s pootlefile interface to use base classes and enable locking - a bit more to do
  - Pootle on XLIFF
- Look at implementing statistics in a separate interface, using a database
- Release jToolkit and participate in 0.9 bug fixing
  - Get translations into release also in Pootle
  - Look into dtd escaping

#### Week of 2006-05-21

- Fix up mozilla conversion and quoting bugs
- Interact with debian about wordforge
- Look at Pootle locking

#### Week of 2006-05-01

- Add benchmarks for user interaction (e.g. submitting a translation)
- Migrate everything to base classes (including dtds etc)
- Migrate Pootle to using base classes (even if it breaks existing features)
- look at locking, to enable mod_python etc

#### Week of 2006-04-23

- Merge kid branch to HEAD
- Work on Pootle performance and scaling issues

#### Week of 2006-04-10

- Branch 0.9 (Friedel did it)
- Fix up jToolkit and XML bugs
- Release 0.9 (under whatever name, two branches of Pootle)

#### Week of 2006-04-03

- Clearing out other cruft (4)
- Merging backwards and forwards (2)
- Doing release of 0.9 (2)
- Looking at improving base classes (6)
- Meetings, bug triaging etc (2)

#### Week of 2006-03-27

- helping friedel with kid (2)
- Converting translation page (8)
- Clearing out other cruft (4)
- Merging backwards and forwards (2)
- Doing release of 0.9 (2)
- Sorting out network problems over the phone

#### Week of 2006-03-20

- Look at consistency in uploading files with new / missing translations
  - Upload and Download merging policy
- Finish off templates
- Bug day
  - send out email

#### Week of 2006-03-15

- Test uploading over existing files (4)
- get translations from Pootle.wf into CVS (4)
- Templating of site: main user fronting pages (8)

#### Week of 2006-03-06

- Upload and download tests
- Upload a zip

#### Week of 2006-02-27

- This meeting (1)
- Help Friedel with Plurals etc (5)
- Write unit tests for Pootle (7)
- More ooo-build work (remaining time)

#### Week of 2006-02-20

- Release 0.8 for real - actually started (2)
- Fix some tests for Dwayne (2)
- Merge Friedel’s variable stuff (1)
- Help Friedel and Charl with Pootle (4)
- Do an ooo-build for Dwayne (3)
- Pootle unit testing (4)

#### Week of 2006-02-13

- Release 0.8 (3)
- Fix up links to toolkit in toolkit-0.8 on wiki (1)
- Migrate 0.8 branch to HEAD (6)
- Migrate convert apps to new API (5)
- Start migrating Pootle (3)

#### Week of 2006-02-06

- Basic example test_ for all apps (2)
- Roundtrip testing (5)
- Moz2po and po2moz against CVS (4)
- escape testing (3)
- Release 0.8 (3)

#### Week of 2006-01-30

- Look at technologies (3)
  - Bazaar
  - XMPP
- str - fix related errors
  - abstracting string manipulation into base classes (3)
- 0.8 release (6)
- porting XLIFF to base.py (4)

### Links to remember

These are for further investigation

- http://www.lehuen.com/nicolas/download/pytst/ - Ternary Search Tree for fast distance-matching search on text strings

### Old Task List

#### pootle for feedback

- improve search so it can be used to locate string
- let person include suggestion and email address
- email suggestion to list with links to accept / reject
- send email to suggester with feedback

#### other reporting tools

these are to help with beta testing

- simple frontend to bugzilla for more complex bugs
- spellchecker - suggest words
- word discussion for glossaries
- dictionary entry - submit and classify words (noun verb etc)

#### mozilla stuff

- do our own localized builds
- make sure translate toolkit is working
- work out how many words different between 1.1 and 1.5

#### openoffice build machine

- vmware / qemu ?
- analyze Visual Studio / Visual C++ Express / mingw
- do rebuild with new translations and dictionaries this week

#### csv2po

- adding comments, review comments etc
- allow review in column 4

#### po2csv

- select columns and add comments in somewhere else
  - location, translator-comments (#., # )
  - #, review gets dropped. so should be # with a special mark

#### pootle

- south african installation - on scir.sjsoft.com
- openoffice.org installation on arsaperta machine - in progress
- go through bugs - dwayne’s patch for bad translations

#### south african openoffice.org

- elaborate customizations (e.g. ‘n etc)
- south african english

#### translation memory

- running as a service ?
- offline delivery, simple
- poedit can use it

#### conflict resolution

- pocompendium can find words translated differently
  - #-#-#- filename: xxx #-#-#- otherfilename: yyy
  - cancel is a problem - then show all strings with cancel in it
- inversion - see which zulu things correspond to different originals
  - Kulungile for OK and Good - then search for all translations of OK and Good

### lower priority

#### other editors

- poedit / kbabel linking to checks
- kbabel on windows? (Kexi guy)

#### dwayne looking at

- fonts
- keyboard

### next priority

#### mozilla

- firefox + thunderbird roundtrip working
- from pootle

#### spellchecker

- found spellchecker stuff
- write our own spellcheck link for windows
- user submissions?
- ? handling encodings messing things up for ZA words
- wrap aspell around MS checkers

#### pofilter

- give clarity on reason (the variable that caused a problem, the word that shouldn’t be translated, etc...)
- X-Accelerator-Marker
- language-specific rules e.g. for Zulu don’t check spaces
- spell-checker - send well-defined comments to translators

#### pocount

- xml output

#### use pootle for feedback from beta testers

- lock it
- report errors / submit suggestions - send to list?
- email integration

#### pootle unicode enhancements

- look at integrating Unicode Pickers

#### ADAPT-IT

- investigate

#### glossary

### notes

#### dwayne's process

1. pofilter
   - a few checks at a time, then all at once
   - if lots of errors, will do accelerators etc
   - mark them for review
2. manually edit the review, add comments
3. go through all the translations and check for strange stuff
4. commit to CVS

1. extract the review for that phase, pack and send in a zip file
2. get stuff back, checks everything is there
3. do a diff
4. use pomerge to merge stuff back (* this should remove the reviews)
5. cvs diff
6. commit