> Isn't it possible to add options to activate or desactivate those > voicing features so everyone could use it or not? Part of the point though is that adding functionality for unsighted users can also increase code complexity, binary size, and RAM usage. Also, if the voice file reaches a certain bound it may become unusable on the Archoses.
All features (voice or not) should consider that adding things isn't free, so there's always some small (sometimes immeasurable, but there) negative cost for people who don't use those features, even when turned off, if they're compiled in. So while it may be possible to voice every single thing, one should consider how much increased usability it adds (for example, if the feature is already usable blind without significant inconvenience, adding extra voice prompts, while nice, may be quite unnecessary). I'm not saying anything about any specific patch, mind you, as I've not looked through. It just needs to be considered that Rockbox, as a project, isn't specifically about enabling devices for blind users, and while it is a significant goal, it must be balanced against everything else it strives to attain.
