Pootle project commands snag list

• Update can remove existing translations with empty strings

• Unable to clone any TP after project already created

  • CommandError: {'code': [u'Project with this Code already exists.']}
  • This raises the point about what to do if a previous project was already there. I guess a --force or such should be provided to allow copying a TP to an already existing proj.

• Cloning of TPs fails if there is a filled PO_DIRECTORY for a project

• Cloning a project unmutes muted failing checks.

• Moving a single TP to a new project doesn't remove stats for previous project, so the TP is still listed there.

• pootle project clone myproj fails with traceback (note no --target-project was specified)

• pootle project remove myproj --language=gl removes TP, but stats are still there showing the _XXX_LAST_CREATED_gl-myproj_LAST_CREATED_XXX

• Cloned a project to myproj, then moved one of myproj TPs to another project, then tried to clone that specific language from the first project to myproj again and it failed because there were conflicting files on POOTLE_TRANSLATION_DIRECTORY for myproj (the files were not removed on disk when moving the TP before).

• Cloning a project does not copy its Pootle FS metadata and language mapping

• Not an error but something to fix: specified two --language when specifying --target-language and the error message is confusing You must set the only source language.

• Clone leads to OSError: [Errno 2] No such file or directory: if project dir doesn't exists

• ./manage.py project update sproj --target-project=tproj --language=af --overwrite does not keep tproj translation

---

This won't be done during this iteration.

• Cloning a project does not copy suggestions. Not sure if that is intended.

I'd say if you need to add new TP you should use clone command.

• update (no --translations) does not add TPs in source to target. Not sure if that is intended.