I had first problems with the German language file and needed to fix it. Post by ce » Sat Dec 10, pm I'm using the Norwegian language file. So, then I understand that all codes are located in the main language file.
If so, I'll check the English file and add the missing codes for the Norwegian hack. Thanks for your confirmation. If the English language file in Joomla is "english. Another question. Did you download from VirtueMart the language files, and uploaded them in the VirtueMart language directory?
Because I cannot find a Norwegian language file there. So if you have to create one, you will have to get the "english. Post by ce » Sat Dec 10, pm Thanks for the info Alex, I've checked my catalogue, there where no VirtualMart language files included in the Joomla package As far as I know there are no VirtualMart Norwegian language files available.
So, I suppose I have to take the hard way to translate one. Or in other words, it is the translation for normal text and messages for example login, cart, "product not found" and so on. You can use the language overrides to adjust them to your taste. This translation is selected in the joomla language manager. You can easily display your shop in 20 languages. Means that the content of any item is most time unique and has its own translation like the product description. Joomla handles this with an extra item per language, translations are associated to other entries.
VirtueMart uses a completly different system. It uses for any translateable item own language tables. Dynamically translateable fields are signed with a flag, when the editing language got changed. VirtueMart allows you to translate many form fields by adding a language key into the form field instead of a single language value string.
This is possible for all fields which are usually set up once in the store configuration. Examples for such fields are custom fields, shopper fields, etc. Be aware that the language keys of the plugins and the countries, even though they are shown in the front-end FE , are defined in the back-end BE.
Shopperfield and orderfield language keys are in the FE. Additional languages are named to reflect the language and stored in a language subfolder. If your shop used German as the default language or supported German as an additional language there would be a folder and files e.
Since Joomla! By storing extension language files in the extension folder, we gain the benefit of isolating and protecting our extension's language files. For example, if an administrator removes a language from the Joomla! Thanks, Mac. For example, I like my proposed version: " Check this box if your shipping address is the same as your billing address.
Thanks Kelvyn! It's en-GB. In any event, to avoid losing the new text I'll set up an override so that the files don't get changed via updates. Cheers, Mac. As described in the FAQ you must use overrides. Joomla's language override facility makes the override file for you. I'm with you, Kelvyn. Am I right in thinking that there are text values that aren't available in the en-GB.
Is there somewhere else I can look to make the needed changes?
0コメント