Double translation of Field titles

I think that the double translation may be coming from field labels, which are filled in from defaults that are already translated, but the label itself is also dynamically translated. I'm not sure this is preventable.

No idea if my problem is the same as yours, but i wrote this:
http://abraham.labs.novij.at/misc/viewsfix.js

And it works for me.
Just enable a block with "

" where you need the titles removed.

potential solution given, no response.

I'm having this same problem with views-7. This is the problem:

We have a D7 with catalan, as main language, english and spanish, and a view with a table which contains a column with a label named "any", which in catalan means year. The problem is that "any" has also a meaning in english, which is translatable into catalan as "qualsevol".

Now, the problem is that if I use "Year" as the label, views shows "Qualsevol", this is, it translates year into catalan as "any" and it translates again "any" (as if it was in english) as "qualsevol". It double translates, as merlinofchaos mention in #1. BTW, If I put "any" it translates it as "qualsevol", so there is no way to put "any" meaning "year" in catalan other than puting "any ", with a blank space, for instance.

Is this, really, not preventable?

The translation logic completely changed in the meantime, so it might just be preventable.

Closing from a lack of activity.

Let's keep this active, sounds like a real fixable problem.

@bojanz

Sadly this seems to be wrong.

The problem are the labels. The default value of this label is already translated into language X. So for example title get's titleX.
This is the value of the label option.

Then the view is rendered and wush: t('titleX') and there is the double translation.

So we actually need to be sure that we fetch *untranslated* labels from entity api.

Hmm. Interestingly, I'm not sure this is the case as I thought it was.

I can't see a why labels might be getting double translated at this point. Are we sure this is still happening with the new translation system?

It's not about the translation system of views.

Let's take for example content: title => the default label is t('title')
So the stored value in german for example is "titel".

And then when you execute the view the label "titel" is runned through the translation system again.

So there are two issues:

in d6--2 the stored value was runned through t() and changed so also in the interface itself.
If you save then the value get's runned through t() again etc.

This is fixed with the new translation mechanism in views3.

There is the other case described in #340064-11: Double translation of Field titles

Togehter i see this issue as fixed. Please open it again if i'm wrong.