[feature] Locale module interaction design

[Gunnar Langemark]

Project: User experience
Version: <none>
Component: localization
Category: feature requests
Priority: normal
Assigned to: Anonymous
Reported by: Gunnar ***@www.langemark.com
Updated by: Gunnar ***@www.langemark.com
Status: active

I suggest that the translation interface be changed so that it is
possible to go through translations of strings - one by one, in a way
so that when you have translated one string you are taken to the next
untranslated string - perhaps even "inside" a filter - so that you can
translate user strings, admin strings, pr. module strings etc.
It is quite cumbersome to make a locale of close to 2000 strings when
80% of the page loads are simple navigation to get back to the locale
search window.
8000 page loads I for one would live happily without.



Gunnar ***@www.langemark.com

[Bèr Kessels]

What about one page with an x amount of form fields on it?
So on one page, I can translate X locale entries. On the bottom there
would be one 'save locales' button.

I thought of this, because i exported my locales table to exel,
translated it and then imported it in drupal. A fast and good way to
translatet, by the way.

Ber

[Gerhard Killesreiter]

Post by Bèr Kessels
What about one page with an x amount of form fields on it?
So on one page, I can translate X locale entries. On the bottom there
would be one 'save locales' button.
I thought of this, because i exported my locales table to exel,
translated it and then imported it in drupal. A fast and good way to
translatet, by the way.

A even better way is to use po-files. There exist specialized programms
to assist in translation. I know that I repeat myself. :)

Cheers,
Gerhard