(Follow up from http://drupal.org/node/684222#comment-3387970)

I'm using http://drupal.org/project/i18n to translate the content of my website, but it seems to me that the multilingual variable "tax name" is not translated on all places ...

I translated the variable at admin/store/settings/taxes/vat and it works here:
YES: Add "including MwSt" or "excluding MwSt" to product prices.
YES: Add "excluding shipping costs" to shippable product prices.

"MwSt." is the translated name for "VAT" – that's how it should be.

But if i go to "admin/store/settings/taxes" i can't see the changes in the table anymore:
There it still is "Name: VAT" and not "Name: MwSt"

I wouldn't bother about that, but the same behaviour unfortunately is on the product-pages (after flushing all caches):

English: Price: 0,00€ including VAT excluding shipping costs
German: Preis: 0,00€ inklusive VAT zzgl. Versandkosten

... it should be (in my opinion):

German: Preis: 0,00€ inklusive MwSt zzgl. Versandkosten

On the german cart-page it even mixes it up:

Subtotal excluding MwSt: 0,00€
VAT: 0,00€

Why is it translated on one place, but not on the other? Bug or feature? ;-)

Thanks for your help!

Tobias

Comments

mstrelan’s picture

mstrelan commented

Some more food for thought (this is becoming far more complex than it should be) - I'm not sure that a "translation" is exactly what we need, rather a "localisation". Translations deal with languages, but English is spoken in 53 countries, French in 29 countries and Spanish in 20 countries.

I assume French Canadians would translate this to GST as that is the tax in Canada. Same goes for English Australians. Spanish speaking countries, possibly excluding Spain, call it IVA, or Impuesto al Valor Agregado which directly translates to Value Added Tax. For more examples see http://en.wikipedia.org/wiki/Value_added_tax

I guess the main point I'm trying to get across is that the tax name should not be determined by the spoken language, but the geographical area.

tfranz’s picture

tfranz commented

Yes, i understand ... (?)

I can translate the word "TAX", but i think i shouldn't really translate the word "VAT", because the spanish "IVA" is similar but not the same as the english "VAT" ...

If i go to Spain, then there could be – "in real life" – for the english visitor:

Subtotal excluding tax: 0,00€
IVA: 0,00€

Comparable: if i sell my products from spain with a spanish online-shop, then there should be on the product-page:

Price: 0,00€ including IVA excluding shipping costs

So if i translate the multilingual variable "Tax name" to german "Steuer" or spanish "el impuesto" or english "tax" it behaves as above.
But then "Tax name" isn't the name any more, but only the word "tax" ...

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Component: Code » User interface

I agree that calling the variable "tax name" is confusing, but I think "tax word" will also be confusing to users. The reason this was introduced was for the case of multiple taxes, the "tax name" is the name of all taxes combined, whereas each individual tax has its own name (or abbreviation). In your example of "0,00€ inklusive VAT zzgl. Versandkosten", it is labelled using the actual tax rule name ("VAT") because multiple taxes may be in use and we must specify which one it includes, and it is difficult to translate these rule names separately due to the way the names are stored.

Any suggestions on improving this will be gratefully received!

xibun’s picture

xibun commented

+1 (also see my older - but still duplicate ;) - issue: #800184: multilingual tax line item)

grub3’s picture

grub3 commented

This is a real issue as it is not legal to print a French invoice with "VAT" instead of "TVA".
I could not find the i18n_variable table. Where is it?

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented

@grub3: install the i18n module and you should be able to translate the "tax name" variable. But if you are based in France, you should also just be able to call your tax rule and tax name "TVA" instead of "VAT", which should avoid this issue entirely.

grub3’s picture

grub3 commented

@longwave. Oh thanks, I did not notice.
I am running a multilingual web site, so I need to translate VAT.
My main tax is named "VAT" in English.

In /admin/settings/language/i18n/variables
it displays:
VAT multilingual (yes) and translated (no).
uc_vat_name multilingual (yes) and translated (no)

How do I translate the variable?
Shall I INSERT records in the i18n_variable table?

grub3’s picture

grub3 commented

@longwave.
Thanks, it worked. I had to switch from the edit pages in French and English and update vales and it worked like a charm. Thanks !