start

This is my list of things done and to do. Some things get done very quickly, others are medium to long term objectives. Feel free to contact me if you want to take one on.

## Onthou

#### Bug fix priorities

1. The formats we work with ie oo, csv, dtd, prop before html.
2. converters before storage taking 1 into account
3. tools unless its critical (DB thinks the tabs things is critical)
4. lastly filters

#### kid

(Just so we remember what our issues are, we probably won’t fix these ourselves)

- kid removes &nbsp; from templates
- kid sometimes inserts spaces between ajacent tags:

     <span> </span><span> </span>
    becomes
     <span> </span> <span> </span> 1

#### jToolkit

- jToolkit, bug #128
- Caching (images, .js, .css) - much better, needs patch to jToolkit
- Support for nicer error pages - done in Pootle
- Catch kid errors better and handle like others
- Handle 404 nicer? Perhaps also in Pootle?
- support for accept-language done in Pootle
- Don’t pretend to work with templates if kid is not installed
- Check perms and shebangs (like Pootle)

#### Pootle

Also see the seperate work on XLIFF work and storage format agnosticism: xliff

- User’s preffered language doesn’t work? (works on server restart, so cache not updated?)
- Clean install, can’t edit own preferences. Check jToolkit/prefs.py:80 - should return null?
- adminpages layout still need to check rtl?
- “Not in goal” always has “0 files, 0/0 words (0%) translated [0/0 strings]”
- tm-copy
- plural copy
- redirect after login
- Downloaded PO cached to much...?
- Pootle must consider plurals in PO header, uploads, prefs, etc. - pomerge?
- After registration, redirect to login, not activation... (only if already registered?)
- Should project admin be able to assign “commit” rights? Siteadmin?
- Performance on cvs merge
- Review all messages for consistency, add comments - a lot better already
- Need to review translations in pootle/ carefully for xml errors, otherwise kid barfes on them and pootle might become unusable - xml test now catches missing close tags, so it is already a bit better

- W: pootle; Executable /usr/share/python-support/pootle/Pootle/html/pootle.css with perms 0755 is not an ELF file or script.
- bubulle: W: pootle; Executable /usr/share/python-support/pootle/Pootle/templates/adminlanguages.html with perms 0755 is not an ELF file or script.
- bubulle: W: pootle; Executable /usr/share/python-support/pootle/Pootle/templates/adminprojects.html with perms 0755 is not an ELF file or script.
- bubulle: W: pootle; Executable /usr/share/python-support/pootle/Pootle/templates/adminusers.html with perms 0755 is not an ELF file or script.
- bubulle: W: pootle: script-not-executable ./usr/share/python-support/pootle/Pootle/pootle.py
- bubulle: W: pootle: script-not-executable ./usr/share/python-support/pootle/Pootle/filelocations.py
- bubulle: W: pootle: script-not-executable ./usr/share/python-support/pootle/Pootle/conflict2suggest.py
- bubulle: not sure that these ones should be installed 0755 or not
- bubulle: jtoolkit actually triggers a lot of those
- bubulle: this is because the Debian policy requires files beginning with a shebang line to be executable

- munzir: 1. Avoiding ‘right’ and ‘left’ in markup according to: http://www.w3.org/International/geo/html-tech/tech-bidi.html
- munzir: 2. Best Practice 12: Watch out for white space. same link above. It would be neater if you removed the spaces in [ Arabic ] ... spaces around brackets and parenthesis cause more harm than good. As a result you won’t need unicode-bidi: embed
- munzir: 3. since the styling shouln’t go into markup, it’s better to make pootle able to load a pootle-rtl.css file in addition to pootle.css in case of rtl languages to override relavent rules. That file would set things like the borders, floats, .... to support rtl
- munzir: 4. make pootle also load a style.css file if available so any one wants to customize pootle won’t play with pootle.css and lose his changes upon upgrade.
- munzir: 5. the line that says: <div lang=”” id=”banner”> is not correct. It’s not allowed to have it like this.
- munzir: 6. validate with http://jigsaw.w3.org/css-validator/ and get rid of the errors. It’s very easy ;)

- chahibi: Edit buton
- Support KDE plurals
- When assigning people, only list those registered for the project. - Clytie - always filter on registered for language
- When assigning rights, only list those registered for the language. - Clytie - always filter on registered for language
- Message for a language displayed on the language page
- Message for a project displayed on the project page
- Make textarea for translation (and for comments) be 100% of the available width. Also remove the javascript to widen and narrow, and the personal option to specify the width (and the default width in the code?)
- Add project attribute for the layout type
  - Admin interface
    - project layout type (auto, gnu, nongnu)
  - When variable is accessed
    - not found - auto
    - if auto - determine and use for session
    - if gnu/nongnu - use for session

#### Toolkit

- ‘é’.isalnum() is False - audit effect where isalnum is used
- output of multiline obsoleted comments are incorrect
- pot2po breaks plurals, doesn’t do fuzzy mathing, etc.
- pootle.py : check new revision: 1.29.2.4; previous revision: 1.29.2.3 (should probably not be ported to head)
- add docs to default toolkit
- pofilter: checks for source language:
  - unammed variables, space at start and end.
  - Message with more than 4 words and no end punc - possible problem.
  - pure punctuation and variables need explanation
  - A list of words that can confuse: register, manual ie the noun verb issue
- consider wording of fuzzy in base

## Gedoen

- Visible <br> is displayed in textarea for editing
- Create MO files not updated correctly if altered
- Create MO files doesn’t display correctly in projects adminpage
- Activated checkbox on user admin page doesn’t update correctly
- checker style doesn’t display correctly in projects adminpage
- Pootle console output (Now in comments, perhaps most useful as an option, since the output can be very useful during debugging and development.)
- meta tag in generated pages say charset=us-ascii
- jToolkit needs to call .serialize(output=”xhtml-strict”) or whatever flavour we prefer in web/templateserver.py and web/server.py
- redigeerskakel in viewmode
- Import po files for pootle and jToolkit - David
- Pootle.title doesn’t display in titlebar as promised in pootle.prefs
- nlocalize() doesn’t work? po.py::parseheader rewritten, need to check 0.9 when David’s merging is done
- usernames ascii only
- Layout of plurals in view mode
- search in grey navigation bar
- move login
- Implement the table sorting .js that Rosetta uses so that we can sort our stats tables.
- Make Home actually point to the root of the server. And change the current Home to ‘My Account’
- Show comments: Automatic, translators and location identifiers
- Show fuzzyness

## Eendag op 'n reëndag

These are medium to long term things todo. Any help appreciated.

- TODO: Fix row colouring after sorting Thanks, Dwayne.
- Quick navigation (next 10, etc) in edit mode
- Fancy spaces
- Wiki integration - At least site and project descriptions can contain html now.
- js table sorting mixes direcotries and files
- Pootle must display a nice error page of some sort
- Check complete escaping and encoding support for po (see http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/msgfmt.html or http://www.tiem.utk.edu/cgi-bin/man.cgi?section=1&topic=msgfmt and also the thread starting at http://lists.gnu.org/archive/html/bug-gnu-utils/2003-06/msg00222.html)
- Column headings (abbreviated) (and localisable) to improve layout - perhaps rather use the complete width of the page instead of just the content area. Especially useful for the rtl layout.
- total row in stats display
- layout br nicely to add newline (if po contains html)
- Display version / status information for PyLucene, elementtree, kid, etc. on about page too. Thanks, Dwayne
- Edit tm entry
- Audit dialects and dialect behaviour
- tmx in xliff
- make extra files hidden ? - this is OS dependent
- Set fuzzy in Pootle - See http://bugs.wordforge.org/show_bug.cgi?id=188 - thanks to Andreas
- Able to edit comments - Perhaps Andreas will do? - he did
- Use PyLucene better
  - language specific indexing
  - better error handling - can user do lucene query, or text only?
  - Update to 2.0 API Nicolas submitted a patch
- spell checking
- Include all languages, but have “activated” field (like accounts), so correct information can be added by siteadmin without having to search for it or edit prefs file
- TM
  - We need to see where the string came from eg OOo, FF, etc
  - Who did it - not much use now
  - and preferably convert accelerator keys to the ones used in the current translation
- Split CSS
- “I can suggest things like replacing those links of Grow, Shrink, Broaden, Narrow but some ajax code that let you drag and resize the box” - Munzir Taha (perhaps using http://jquery.com/)
- “pootle misses Search And Replace” - Youssef Chahibi
- Names for different plural forms, for example: Arabic Plural Form 3 = مثنى
- Have the activation code emailed again. (Is done, perhaps a message?) Activation code is mailed again if user tries to reregister
- multiple textareas for editing instead of just one
- On translate-pootle: “How about having, as one of our Quick Links, the place we were when we last logged out? Just use the path as the link name.” - Clytie
- About word counts vs string couts Jamil says: yea.. but it will be better if we can get in the summary page too. we can set this option in the option page. who wants to see what. i mean, this can be configurable in the option page

## Things to think about

- When we upload an XLIFF file for _overwriting_ should we throw away the suggestions in alt-trans tags?

## 2007

- Check why wiki doesn’t work with google

- Write ideas about extentions of the po xliff representation guide (msgctx en #|)
- Pretty usernames in assigns interface - mooi gebruikername - 2
- Use msgctx in Pootle merge code - 8
- pomerge with msgctx - 8?
- import jtoolkit and apply fixes 16 - maybe
- Make textarea for translation (and for comments) be 100% of the available width. Also remove the javascript to widen and narrow, and the personal option to specify the width (and the default width in the code?)
- Add project attribute for the layout type
  - Admin interface
    - project layout type (auto, gnu, nongnu)
  - When variable is accessed
    - not found - auto
    - if auto - determine and use for session
    - if gnu/nongnu - use for session

## Non-project

- Wiki work
  - Find unused pages and remove
  - link meaningfully to the one, correct place
  - Update wordforge site
- SVN work
  - Update README and related files
  - See how to do offline documentation
  - Look at failing unit tests - Andreas
  - Bugzilla (perhaps 180, 192, 203, test 177, 110)
  - Look at contributed patches
    - Nicolas François
    - Lars - Version control
  - jToolkit
    - Get started
    - Look at patches
- Build big windows installers

[Zuza]

- Look at hyph-build system
- Update af wiki pages
- Consider af_NA

## Week van 2007-01-15

- Look at original project proposal and do a checklist
- XLIFF testing of trunk
- Look at integrating static docs with at least the toolkit
- Look at integrating API docs with at least the toolkit
- Update right
- pot2po bug with changing location
- Bugs reported for 0.11rc

## Week van 2007-01-15

- New pot for 0.11
- Update translations on pootle.wordforge.org
- Notify translators
- Install 0.11rc on server
- xliff2po bug that Sophon reported

## Week van 2007-01-08

(was totally overcommited)

- Problem with assignments - fout met toekennigs - 4
- Pretty usernames in assigns interface - mooi gebruikername - 2
- Use msgctx in Pootle merge code - 8
- pomerge with msgctx - 8?
- file overwrite in 0.10 branch - 5
  - Change default rights to not include translate right
  - Enable suggest right by default - took very long due to complications in unit tests
  - Overwrite right
- new pot - 1
- build translate-toolkit-1.0beta from trunk for the pootling guys - 2
- Make textarea for translation (and for comments) be 100% of the available width. Also remove the javascript to widen and narrow, and the personal option to specify the width (and the default width in the code?)
- Add project attribute for the layout type
  - Admin interface
    - project layout type (auto, gnu, nongnu)
  - When variable is accessed
    - not found - auto
    - if auto - determine and use for session
    - if gnu/nongnu - use for session
- import jtoolkit and apply fixes 16 - maybe
- Mozilla releases - released Firefox and thunderbird 1.5.0.9
- Write ideas about extentions of the po xliff representation guide (msgctx en #|)