I'm not understanding why our Drupal installation with 3 languages and English as the original source shows all three languages of developed content as source in the translation interface.

We want to instruct the 'client' to translate menu items and similar strings from an exported .po file yet this is complicated if it exports the original string in the 3 current languages.

Is this a fixable issue? Or is it not an issue but standard?

CommentFileSizeAuthor
#2 Translate-interface.jpg155.94 KBdsc74
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drewish’s picture

Status: Active » Postponed (maintainer needs more info)

i'm not sure i understand what you're running into. could you post a screenshot with some annotations?

dsc74’s picture

FileSize
155.94 KB

please find attached

drewish’s picture

Project: Translation Overview » Drupal core
Version: 6.x-2.3 » 6.x-dev
Component: User interface » translation.module

That's not a screen provided by the Translation Overview module. It looks like a core Drupal form. Re-categorizing this issue.

dsc74’s picture

excuse me for being a div but does "Re-categorizing this issue." mean you have?

dsc74’s picture

Status: Postponed (maintainer needs more info) » Active
dsc74’s picture

Assigned: dsc74 » Unassigned
Priority: Normal » Critical
kdebaas’s picture

Project: Drupal core » Translation table
Version: 6.x-dev » 6.x-1.0-rc2
Component: translation.module » User interface
Priority: Critical » Normal
Status: Active » Closed (duplicate)

Please only mark as critical that which breaks functionality completely. And submit your issues in the right issue queue: The screenshot shows the interface from the Translation table module. A quick look over there reveals a duplicate issue to which you could add your perspective: #636126: Why does the original language also show up as it's own translatable column in the translation table?
Cheers