OpenCart Community

Hi.
I am using OC 3.0.4.0.
This issue with the translation of the VAT rate still exists !!!
Is there any working solution?

I'm refering to this topic here: viewtopic.php?p=703833

leatherboy wrote: ↑

Tue Dec 24, 2024 7:17 pm

Hi.
I am using OC 3.0.4.0.
This issue with the translation of the VAT rate still exists !!!
Is there any working solution?

I'm refering to this topic here: viewtopic.php?p=703833

Tax names and titles are not set in language files but in the tables and those have no language id and are thus the same for all languages.

I understand that.
Do you think it is right to have a Greek word in the English or French cart and vice versa?
And do you think that it is so difficult to solve this issue after so many years?
I think that it is unacceptable.

leatherboy wrote: ↑

Fri Dec 27, 2024 6:38 pm

I understand that.
Do you think it is right to have a Greek word in the English or French cart and vice versa?
And do you think that it is so difficult to solve this issue after so many years?
I think that it is unacceptable.

"I think that it is unacceptable.", and then what?

then nothing!!!
I dοn't and you probably dοn't develop OC.
But if the developers who support OpenCart consider it a multilingual program then they should fix this problem as well as some others related to translations which are however solved in indirect ways.
if for anything, we accept the "then what?" for an answer, nothing would develop.

@leatherboy
Are you a shop owner or a developer?

leatherboy wrote: ↑

Fri Dec 27, 2024 11:46 pm

then nothing!!!
I dοn't and you probably dοn't develop OC.
But if the developers who support OpenCart consider it a multilingual program then they should fix this problem as well as some others related to translations which are however solved in indirect ways.
if for anything, we accept the "then what?" for an answer, nothing would develop.

"I dοn't and you probably dοn't develop OC. ", well, I do, a little...

Still, while I agree that multi-lingual support in OC has always been an afterthought and not consistently implemented in all corners, dealing with a "free of charge" software, when things are not as they should have been, the term "unacceptable" is rather unacceptable, that term should be reserved for when you actually paid for stuff.

@by mona
A developer and computer shop owner since 1991.

@nonnedelectari
I understand and accept what the free of charge means.
OpenCart is not a program that has been abandoned. It is a program that evolves and releases new versions. This means that those involved in this development and those of us who support it by using it for the online stores we build and buy add-ons from Marketplace, believe in it. Otherwise we would be dealing with WooCommerce or any other platforms. So when you move on and go to new versions and you are interested in having a competitive program, you cannot let unsolved simple and basic issues that have been known for many years. The same issue has been reported since at least 2017!!! That's why I wrote the unacceptable.
The OpenCart community is not only those who build it but also those who support it in many ways. Otherwise it would not have existed for so many years.

Happy New Year

leatherboy wrote: ↑

Mon Dec 30, 2024 9:11 pm

The same issue has been reported since at least 2017!!! That's why I wrote the unacceptable.

That doesn't sound good, but you could learn how to fix it and submit the code to OpenCart

The solution would be a modification which splits up the current 'oc_tax_rate' DB table into 2 tables:

oc_tax_rate
tax_rate_id
geo_zone_id
rate
type
date_added
date_modified

oc_tax_rate_description
tax_rate_id
language_id
name

And then modify any controller or model or library class using the tax rate.

JNeuhoff wrote: ↑

Tue Dec 31, 2024 7:35 pm

The solution would be a modification which splits up the current 'oc_tax_rate' DB table into 2 tables:

oc_tax_rate
tax_rate_id
geo_zone_id
rate
type
date_added
date_modified

oc_tax_rate_description
tax_rate_id
language_id
name

And then modify any controller or model or library class using the tax rate.

There are several tables which lack multilingual support, like geo_zones for shipping.

No need for extra tables if you want just translate the tax names. it can be translated from the tax function itself tax_name_eng = tax_name_fr (yes it will be hardcoded but hoe many taxes you may have:)? and it will solve your issue

D3MO wrote: ↑

Sun Jan 05, 2025 9:08 pm

No need for extra tables if you want just translate the tax names. it can be translated from the tax function itself tax_name_eng = tax_name_fr (yes it will be hardcoded but hoe many taxes you may have:)? and it will solve your issue

Hardcode languages to the rescue.

D3MO wrote: ↑

Sun Jan 05, 2025 9:08 pm

No need for extra tables if you want just translate the tax names. it can be translated from the tax function itself tax_name_eng = tax_name_fr (yes it will be hardcoded but hoe many taxes you may have:)? and it will solve your issue

.. but how many taxes you may have ..

Simply think of a webshop selling digital goods.
Only for the EU you will need at least currently 27 ..

And every tax name can be defined correctly when defining the tax rates.
Finally I do not really see a need to translate anything, because USt. is USt., MwSt. is MwSt., VAT is VAT, and PVA is PVA and so on ...

OSWorX wrote: ↑

Mon Jan 06, 2025 4:21 pm

D3MO wrote: ↑

Sun Jan 05, 2025 9:08 pm

No need for extra tables if you want just translate the tax names. it can be translated from the tax function itself tax_name_eng = tax_name_fr (yes it will be hardcoded but hoe many taxes you may have:)? and it will solve your issue

.. but how many taxes you may have ..

Simply think of a webshop selling digital goods.
Only for the EU you will need at least currently 27 ..

And every tax name can be defined correctly when defining the tax rates.
Finally I do not really see a need to translate anything, because USt. is USt., MwSt. is MwSt., VAT is VAT, and PVA is PVA and so on ...

Nop VAT is in my country PVM:) and if it shows wat it is obviosly english not translated to language. not all parts of the world using english as native:)

D3MO wrote: ↑

Mon Jan 06, 2025 4:56 pm

Nop VAT is in my country PVM ..

Whatever the local tax is called/named, it will have always the same name - regardless which language is used.
If it's PVM, then it will PVM.
If you're in Austria and Germany, it's called USt., in Switzerland they call it MwSt. .. and so on ..

My tax authority will refuse every invoice if I do not write the correct tax name on it.
So, translating is for the .. fishes .. (as we say it here .. means useless).