Tools brainstorm
From My Wiki
OTT07-BrainstormToolsGroup
Needs and Quick Wins
- Lack of integration/interoperability between tools
- Different areas have their own tools, but it's difficult for a project to use them all
- Style guide for each language
- Project Mgmt / workflow tools
- Better use of standards for storing translations within projects
- po-files and compatible files
- reason: many apps don't allow easy export into po or po-convertible formats.
- Better integration between different projects,
- shared TM
- shared glossaries
- common ui's and systems
- In-line tranlations in graphics, i.e tools for showing svg's that allows in-line translation and saving as po-files
- built into GLADE or other ui designers
- Lack of visibility of existing tools
- possibly a best-practice guide segmented on roles
- Open content projects
- new free software tools
- web site projects
- dimitris, dwayne, danilo potential collaboration
- Create a generic model that describes what a translatable project is, describe roles in such a project, and share these models, and interoperate.
- Using each others tools, integration
- Brian can improve his own product by adding po support into that, alowing the use of other tools
- defining standards that are lowest common denominator
- po for text strings
- web service standards/convention for REST interface ???
- RSS for moving data between systems
- open-tran.eu
- common API's for TM tools to contect and collect translation memories
- Integration of transifex, damn lies, and pootle
- plugins for CMS's to export content into po-files
- possible bounties or looking for funding as a group
- possible generic code libraries
