All the wordings of VikBooking are language definitions that can be easily translated through the Joomla! .INI language files of the component and modules. Words like "Book Now", "Check-in", "Check-out" are language definitions while the name of the room is a Content that could not be translated through the language files.

Translations are used for both front site and Administrator section. All the language definitions for the extensions are located in the following directories:
/administrator/language/ (back-end, system)
/language/ (front-end, modules)

Unless you have a good text editor for editing .ini files, we recommend using our Online Translator. It will help you translate components and modules into other languages avoiding syntax errors.

Both the above directories contain sub-folders, one for each language installed on your Joomla. For example, a Joomla site with two languages installed, English and Spanish (from the Administrator section, Extensions - Language Manager we can see all the Languages installed), will have the folders en-GB and es-ES on those directories above. That is where the .ini language files are located.

With the .ini language files we can translate all the definitions of VikBooking and modules. View Details, Starting From, Book Now, Order Status, etc.. are examples of translatable definitions. If we wish to have these words translated in other languages, we have to translate them manually.

These are the steps to follow for creating a Spanish translation file, for example, of VikBooking:
1. Copy the file /language/en-GB/en-GB.com_vikbooking.ini into the folder /language/es-ES/
2. Rename the file as /language/es-ES/es-ES.com_vikbooking.ini
3. Open the file es-ES.com_vikbooking.ini and translate all the English definitions into Spanish
4. Save the changes and make sure the file is uploaded onto the right directory of the server.

The structure of the .INI language files has changed since Joomla 1.6 and now it reflects the standards of the .INI markup. Make sure to respect the syntax by opening and closing the quotes for each definition:

LANGKEY="Translated Text"

All the .ini language files should be saved with a proper encoding or some special characters will not be readable in the site. UTF-8 is the encoding your text-editor should apply.

Last Update: 2019-03-19 11:37
Helpful?
50% of people found this helpful.
This site uses cookies. By continuing to browse you accept their use. Further information