Closed (fixed)
Project:
German translation
Version:
master
Component:
PO files
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Aug 2011 at 07:20 UTC
Updated:
11 Mar 2019 at 20:37 UTC
Jump to comment: Most recent
Comments
Comment #1
drcho commentedIf you place a whitespace after the %1 then it works. Curious.
Comment #2
dawehnerActually i have no idea on earth where this comes from. Are you able to grep/search in all your code after this snippet?
If you put this into drupal there are gazillions of sites with this problem, crazy.
Sadly i can't find this in my code basis of drupal+contrib modules.
Comment #3
Reen commentedI found the bug!
It is in the translations.
go to /admin/config/regional/translate/translate and search for "command"
you will find one entry %1. Edit it and you will see.
Maybe someone should move this bug to the translation section.
Comment #4
dawehnerLet's do it, seems to make sense but sadly i can't reproduce this, even imported a full po file.
What kind of strings do you have imported on your site?
Comment #5
hexabinaer(Issue applies to Drupal core 7.8 as well, so I'm not sure about the version change in #4)
Hopefully my beginner's pondering can be of any help ...
To reproduce this
Install admin_menu, activate Administration views and enable the view Taxonomy Term. Check for current translation. (I am only using German and English so far - does it appear in any other translation?)
I use Localization update. The phenomenon appeared when I used it to apply all pending translations (although I'm not sure if I have enabled the taxonomy term view beforehand). But I can't find the strings in any .po file, neither in /sites/all/translations nor elsewhere.
Thoughts
I searched a dump of my database for "command-with-section" and found it 3 times - which is exactly the amount of taxonomy terms I clicked to verify my findings. This is way above my head, but is it possible that this funny "translation" is somehow generated?
I reckon once you use the interface translation to get rid of this, you won't be able to reproduce it anyways - am I wrong?
Comment #6
marcoka commentedi had that too.
just go to: http://dev.url.com/admin/config/regional/translate/translate
and search for @command-with-section
and the kill the funny translation
Comment #7
pascalduez commentedI just discovered this as well. Happened after running a batch update through the Localization update module.
Seems like an error in the latest views translation German set (line 737)
http://ftp.drupal.org/files/translations/7.x/views/views-7.x-3.0-rc1.de.po
As mentioned in #6 removing the string in the translation interface resolve it.
Comment #8
pascalduez commentedComment #9
pascalduez commentedComment #10
hass commentedLooks to be fixed or at least I'm not able to find these two strings on l.d.o
Comment #11.0
(not verified) commentedmore explications
Comment #12
joachim namyslo