I've been working with the localization Server for the first time today. Even as an "experienced" Drupal user it took me a while to understand that I've got to go down to the bottom of the page to save my suggestions or corrections.

Since you got those little buttons for edit and Detailed Information it would be more consequent to have another button for saving at every field.

Did you do that because of performance reasons, so people enter multiple strings before saving, so there are not too many page loads? If so, I could understand that. Or is it maybe an option that is not turned on in our server (german usergroup)?

I raise this because you have done a very good job to improve the UI in comparison to a "standard drupal" interface.

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Indeed, this would be great to have. There were suggestions to have a mode with one translation field at once and move to the next one with an AHAH/AJAX callback as in http://www.rememberthemilk.com/services/translate/ Basically I am trying to gather feedback and solidify a plan to how these things should be done instead of sticking AJAX everywhere I could :) So I agree that this is a good suggestion. First I'd like to concentrate on rethinking the translation interface (see http://drupal.org/node/215286 and please comment there). Then come more convenience features :)

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Closed (duplicate)

The new UI released in 6.x-alpha1 and 5.x-alpha4 contains a save button on all the strings. There are two issues with it. One is that it does not actually work (somehow the JS action is stopped IMHO, at least I put in some time to debug, but did not reach a result). Second is that it would submit the whole form and not just save the individual string. It needs fixing either way. It would be great to fix this up.

This issue is tracked at http://drupal.org/node/306371