"ext Mohammed Hassan" <[EMAIL PROTECTED]> writes: > What I'd propose is we/I replace the logical IDs with Engineering > English in the POT files you use to translate and convert them back > upon packaging and building.
One immediate problem I see with this is that multiple logical ids can map to the same Engineering English string, so you can't reliably reverse the mapping. (Also, the code itself should start using Engineering English itself, of course, to make it more useful to external developers that don't have the UI specs, and because that is how God intended it to be done. :-) It would be interesting to take our current translations and mine them for the logical ids that map to the same Engineering English, but at the same time have different translations in some language. These are the cases where we would need to use the "menu|Open" construct in the code instead of the existing Engineering English string. Identifying and handling these cases is where I see a large part of the effort needed to move away from logical ids, so it would be good to get an overview. Once that has been dealt with, we could consider using your scheme, or we could consider Engineering English instead of logical ids everyhwere in our processes. _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
