Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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?
Comment | File | Size | Author |
---|---|---|---|
#2 | Translate-interface.jpg | 155.94 KB | dsc74 |
Comments
Comment #1
drewish CreditAttribution: drewish commentedi'm not sure i understand what you're running into. could you post a screenshot with some annotations?
Comment #2
dsc74 CreditAttribution: dsc74 commentedplease find attached
Comment #3
drewish CreditAttribution: drewish commentedThat's not a screen provided by the Translation Overview module. It looks like a core Drupal form. Re-categorizing this issue.
Comment #4
dsc74 CreditAttribution: dsc74 commentedexcuse me for being a div but does "Re-categorizing this issue." mean you have?
Comment #5
dsc74 CreditAttribution: dsc74 commentedComment #6
dsc74 CreditAttribution: dsc74 commentedComment #7
kdebaas CreditAttribution: kdebaas commentedPlease 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