Yup, I meant the .talk files sorry. I see your point that's the whole reason for bringing this up is to see what works and doesn't. Where do I find what programming languages you are using so I can get working on some of these maybe?
-----Original Message----- From: rockbox-dev-boun...@cool.haxx.se [mailto:rockbox-dev-boun...@cool.haxx.se] On Behalf Of Paul Louden Sent: Sunday, March 28, 2010 12:56 To: Rockbox development Subject: Re: Idea Discussion: making voice more usable throughout Rock box Unfortunately, I find it a little hard to understand what exactly you're saying in your message. For example, ".toc" files? Are you referring to ".talk" files? Anyway, one important thing to keep in mind that while accessibility is a significant goal of Rockbox, it isn't accessibility software. Improvements to the accessibility must generally be weighed against the impact they will have on its core roles as a music player software. As it stands outside of plugins (which aren't a core role) there should be little functionality denied unsighted users and in relationship to audio file playback especially. I'm not sure in which areas you're talking about integrating voice "more tightly." It's a very vague phrase that doesn't really have any more meaning on its own. As for plugins, until such time as they're fully translated and integrated into the language system it will simply be impossible to extend voice to them in a useful and expandable way. There's already been some work on this but as with many things, it's not an issue of "what should be done?" so much as finding people willing to dedicate the time to hammering it out and ensuring it all works well. A good starting point, then, is to actually find and describe clear problems that aren't known and discussed elsewhere on the list or in the forums, and to make sure that when you do discuss them you're careful to use the terms and spellings used in the manual so that time isn't wasted in back and forth simply trying to understand what you're saying in the first place. That being said, don't expect much to come from many things - most changes in Rockbox come when someone directly affected by something puts in the work to change it. It's somewhat rare new features or improvements happen by someone with no direct interest in the project choosing to implement it. Bugs are different, though. If our manual says something works a specific way, and it doesn't, or it crashes while doing so there's generally some interest in getting the issue resolved.
