Greg,
To me, sorting by module inside the interface isn't a solution
because
you still have the problem of a new module giving you 300 new
strings
- the presentation layer is just different because it is a web UI
instead of a POT and I don't see how that makes them more
manageable.
Mohammed is blind, and his screen reader probably doesn't interact very well with the program. That is why the PO program may be a bit difficult to use. Mohammed has been using Drupal for a long time now, and is familiar with the interface and everything. This is why this solution would work for him.
Further more - It seems to be simple to implement an elegant solution for this. Imagine being able to filter only messages for a specific module. Wouldn't that be just dandy? I will like that feature. I will see if I can code it and send a patch. I am not an expert coder though.
My opinion is English speaking people in general don't use the locale/i18n module as much, so the usability issues for you guys aren't that apparent as they are for visually impaired people or people whose native language (like me and Mohammed) is not English.
Regards,
Kobus
Kobus Myburgh wrote:
Further more - It seems to be simple to implement an elegant solution for this. Imagine being able to filter only messages for a specific module. Wouldn't that be just dandy? I will like that feature. I will see if I can code it and send a patch. I am not an expert coder though.
This is rather difficult to do. It might be possibly if you only use imported strings as the comments that the strings have (see the POT files) indicate from which module they are (Note: We also shorten this comment field as it gets too long if a string occurs in more than one module).
However, Drupal also collects untranslated strings as it encounters them. In this case the comment contains the URL where the string was encountered. If the string occurs in a block this might be any url and you can't decide which the original module was.
I wonder if the solution we envision for the translations teams might be a solution for you: We plan to have a Drupal site where you can translate any Drupal strings inline, i.e. where they occur on the Drupal page. This will however rely on JavaScript and I don't know how well screenreaders support this nowadays.
Cheers, Gerhard
-
Gerhard Killesreiter -
Kobus Myburgh