Use horizontal instead of vertical table columns [#653730]

We're using 7 languages, and the current table layout is unusable.

This patch corrects that by stacking the translation string, instead of creating new columns.

Comment	File	Size	Author
#6	653730-usability.patch	13.59 KB	agentrickard
#1	653730-usability.patch	5.24 KB	agentrickard
#1	Picture 2.png	24.03 KB	agentrickard

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

File	Size
Picture 2.png	24.03 KB
653730-usability.patch	5.24 KB

Comment #2

Pasqualle

🇭🇺 Budapest

CreditAttribution: Pasqualle commented 7 December 2009 at 23:12

how would it look like with a long description field, like a taxonomy term description? The place for the source string looks small.

the screenshot looks nice and I know how unusable this is with 7 cols, but I do not think that you have a translator who speaks seven languages..

As I see I will have to create a theme template for this, with a selectable horizontal-vertical format..

Comment #3

agentrickard

he/him

English

Georgia (US)

CreditAttribution: agentrickard commented 7 December 2009 at 23:31

Status:

Needs review

» Needs work

That would work for me. I could rework the patch to make this a configurable option and provide two templates.

And we do actually have a use case where we need 7-12 translations for an international firm. The case isn't that the translator speaks all those languages, but needs an efficient means to enter them after gathering all the strings (probably via email or Word.)

We could also move the actions links to a separate row, and possibly make larger text display in some cases.

Comment #4

Pasqualle

🇭🇺 Budapest

CreditAttribution: Pasqualle commented 8 December 2009 at 00:03

thanks

tip: if you have outside translators then the po export-import functionality might be easier, so nobody have to type it into Drupal. It works with dynamic strings also, just there might be a bug in Drupal 6, that the location field is not trimmed at import. So you may have to run "UPDATE locales_source SET location = ltrim(location)".

Comment #5

agentrickard

he/him

English

Georgia (US)

CreditAttribution: agentrickard commented 8 December 2009 at 15:42

We're pretty sure they want a UI. I was going to write one directly onto the menu item editing form, and then found this module.

Comment #6

agentrickard

he/him

English

Georgia (US)

CreditAttribution: agentrickard commented 8 December 2009 at 16:40

Status:

Needs work

» Needs review

File	Size
653730-usability.patch	13.59 KB

Here's a patch against the latest -dev. It cleans things up a bit and adds a hidden conf variable. Since this module has no settings page, for now, to use the alt layout, you put this in settings.php.

/**
 * Conf override for translation table module.
 */
$conf['translation_table_orientation'] = 'horizontal';

I am sure there is some optimzation of code to be done. Right now I just do a pretty crude theme switch at the top of theme_translation_table. But it does work, and I may not have time for refinements.