Category brand name is translate in module

  • Posts: 52
  • Thank you received: 4
  • Hikashop Multisite
4 years 3 months ago #327442

-- HikaShop version -- : HikaShop Business 4.3.0 [2007271529]
-- Joomla version -- : 3.9.23
-- PHP version -- : 7.4.13
-- Browser(s) name and version -- : Microsoft New Edge

I made module that will show all brandname below each other.

There is one brandname, named Comma, when show it on the screen it's translated to 'Komma'. I can't find where I can change this.

In the database table #__hikashop_category the catogory_name is Comma

As well in the hkashop backend as well in the frontend the name is translated to Komma.



This is not good. How can I solve this? Especial by multilanguage websites the brandname may never be translated.

Please help.

Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 83404
  • Thank you received: 13498
  • MODERATOR
4 years 3 months ago #327453

Hi,

Translations of category names and brand names can be made with translation overrides:
www.hikashop.com/download/languages.html#modify
"COMMA" is actually a translation key used by default in Hikashop language files:
COMMA="Comma"
So I would recommend to actually change the name of that brand to something else like "BRAND_COMMA" and then add a translation override like this:
BRAND_COMMA="Comma"
That way, you'll get the correct brand name.

Please Log in or Create an account to join the conversation.

  • Posts: 52
  • Thank you received: 4
  • Hikashop Multisite
4 years 3 months ago #327469

Hello Nicolas,

Thanks fot the answer.

It's a nice quick solution, but not very end-user-friendly. Would be nice if everything that cannot be translated starts with # notrans # and that that is removed during rendering. Eg # trans # Comma will eventually be displayed as Comma. Or even better if we could indicate that a category may or may not be translated.

Please Log in or Create an account to join the conversation.

  • Posts: 83404
  • Thank you received: 13498
  • MODERATOR
4 years 3 months ago #327487

Hi,

You mean that if a text starts with #notrans# we don't translate it ?
That could be something we could do in a future improvement yes.
That's quick and easy to add.
Having an extra option in each translatable element would be complex to handle as we would need extra options everywhere and checking these options throughout all the code base. So it's a lot of work, just for the rare case where a text would have already a translation you don't want to use, which can actually be circumvented quite easily with the solution I provided in my previous message or with a tag like you proposed.

Please Log in or Create an account to join the conversation.

  • Posts: 52
  • Thank you received: 4
  • Hikashop Multisite
4 years 3 months ago #327496

I think the tag-option is the most end-user-friendly. Would be nice to see this in the feature version.

The following user(s) said Thank You: nicolas

Please Log in or Create an account to join the conversation.

Time to create page: 0.053 seconds
Powered by Kunena Forum