[support] local.module and filtering strings

[Kobus Myburgh]

> 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 

I see your point.

> 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.

I am managing the translations as it is. Sorting the translation
strings by module would be nice, but not a necessity for me - it would
be like the permissions page - having it sorted differently (or having
the header repeat from time to time) would be ideal for me, but not
necessary. My point being that PoEdit probably doesn't work well with
screen readers, and that is why Mohammed uses the locale.module. This
functionality, although not necessary for me, it may be vital to
Mohammed.

Groete,

Kobus