KM FasTrans User Manual

This User Manual contains information not available in the online help and in some cases also contains some of their support when the context so requires.

Please read this document before using the product and especially before asking for support, because if the question is answered in the document it will not get any response from the support group.

Version History

 Version  Date Modified/New Chapters
 Version 1.8 (KMFasTrans 3.0.0)  July 2014  Introduction, Installation
 Version 1.7 (KMFasTrans 2.3.0)  March 2014  Installation
 Version 1.6 (KMFasTrans 2.1.2)  October 2013  Configuration
 Version 1.5  August 2013  Introduction, Productivity Tools
 Version 1.4  March 2013  Introduction, Inconsistencies processing, Synchronization of items associations
 Version 1.3  September 2012  Installation
 Version 1.2  July 2012  Permissions Management
 Version 1.1  June 2012  Installation
 Version 1.0  April 2012  -

Contents

The contents of this manual is as follows:

Introduction. Contains an overview of product features and reference the chapter that describes them in greater detail.

Installation. It contains instructions on installing and uninstalling the product.

Configuration. Describes the available options to configure the product.

Permissions Management. This important chapter contains all the information needed to manage the permissions of the component and the language-specific permissions. His reading is required before setting these permissions.

Sets of Translations. This chapter describes how to create, delete and modify sets of translations.

Inconsistencies processing. This important chapter describes how to find and resolve inconsistencies in the translation process.

Synchronization of items associations. This chapter describes how to synchronize items associations between Joomla and KMFasTrans.

Management of Translation Items. Contains instructions and little tricks for creating and editing translations items.

Productivity Tools. Describes available productivity tools and how to use them.

 


Introduction

KMFasTrans is a tool that will help you in the translation tasks required to create a multilingual website in Joomla! using multilingual functions provided by Joomla! from version 1.7.1 onwards.

Increased ease of Management with Translation Sets

When you translate content into several languages in Joomla!, what you are doing is creating a different item for each language. Each item is assigned to a language and has the same content (translated) that another item in another language. For example, suppose you have a website with three languages, English, French and Spanish. For each content (category, menu, banner, article ..) you have to create three items, one for English, one for French and one for Spanish. And these three elements are related and have many things in common, and here is where KMFasTrans comes to help.

In KMFasTrans we created the concept of Set of Translations (or Translations Set). A Set of Translations is the set of items representing the same content in different languages. In the example above, if the items have the id's 10 for English, 23 for French and 31 for Spanish, you will have a Translations Set composed of items whose id's are 10, 23 and 31.

Each Translations Set has a number of attributes that are described in detail in section "Sets of Translations". One of the most important attributes is the Status, indicating whether they have done all the translations of the same content, whether or not they are all published, and if there have been any changes since the last publication.

To find translations already made and their status, you have the screen "Translations Dashboard" where all the information of all translations of a particular item or element type is in sight. From this screen you can make changes to the sets of translations, by assigning, unassigning or changing items of the Set, or changing the Set Status. You can also publish, unpublish or trash any of the items whether they are or not assigned to a Set. For a more detailed description see the Online KMFasTrans Dashboard Help.

Improved effectiveness and efficiency by cloning items, and filtering parameter values by language

Another aspect that KMFasTrans will help you enormously is on creating or editing translations items. First of all you must know that to create or edit a translation item with KMFasTrans, you must have created in advance, using the native Joomla!, one item (and preferably only one), whose language will be the 'From' (or source) language for the translation.

Following the previous example of a website in three languages, English, French and Spanish, the most efficient sequence of tasks would be to create the entire site first in one language, eg English, and then use KMFasTrans to translate each content (categories, articles, ...) into the other languages. You can do it in the sequence you want, but always bearing in mind that to create an item you need an existing item of the same type. The language of the existing item  will be used as the source language for the translation.

The most efficient sequence is: Categories, Articles, Menus, Banners, Contacts, Newsfeeds or Weblinks and then Menu items and Modules. 

When you create an item as a translation of another one using KMFasTrans, the new item created in one of the remaining languages inherit some attributes of the original item, such as the type. To facilitate the creation of the new item, KMFasTrans provides a facility to copy the item parameter values from the source item to the target item (ie, cloning the item). This function will copy all the values that are not language dependent. For example, if you are creating an article, its category will be different from that of the original article as it must be a category on the language in which you are creating the new article.

KMFasTrans will also help you in this task, because it will automatically filter all language-dependent values. In the above example, if you are creating a new article, the drop-down list of categories that the new article may belong to, will only show those that are in the same language in which you are creating the new article (or language '*' in this case). And the same applies to all drop-down lists. This way you do not have to worry about ensuring that an item is in a category of their own language, avoiding mistakes and wasted time.

This also occurs with parameters that are dependent on others. For example, if you are creating a menu item, by modifying the value of the menu location, automatically, without reloading the page, the values of the parent items will change to show only those relating to the new menu.

Improved effectiveness and efficiency with translations suggestions.

One of the characteristics that provide greater efficiency in the creation of translations is the use of known translations to populate the language-dependent fields. For example if you are translating a menu item of type 'Single Article' from English to French, and a French translation of the article is known (it was created erlier) , the 'Select Article' field in the French menu item will be automatically populated with the translation of the article into French. Thus saving the time to search the article and also avoiding possible mistakes. The same applies for any language-dependent field of any element type (articles, modules, menus, etc.).

Improved effectiveness and efficiency with automatic synchronization of items associations.

Another important aspect is the association of items. If you want (as usual) to view the translation of the current page when you switch the language in the front end, it is necessary that the menu item that leads to the page in one language, be associated with the menu item that leads to the page in the other language. When the number of languages or menu items is high, the manual association of each menu item, can be very time consuming. But with KMFasTrans this is done automatically. Each time you create a new item with KMFasTrans, automatically you associate the new menu item to those who belong to the same set of translations. No omissions or mistakes.

The same is true when you associate/dissociate elements to/from a set of translations, the Joomla item associations are also created or modified to reflect the changes in the set. And it also works in the opposite direction, changes made to Joomla item associations will be automatically reflected in KMFasTrans sets of translations.

There is also an option that allows you to launch a processs that will create, edit or delete sets of translations using the current Joomla menu associations and also the opposite, create, edit or delete Joomla item associations using the current sets of translations.

This feature allows you to have the associations fully synchronized with a very little effort.

Guaranteed quality of the multilanguage structure thanks to the consistency checking process

KMFasTrans PRO introduces a new concept in the process of translating a website that we have called 'inconsistencies'. The purpose of this feature is to detect potential mistakes that can occur when creating a multi-language site.
A website that does not contain inconsistencies provides the guarantee that all that has been translated is consistent and will have the same behavior in any language.

Improved effectiveness and efficiency with automatic translations.

KMFasTrans, also provides support for content translation using 'Bing Translator'. When creating or editing an item, you will see in certain fields of the edit form, a button "Translate". Pressing this button, the content of the field is populated with the translation of the content of the original field. For example, if you are translating the article with id = 10 in English to article with id = 20 in French, when you press "Translate" in the Title of the article with id = 20, the Title field of the article with id = 20 will be populated with the French translation of the Title of the article with id = 10. Although it is known that automatic translations are frequently quite poor, it is also true that they provide a basis on which to build the proper translation.

Article level switching.

Joomla 2.5 only provides menu item level switching. With KMFasTrans you can also have article (or contact or news feeds) level switching. You just have to publish our KMFT Language Switcher module.

Joomla 3.x provides article level switching, but if the language of your article (or the category to wich the article belongs) is 'All' then you still need the KMFT Language Switcher module because the native Joomla Language Switcher module does not switch elements whose language is 'All'.

If you need item level switching for elements of third-party extensions you can also get it with our KMFT Language Switcher module.

Third-party extensions support.

Since version 3.0.0, KMFasTrans supports all the above features for elements of third-party extensions. See 'Installing support for third-party extensions' in chapter 'Installation' to know how to get this support.

Improved effectiveness and efficiency with language specific permissions.

Last but not least, KMFasTrans, provides permissions to the language level. If you have different people doing translations into different languages, you can create groups of translators with limited access to certain languages. For example, a group of translators can handle the translation into French. The components of this group can see all the translations into other languages, but can only perform the actions that they are allowed in each language. 

All this will help you be more efficient in your translation tasks and maintain all your translations under absolute control.


Installation/Unistallation

Installation

KMFasTrans is composed of a component, a plugin and one or more modules. Installation is performed following the same procedure as the installation of any component, using the Joomla installer. When installing the component, the plugin and modules are also automatically installed without additional intervention.

From version 2.3.0 when you install KMFasTrans PRO for the first time or you upgrade to PRO from FREE, the installation process will autonatically create sets of translations based on existing Joomla associations. As this can be time consuming, especially in large websites with many items, you can override this process by modifying the installation file. Just open the php file named careate_sets.php in the root of the zip file and change 'YES' by 'NO' in the line "define('KMFT_CREATE_SETS', 'YES').

If you are installing for the first time, the installation process will check if the version of KMFasTrans to be installed is compatible with the version of Joomla, and if so, it will create all tables and data necessary for proper operation.

If it's an update, that is, it is not a first installation, KMFasTrans will keep all data as they were before the upgrade. The upgrade process checks, just like in the installation, if KMFasTrans version is compatible with the version of Joomla, and will also perform the following additional checks:

        • The version to be installed is equal to or higher than the installed version.
        • FREE version is not installed over PRO version.

If any of the above checks fails, the process aborts and displays an error message or a warning. The state existing prior to the installation or upgrade remains unchanged.

If you do not have InnoDB as storage engine atleas for table "menu_types" you will get the following error:

WARNING: You need to have the table option storage engine = InnoDB in MySQL at least in table "menu_types", otherwise the installation would fail. If your MySQL versión is 5.5.5 or higher this is the default. If it is lower you will have to do it manually. You can use PHPMyAdmin.

The way to correct this using PHPMyAdmin is as follow:

1 Open PHPMyAdmin and go to menu_types table.

2. Click Operations.

3. Select InnoDB as Storage Engine in the dropdown box

4. Click Go

The image below shows these steps:

phpmyadmin

When you change this option in the database the safest way to proceed is to uninstall the extension and install it again.

If you have installed KMFasTrans PRO under a Joomla version lower tha 2.5.4 you MUST disable the plugin option 'Language Permissions' BEFORE upgrading to Joomla 2.5.4 or higher. Otherwise the Joomla upgrade will finish in error. Once the Joomla upgrade has finished you should enable 'Language Permissions'.

If you had defined language permissions before the upgrade, such definitions will be maintained and made available again after the upgrade once you have enabled the option.

Installing support for third-party extensions

This functionality is only supported on KMFasTrans PRO - Joomla3.x. Subscribe now!.

For KMFasTrans to know third-party extensions you need to install the proper support plugin for each third-party extension you want to use. When installing the plugin, the Joomla, KMFasTrans and third-party extension versions are checked and if incorrect the plugin is not installed or is not enabled if already installed.

If the plugin installation is sucessful, all extension elements supported will be accessible on the filter - Select Element Type -. For example, once the plugin for K2 support is installed that filter will show the following:

K2 elements

Extension specific Modules and Menu Items will also be available when selecting J-Modules or J-Menu Items in the filter.

You can view the supported third-party extensions and their versions and download the support plugin inThird-party extensions support

Uninstallation

KMFasTrans is uninstalled just like any component, but you only need to uninstall the main KMFasTrans component. By doing so, the plugin and all modules will also be unsinstalled.

You should not uninstall the product unless you do not want to continue using it anymore, because the uninstall process will remove without notice all tables and all data, and can not be recovered.

Otherwise you must upgrade. That is, to upgrade from one version to a higher version FREE or PRO, or to upgrade from FREE to PRO.

Needless to say that you should make a backup copy of the website prior to any installation or uninstallation of the component.

Post-First Installation

After the first installation it is necessary to perform the following tasks:

    • Set the appropriate language in the existing menus.

When you install the product the field language is added as a required field for menus, so you can easily control the language of the menu-items associated with a menu. The installation process sets the value 'All' for the language in all existing menus, and you need to change it manually to get the right one.

To do this you must edit each existing menu using the standard Joomla menu edit form. The KMFasTrans plugin will introduce a drop-down list of languages where you must select the appropriate language for the menu.

The menus you create later with KMFasTrans as translations to existing menus will automatically have the language in wich they are created.

    • Establish multi-language "infrastructure" if does not exist yet.

This is done by clicking 'Create Default Home' button (or 'Create Multilingual Infraestructure' button) on the toolbar of the Content Languages Screen.

This "infrastructure" consists of the following:

    • A menu with title "Menu-All", menu type "defaultallmenu" and type "Category List".
    • A menu item with title "Menu Item-All" in the menu "Menu-All" as the default Home page for language "All".
    • A menu module with title "Menu Module-All" in the position "default_all_menu_module_position" (a fictitious one) linked to menu "Menu-All" and unpublished.
    • A category with title "Root Category-All-Articles" that is required for "Menu Item-All".

Each time this button is pressed, KM FasTrans will try to create these four items and will create only thouse that do not exist yet. You will be informed of the items that already existed and those just created. You can also know at any moment the status of these items in the control panel screen.

Once these four items are created, your site is ready for multilanguage. You don't have to use these items for anything ( and is better if you don't use them at all as if problems arise you could delete them and recreate pressing this button. An exception to this might be the category, which may be used freely if needed). If you need a menu, menu item and menu module assigned to language 'All' you can create as many as you need without changing anything of those four items that were created automatically.

If you already had this infrastructure in place before installing KM FasTrans, you can just ignore the warning messages, or you can click on the button anyway because it will not affect what you had previosly, the only change will be that the default home page for language 'All' will be the new automatically created menu item with title "Menu Item-All". You also can use the proper option to disable the warning message.

Remember to publish the Language Filter plugin. If you want to have translated content switching when switching languages you have to set the value 'YES' for the option "Menu associations". If you forget to do it at first then you will have to re-edit all menus to create associations.

If you want to switch content at the article, contact or newsfeed level, you have to publish the KMFT Language Switcher and assign the position and pages as you want. Remember that this module requires menu associations to be in place to work properly.

 


Configuration

You can configure the KMFasTrans selecting Components-> KM FasTrans-> Control Panel-> Options from top menu.

A modal window appears with several tabs:

KMFasTrans permissions configuration KMFasTrans permissions configuration

 

In all tabs except 'Translation options' the tips on the options texts clearly explain the purpose of each parameter.

The following describes the tab 'Translation options':

Here you can configure an automatic translation service from those available in the dropdown menu 'Translation service'. The Bing translator is the only one currently supported.

 

KMFasTrans translation options configuration KMFasTrans translation options configuration

 

Bing Translator Service

Bing Translator is a hosted service by Microsoft that provides language translation. This can be used within KMFasTrans PRO to suggest translations when creating or updating items.

At the time of writing you can subscribe to several plans based in the number of characters to translate per month. There is a free plan that allows translation up to 2 million characters per month.

Please note that Microsoft may change its plans at any time.

To use the translator you have to:

    • 1. Sign up for the service.
    • 2. Getting your Credentials.
    • 3. Configure KMFasTrans.

For the first two steps above you can follow the instructions on Signing up for Microsoft Translator on Windows Azure Marketplace or follow the step-by-step instructions below.

Step 1. Sign up for the service.

a). Visit https://datamarket.azure.com/dataset/bing/microsofttranslator to see the Microsoft Translator Offer page on Windows Azure Marketplace.

 

Windows Azure Marketplace Microsoft Translator

 

b). On the right hand side of the screen, you'll see a number of different monthly volume offers. Choose the one that meets your monthly volume usage needs. The free 2 million characters per month subscription offer, is at the top of the list.

c). Press the 'Sign Up' link on your chosen offer and you'll be taken to a page where you are asked to sign in using a Microsoft account. If you already have one, just sign in. If you don't, you'll have to create a new one.

 

Windows Azure Marketplace Sign in

 

d). After Sign in you'll be taken to a Registration page where you have to enter some data.

 

Windows Azure Marketplace Registration

 

e). Fill out your details, and press the 'Continue' button. You'll be taken to the Terms of Use page.

 

Windows Azure Marketplace Terms of Use

 

f). Read it carefully, and if you accept it, check the box at the bottom of the screen that says 'I accept the Terms of Use', and press the 'Register' button. You will be taken to the Sign up page.

 

Windows Azure Marketplace Sign Up

 

f). Check that you agree with 'Offer Terms and Privacy Policy' and click the 'Sign Up' button. This will complete Step 1.

 

Step 2. Getting your Credentials.

Visit https://datamarket.azure.com/developer/applications/register to be taken to the screen that allows you register your application.

 

Windows Azure Marketplace Register application

 

You use this to get the Client ID and Client Secret values that KMFasTrans needs to authenticate the service.

    • - Fill out the Client ID, and Name fields.
    • - The Client Secret field is already completed for you. Do not change it.
    • - Fill out the 'Redirect URI' field with any valid URL that uses https, for example https://microsoft.com. This field is not used by the Microsoft Translator.
    • - You can also leave the 'Enable subdomain access' checkbox unchecked, as the translator doesn't use it.

Remember and note the Client ID and Client Secret fields. You will need these to configure KMFasTrans.

Next, you'll be taken to a page containing the list of your applications. (Note: For future reference, here's a shortcut: https://datamarket.azure.com/developer/applications).

Step 3. Configure KMFasTrans.

Fill in the following options in the 'Translation options' tab with the data from Step 2:

    • Translation service: Bing translator.
    • Bing translator Client ID: The Client ID supplied in Step 2.
    • Bing translator Client Secret: The Client Secret obtained in Step 2 (Copy and Paste).

Translation tags option:

This option is valid for all translation services.

Using this option you can choose to perform a special process for the translation of texts contained between the choosed characters. If for example you choose '{ }', that indicates that all the content between the opening tag '{' and the closing tag '}' will be subject to a special translation process. You can choose none, one or several options from the drop down menu.In the current version the only special process available is 'No translation', which means that the original value is preserved after translation.

 


Permissions Management

KMFasTrans supports the management of native Joomla permissions and also introduces a new layer of language-level permissions. Thus, the actions permitted to a user on languages and elements of a language will be divided into two main categories:

A. Language Permissions

These are the com_languages component permissions but are managed within KMFasTrans. They affect the management of languages only, ie Installed Site Languages, Installed Administrator languages, Content Languages and Overrides. You can allow or deny management of languages for a user group. If you deny, the users of that group will not have access to these functions. Actually they will not see the links neither in KMFasTrans submenus nor in pages.

A new button 'Language Manager Options' has been added to the Control Panel toolbar to configure the 'Language Permissions'. 

B. Translations Permissions

These are permissions to create, delete, edit, edit state or edit own of translations elements and are a combination of the following levels of permissions:

      • 1. KMFasTrans component permissions. These are the highest priority translations permissions. If an action (such as editing the state) is denied in KMFasTrans it will can not be taken at any level.
      • 2. The permissions of the Element-Component. This refers to the component that contains the items being treated. For example com_content if we are creating or editing an article, or com_banners if we are editing or creating a banner.
      • 3. The permissions of an specific language. For example, you can not edit an article or any other item in English if you have not edit permission for English language.

Permissions of of an specific language are only supported on KMFasTrans PRO. Subscribe now!..

      • 4. The permissions of a particular item. It applies to articles or categories. You can not edit a particular article if you do not have permission to edit this article.

Using these two categories and four levels of permissions you will have great flexibility in determining what a translator can do. You can deny all administration permissions for all components except KMFasTrans, only allowing users to create new translations or edit existing ones. In terms of security this is similar to creating translations from the front-end.

For example you could set up a group of translators who only are allowed to translate banners to the French language, and unable to publish or unpublish the banners they create. To do this you have to:

    • Allow Access Administration Interface to this group in KMFasTrans Options.
    • Deny Access Administration Interface to this group in Language Manager Options of KMFasTrans.
    • Deny Delete, Edit and Edit State to this group for every language except French in KMFasTrans Content Languages.
    • Deny Access Administration Interface to this group in every component including com_banners.
    • Deny Create, Delete, Edit, Edit State, Edit Own in every component except com_banners.
    • Allow Create, Delete, Edit and deny Edit State in com_banners.

When a user of this group access the administration it will see one screen similar to the following one:

 

KMFasTrans permissions only

 In the above image you can see several things:

1. The user only has access to the component KMFasTrans, within it, only to Control Panel and Translations Management Dashboard. He is not allowed to manage languages because the Access Administration Interface has been denied.

2. The element types he can select in the - Select Element Type - dropdown list are Categories and Banners only (Banners is selected in the image). 

3. In the listing you can see that all languages except French are in gray, ie nothing can be changed.

3. The status in the column Frances (FR) is also in gray because we have denied Edit State for this users.

 

With respect to Translations Permissions, if you do not have permission to take a certain action, you can not click on the text or image that enables the action. Furthermore, in order to recognize that you do not have permissions, the text or image will appear in gray and in most cases by placing the mouse over the text or the image, an explanatory text will be shown.

To assign permissions to users, you must create one or more user groups and assign each of them the desired permissions.

How to create a group could be as follows:

a). Go to Users-> Group-> Add new group.
b). Set as Group Title: "Translators".
c). Set as Parent Group: "Manager".
d). Save and go to Users-> Access Levels-> New Access Level.
e). Set as Title Level "Translations" and check the "Translators" checkbox.
f). Go to Components-> KM FasTrans PRO-> Control Panel and click Options on the toolbar.
g). In the Permissions tab and in the group Translators, the Action 'Configure' should be 'Denied' and the Action 'Access Administrator Interface' must be 'Allowed'. The remaining actions, 'Create', 'Delete', 'Edit' and 'Edit State must be configured as appropriate for the user group that is being defined.
h). Click 'Save' and make sure that the settings are correct.

If you want to allow or deny language permissions for this group you have to access tha Language Permission screen:

a). Go to Components-> KM FasTrans PRO-> Control Panel and click Language Manager Options on the toolbar.

The Language Manager Options screen will open and you can configure the permissions of the grupo in the Joomla Language Manager standard way.

Now you can register a user belonging to the group 'Translators' and access to the Joomla Administration. With this basic configuration the user can do all that was allowed in each component. You can refine the group permissions by setting the desired options in each component.

Then, if you want to, you can set permissions for each language for that user group. To see in detail how to do this see KM FasTrans New/Edit Content Languages Help.

Setting Language Permissions.

Language Permissions are set from within KMFasTrans. If allowed, you simply need to click on the 'Language Manager Options' button on the right side of the toolbar of any screen except editing. After clicking on the 'Permissions' tab, the standard Joomla permissions management screen will be displayed.

Setting permissions of KMFasTrans.

KMFasTrans permissions are configured as those of any component. If allowed, you simply need to click on the 'Options' button on the right side of the toolbar of the Control Panel or Translations Management Dashboard screens. After clicking on the 'Permissions' tab, the standard Joomla permissions management screen will be displayed.

Setting permissions of a particular language.

This functionality is only supported on KMFasTrans PRO. Subscribe now!..

Permissions of a particular or specific language is an important feature of KMFasTrans PRO. This allows users groups access to different sets of languages. Permissions for a particular language are set as follows:

If allowed, on the 'Content Languages' Screen click on the title of the language or enable the CheckBox and click Edit in the toolbar. This opens a window where you can select one or more user groups (previously created).

For each user group you can set the following permissions:

    • Delete
    • Edit
    • Edit state

Setting Language Permissions has the following effects on the operation of KMFasTrans:

Language Component Permissions Effects in Installed languages Effects in Content languages Effects in specific Content Language Effects in Overrides Effects in Translations
Access Create Delete Edit EditState
N - - - - No access No access No access No access No effect
Y N N N N All actions denied All actions denied All actions denied All actions denied No effect
Y Y - - - No effect Can create a language.
Can create Default Home elements.
All actions denied Can create an override No effect
Y - Y - - No effect Can empty trash of any trashed language (*). Can empty trash of any trashed language (*). Can delete an override No effect
Y - - Y - No effect Can edit any language (*) Can edit language (*) Can edit an override No effect
Y - - - Y Can change default language for any language Can publish, unpublish, trash and untrash any language (*) Can publish, unpublish, trash and untrash any language (*) No effect No effect

(*) Subject to language specific permissions 

 

Setting KMFasTrans Component Permissions has the following effects on the operation of KMFasTrans:

KMFasTrans Component Permissions

Effects in languages

(Installed, Content, Overrides)

Effects in Translations Dashboard Effects in Translations Edit or Create Component Access
Access Create Delete Edit EditState
N - - - - No effect No access No access No effect
Y N N N N No effect All actions denied. Can see elements in read only mode All actions denied. Can see elements in read only mode No effect
Y Y - - - No effect Can assign translation Items for any language (*)&(**) Can create new Items  (*)&(**) No effect
Y - Y - - No effect Can unassign translation Items for any language (*)&(**) No effect No effect
Y - - Y - No effect Can access translation Items for editing (*)&(**)&(***).
Can change translation Iitems (*)&(**).
Can edit translation Items (except status) (*)&(**)&(***) No effect
Y - - - Y >No effect Can publish, unpublish and trash translation Items (*)&(**)&(***) No effect No effect

(*) Subject to language specific permissions

(**) Subject to Component-Element permissions

(***) Subject to Item permissions

Setting Element-Component Permissions has the following effects on the operation of KMFasTrans:

Element-Component Permissions

Effects in languages

(Installed, Content, Overrides)

Effects in Translations Dashboard Effects in Translations Edit or Create
Access Create Delete Edit EditState EditOwn
N - - - - - No effect Will not show the element type in the Element Type drop-down list No access
Y N N N N N No effect Can not change Item (Id)  status
Can not change Set status.
Can not assign translation Items
Can not unassign translation Items
Can not change translation Items
Can see any Item
Can not edit any Item
Can not create new Item
Y Y N N N N No effect Can assign translation Items for any language (*) Can create new items  (*)
Y N Y N N N No effect Can unassign translation Items for any language (*) No access
Y N N Y N N No effect Can access translation Items for editing (*)&(***) Can edit translation Items  (*)&(***)
Y N N N Y N No effect Can publish and unpublish translation Items in any language (*)&(***) No access
Y N N N N Y No effect Can edit the own Items only.  Can edit the own Items only. 

(*) Subject to language specific permissions

(***) Subject to Item permissions 

Setting particular Language Permissions has the following effects on the operation of KMFasTrans: 

Language Specific Permissions

Effects in languages

(Installed, Overrides)

Effects in Content languages Effects in Translations Dashboard Effects in Translations Edit or Create
Delete Edit EditState
N N N No effect All actions denied for the language. All language specific actions denied No access
Y N N No effect Can delete the language. Can unassign translation Items of the language (***) No acces
N Y N No effect Can edit the language. Can edit translation Items of the language(***) Can edit translation Items of the language (***)
N N Y No effect Can edit state of the language. Can publish, unpublish and trash translation Items of the language (***) No access

 (***) Subject to Item permissions 

Setting Item Permissions has the following effects on the operation of KMFasTrans:

Item Permissions Effects in Installed languages Effects in Content languages Effects in specific Content Language Effects in Translations Dashboard Effects in Translations Edit or Create
Delete Edit EditState
N N N No effect No effect No effect Can not assign, unassign, change, publish, unpublish or edit the Item No access
Y - - No effect No effect No effect Can unassign the Item No effect
- Y - No effect No effect No effect Can edit and change Item Can edit this Item
- - Y No effect No effect No effect Can publish, unpublish and trash the Item Can publish, unpublish and trash the Item

 Applies to: Articles and Categories

 


Sets of Translations

As stated in the Introduction, when you translate content into several languages in Joomla!, what you are doing is creating a different item for each language. Each item is assigned to a language and has the same content (translated) that another item in another language. For example, suppose you have a website with three languages, English, Spanish and French. For each content (category, menu, banner, article ..) you have to create three items, one for English, one for Spanish and one for French. And these three elements are related and have many things in common.

In KMFasTrans we have created the concept of Set of Translations (or Translations Set). A Set of Translations is the set of items representing the same content in different languages. In the example above, if the items have the id's 6 for English and 84 for Spanish, we will have a Translations Set composed of 2 items whose id's are 6 and 84. The figure below shows what we will see at the Translations Dashboard Screen:

um set of translations 1

As you can see in the figure there is a row for the id 6 with title "Australian Parks". There are also several columns, which contain information of the items in English, Spanish and others, and the first one contains the information of the set of translations.

(For a detailed explanation visit KM FasTrans Translations Dashboard Help).

Hovering over each of the icons contained in these language columns you will see an explanatory text about its content and where appropriate a description of the action that will be taken when you press that id or image.

For example, if you hover over the edit icon of English column you would see:

um set of translations 2

If you hover over the two arrows icon in Spanish language you would see:

um set of translations 3

and so on.

Translation Set column

The Translation Set column shows two attributes, the Set Number and the Set Status.

The Set Number is a number assigned by KMFasTrans when creating the set of translations. It is a unique number for the entire web site and can not be changed. If you delete a set of translations, its number will not be reused.

The Set Status indicates the current status of the set of translations and is identified by an image and (hovering over the image) a text is displayed as follows:

    • Status: Not completed.

um set of translations 4

This state has two possible causes:

    • The set of translations lacks at least one translation id for some of the published content languages.
    • Not all id's of the set are published (This depends on the value of the option "Include published elements only for "Completion" of a Translations Set").
    • Status: Completed.

um set of translations 5

 

The set of translations has been completed when it contains as many translation id's as published content languages, and also all such id's are published (This depends on the value of the option "Include published elements only for "Completion" of a Translations Set"). As you can see in the example above, when you hover over the status image, the status and the completion date and time will be shown.

Each time you change the status of any id of the set to "Unpublished" or "Trashed", the set status will change to "Not Completed" regardless of the status it had before(depending on the value of the option mentioned above). When changing the status of an id of the set to "Published", the set status will change to "Completed" if it contains as many id's as published content languages and all of them are published(depending on the value of the option mentioned above).

Warning: from version 1.4.0 a set will not be allowed to contain an id assigned to language 'All', since by definition if an id is assigned to language 'All' it will be shown on all pages, and thus not required to be translated. For example, the module containing the login form will normally be assigned to language 'All', since the translation into every language is automatic using the standard language files of Joomla.

    • Status: Modified.

This functionality is only supported on KMFasTrans PRO. Subscribe now!.

um set of translations 6

 

The status "Modified" means that after completing the set of translations, at least some element of the set has been modified using the KMFasTrans edit form or the native Joomla editing form or the front-end editing form.
If the change is permanent, you can change the set status to "Completed" by clicking the Set Status icon.

If you changed the status of the modified id to unpublished, by changing its status to published, the set status will also change to "Completed"(depending on the value of the option mentioned above).

Creating a Translations Set

When you start to use KMFasTrans there are no set of translations. For example you could begin to translate the id 67 of the following figure:

um set of translations 7  

A set of translations can be created in two ways:

    • Manually

In the example in the figure above, to manually create a set of translations that contains for example the ID 67 in English and an ID in Spanish, you need to have previously created an ID in Spanish that is the translation of the ID 67 in English. Suppose you already have it and that its ID is 141. To create the set of translations you only have to click the link icon in the column Español (ES) and the following screen will display:

 um set of translations 8

Warning: the drop down list "Select Association:" must be set to "Not associated" to show only items that do not belong to any other set of translations. If you choose the value "Any", the list will contain all items in that language, whether or not they belong to another set of translations. In this case for each associated item you will see an association icon in the column 'Association' and you can see its associations by hovering over the icon. If you choose an item that already belongs to another set, such item will be disassociated from that set and associated to the set you are creating or updating.

By clicking on the title of the item you want, a set of translations will be created containing the two elements, 58 and 141. The Translations Dashboard screen will now show as follows:

um set of translations 9

As you can see, the set of translations just created has the number 165 and it is "Not Completed" because there are no translation into the other languages.

    • Automatically

This functionality is only supported on KMFasTrans PRO. Subscribe now!.

A set of translations is created automatically when you create a new item as a translation of another one using KMFasTrans New / Edit Translations form and there is no already a set.(If the set already exists it will be updated by assigning to it the new item just created).

You only have to click the create icon in the column whose language is the one in which you want to create the new item that is the translation into that language of the item in the row.

For example, in the above figure you can see that there is no translation into Italian of the Item with ID = 67 titled "Utility Modules". By clicking the edit icon in the column "Italiano", the following screen will be displayed:

(For a detailed description of the use of the edit screen visit KMFasTrans New / Edit Translations Help).

 um set of translations 11

On this screen fill all required fields to create the new item using the aids provided (such as the Translate and the Copy buttons). When you are ready, click any of the buttons "Save", "Save & Close" or "Save & Next", and at that time, in addition to creating the new item, it will also be created the set of translations if did not exist, or in the case of the example, the existing set (number 165) will be updated with the new Item just created. 

If everythig went correctly, the Translations Dashboard screen will now show as follows:

um set of translations 12

You can see that there's a new item in Italian language, whose ID is 143.

Deleting a Translations Set

A Translations Set is deleted when you unassign the second last translation item. By eliminating the set, the last two elements of the set will stay but not assigned to any set, ie not associated.

In addition to delete a set manually as described, a set of translations can also be deleted automatically when you change the language on an item in the KMFasTrans New / Edit form under certain conditions. For more details see the section "Language field" in KMFasTrans New / Edit Translations Items Help.

Modifiying a Translations Set

The set of translations is modified each time you change one of the items it contains. It is also modified when you associate or disassociate an item. Associating an item to a Set is performed in the same way as described in the preceding paragraph "Creating a Translations Set". To disassociate an item from the Set, just click on the broken link icon in the language column that contains the item you want to disassociate. Before dissociating the item you will see a confirmation screen.

Translations Set Details

By clicking on the Set Number you will see the details of its content as shown below:

um set of translations 10

The first five lines show attributes of the Translations Set:

    • Created on:

Date and time when the set of translations was created.

    • Current status:

Current status of the set. The set is usually created in status "Not Completed". It can be created in status "Completed" if there are only two languages.

    • Last status change: self-explanatory
    • Last action taken:

It can be Assign, Unassign or Modification of an Item.

    • Last element modification:

Indicates who, when and which item was last modified.

The list below the first five lines contains the elements of the set. The values for the columns are self explanatory.

 


Inconsistencies processing

Inconsistencies processing is only supported on KMFasTrans PRO. Subscribe now!..

In version 1.4.0 of KMFasTrans PRO we introduce a new concept in the process of translating a website that we have called 'inconsistencies'. The purpose of this new feature is to detect potential mistakes that can occur when creating a multi-language site.

We say that an element is inconsistent when one of its parameters is not consistent in the context of the element. For example, an article in English language whose category is in Spanish.

As discussed later, there are two types of inconsistencies that we call 'self' inconsistencies and 'translation' inconsistencies.

Translation Inconsistencies are always detected in relation to the source of the translation. For example if the item Art1-GB in English belongs to the category Cat1-GB in English and the translation of Art1-GB into Spanish is Art1-ES, then the category Cat1-ES of Art1-ES must be the translation into Spanish of the category Cat1-GB. If it is not or does not exist, Art1-ES has a translation inconsistency. To detect this inconsistency Art1-ES is analyzed with regard to Art1-GB which in this case is the source of the translation.

Thus it is necessary to have a reliable source with respect to which perform the detection of inconsistencies. This reliable source is one of the content languages defined in the site that we have called the 'Reference Language for detecting inconsistencies'. The reference language is selected on the screen that displays the content languages.

For the reference language to be reliable it shall not contain inconsistent items (items with self-inconsistencies) because if an item has inconsistencies and is used as a translation source it will transfer its inconsistencies to the translated element. Since the reference language is the reference for translations into other languages, by definition the elements in the reference language can not have translation inconsistencies, only self-inconsistencies.

Although it is necessary to define a reference language is still possible to make translations from any language to any language because the detection of inconsistencies will check that the source item of the translation is not inconsistent, preventing the translation to occur if it is.

As expected, the detection of inconsistencies is costly in terms of database access. Depending on the size and number of languages on the site you may want to disable the continued detection of inconsistencies while building a new language and enable it when it has been finished or is about to finish in order to find all the inconsistencies in one detection cycle. A component option is available to enable or disable the detection of inconsistencies.

You may also want to disable the detection of inconsistencies if greater freedom to make the translations is desired. The detection of inconsistencies is preventive, preventing certain actions that if taken would create an inconsistency. For example creating a set of translations that lacks an element in the reference language, or creating a translation from a source element that has inconsistencies.

If inconsistencies detection is enabled, inconsistencies will been calculated when editing any element and the result will be displayed in the editing screen. Inconsistencies may also be calculated for all elements in a process we call 'Verify' of inconsistencies.

With the detection of inconsistencies enabled the Translations Dashboard screen will show the current reference language and will signal all items that contain inconsistencies. (See the screenshots of the Translations Dashboard below).

Our advice is to keep enabled the detection of inconsistencies because it helps to find mistakes in the multi-language structure. A website that does not contain inconsistencies provides the guarantee that all that has been translated is consistent and it is going to have the same behavior in any language.

Selecting the Reference Language

As mentioned above it is necessary to select a reference language for the detection of inconsistencies. When you install version 1.4.0 for the first time KMFasTrans will choose the default site language as the reference language if it is also a content language. If it wasn't a content language, the first content language found will be used. If there weren't content languages configured the detection of inconsistencies will be disabled.

The reference language is chosen in the content languages management screen:

Selecting a reference language

To choose a reference language just click on the desired language in the 'Incons.Reference' column (this column is only visible if the detection of inconsistencies is enabled).

When changing the reference language it is necessary to verify self inconsistencies for the new reference language and translation inconsistencies for all the components.

Self Inconsistencies

Self-inconsistencies are those that an element has in itself regardless of whether or not it is translation of another element. The example given above of an article whose category is of a different language to the article is a self-inconsistency. This kind of inconsistency is detected when editing an item in the reference language and the source and destination elements are the same, or when editing an item in a language other than the language of reference and the item is not associated with any other (it does not belong to any set of translations).

Types of self inconsistencies:

    • 1. The language of a field element does not match the language of the element that contains it. For example the parent category of a category must always be in the same language as the category.

Self inconsistency type one

 

    • 2. The language of a parameter does not match the language of the element that contains it nor is it equal to the language '*'.

For example the category of an item has to be in the same language as the language of the article or in the language '*'.

Self inconsistency type two

 

    • 3. The menu of a menu item in a specific language different from the language '*' is not in that specific language.

Self inconsistency type three

 

This inconsistency is also detected as a self-inconsistency in the menu if the menu is in the reference language or it is not associated, as shown in the image below.

Self inconsistency type three in the menu

The main function of detecting self-inconsistencies is to provide a reliable source of translations. Thus its main application is the detection of self-inconsistencies of the chosen reference language.

The self inconsistencies are detected in two ways:

    • 1. When creating or editing a translation the detection of self-inconsistencies is performed on the item that is in the reference language because if this does not have self inconsistencies either the translation will. If it has self inconsistencies the only allowed action will be the edition of that item (the one in the reference language). If the item is associated (belongs to a set of translations) you won't be allowed to edit any other element of the set or create new translations until the self-inconsistencies of the element in the reference language are removed. If an item is not in the reference language and it is not associated, its self-inconsistencies will also be detected and displayed.

To remove the self-inconsistencies of an item you have to edit it and for it, its ID must be in the column with header 'ID' of the Translations Dashboard. This is achieved by entering its ID or title in the filter 'Filter Title, or Set Id' or selecting its language in the filter '-Select "From" Language-' and clicking the edit icon in the column of its language .

    • 2. Manually at any time you can launch a process that detects the self-inconsistencies of a particular language. It is appropiate to use it for detecting the self-inconsistencies of the reference language as the self-inconsistencies of the other languages (if any) are going to be resolved when its translation inconsistencies (if any) are resolved. This process is launched from the screen displayed when clicking the icon 'Verify Incons' of the Translations Management Dashboard toolbar.

Translation Inconsistencies

Translation inconsistencies are those that an element has in relation to another that is its source of translation. For example a menu item in Spanish language(MI1-ES) showing an article in Spanish language (Art1-ES) is inconsistent if the article in Spanish language is not the translation of the article in English language that shows the menu item source of the translation. The figure below explains the example:

Example of translation inconsistency

If item Art1-ES was not the translation into Spanish of Article Art1-GB, then the menu item MI1-ES would be inconsistent with an inconsistency of translation.

Remember that in KMFasTrans article Art1-ES is the translation into Spanish of the article Art1-GB if both articles are associated, ie if they belong to the same set of translations.

Types of translation inconsistencies:

The types of translations inconsistencies refer to the element source of the translation, the element destination of the translation and each of the fields of those elements that can have inconsistencies.

If an inconsistency is detected when editing or creating an item, the following information is displayed:

Translation inconsistencies info

First of all a warning message: "Translations inconsistencies ...." is displayed with a link to get more information and to take some actions directly. (We'll see this screen in more detail later on). For ease and convenience that same link is also available on the Info & Actions column in each inconsistency row.

Secondly the currently selected language as the language of reference is showed. In the example it is English(UK).

Thirdly the source element of the translation is showed. In the example it is an article whose title is 'Content' and its id is 10. In this case it matches the element shown below as the translation source (lefthand side) but is not so in all cases. For example, if the source element, and the target element are the same then:

    • If the language is the language of reference only self-inconsistencies will be shown and then there won't be any element source of translation.
    • If the language is not the language of reference then it will show translation inconsistencies relative to the source of the translation. This source will be the associated item (in the same set) whose language is the language of reference. If the item being edited is not associated (ie, does not belong to any set) then it will show only its self- inconsistencies and then there won't be any element source of translation.

Fourthly you have the translated item, in this case an article titled 'Contenido' with id:82. This is always the element that appears as the destination of a translation on the right hand side of the screen.

Following is a table with several fields:

Inconsistent Field: is the field detected as inconsistent on the target element relative to the source element. It has two subfields, the 'Fieldset' and the 'Field'. These allow you to identify the field among those that are listed below in the editing form.

Field values in the Source Element: contains the values of the field in the source element that led to an inconsistency in the target element. In the example these are the values of the field 'Category' in the fieldset 'Edit Article' of the article titled 'Content' with ID: 10. The values for this field are:

    • ID: The ID of the selected item in the field. In this example it is a category whose ID is 21.
    • Title: The title of the selected item in the field. In this case, 'Components', which is the title of the category with ID 21
    • Language: The language of the category 'Components'
    • Status: The status of the item in the field. In this case the item is selected in the field.

Field values in the Translated Element: contains the field values in the target element that constitute an inconsistency relative to the source element. In the example these are the values of the field 'Category' in the fieldset 'Edit Article' of the article titled 'Contenido' with ID: 82. Values for this field are:

    • ID:It is the id of the element that should be selected in the 'Category' field. In the example the ID is zero because the inconsistency is 'No translation found' indicating that a translation into Spanish for the category 'Components' with ID: 21 was not found.
    • Title: Is the title of the item that should be selected in the field. In this case is blank because as it happens with the ID the translation was not found.
    • Language: The language of the category that should be selected in the 'Category' field. In the example is blank because as it happens with the ID the translation was not found.
    • Inconsistency: The inconsistency found.

In this example it is interesting to note that the categpry selected in the target element is 'Componentes', which at first sight seems to be the Spanish translation for the category 'Components'. And indeed it is the translation in this case, but the process has not detected it because the category 'Componentes' is not associated with the category 'Components', ie they aren't in the same set of translations. Thus in this example the inconsistency is resolved by simply associating both categories.

Now we will describe the types of inconsistencies that can be found:

    • 1. Selected – No translation found

This is the case explained above. If the element that it is the translation of field in the source element into the target language exists but it is not known because it is not associated (not in the same set of translations that the source), the inconsistency is resolved by associating the two. If the translation of the field does not exist it must be created. The fastest way to associate the items or create a new translation from this screen is by clicking the link found in the warning message at the top of the screen or in the column Info & Actions in the inconsistency row. The screen obtained when clicking that link is as follows:

Selected - No translation found

 

This inconsistency usually appears with some frequency when creating a new element translation if you forgot to previously translate some of the fields you were going to need. For example when translating an article from English to Spanish without having previously translated the category. In the example would be enough to click on the icon Create link (association) to associate 'Components' with 'Composants'.

 

    • 2. Selected – Not selected

Selected - Not selected

 

This inconsistency indicates that a translation of the field in the source element was found but that translation is not selected in the target element. In the example, the category 'Componentes' (ID: 84) is the Spanish translation of the category 'Components' (ID: 21) but it is not selected in the 'Category' field of the article 'Contenido' (ID: 82) .

This inconsistency is resolved by selecting the translation of the element in the destination field. In the example, selecting the category 'Componentes' for the article 'Contenido'.

The screen obtained when clicking the link on the warning message at the top of the screen or in the column Info & Actions in the inconsistency row is as follows:

Selected - Not selected second screen

 

    • 3. Selected – Trashed

This inconsistency is only detected when the component option "Detect inconsistencies for trashed elements" is set to 'Yes'

Selected - Trashed

 

Indicates that the translation of the field in the source element was found and that it is selected in the target element but it is in the trash. The inconsistency is resolved by removing the translation from the trash or by creating a new translation of the field in the source element. Again the quickest way to resolve the inconsistency is by clicking the link on the warning message at the top of the screen or in the column Info & Actions in the inconsistency row. The screen obtained when clicking that link is as follows:

Selected - Trashed second screen

 

    • 4. Selected – Archived

This inconsistency is only detected when the component option "Detect inconsistencies for archived elements" is set to 'Yes'

Selected - Archived

 

Indicates that the translation of the field in the source element was found and that it is selected in the target element but it is archived. The inconsistency is resolved by unarchiving the translation or by creating a new translation of the source field. Again the quickest way to resolve the inconsistency is by clicking the link on the warning message at the top of the screen or in the column Info & Actions in the inconsistency row. The screen obtained when clicking that link is as follows:

Selected - Archived second screen

 

    • 5. No translation found – Selected

This inconsistency usually appears when the field is a multiple choice field and there is an element selected in the target (or translated element) for which no translation into the language of the source element has been found.

No translation found – Selected

 

In the example the category 'Productores' is selected in the Basic Options fieldset of the translated element (in Spanish language) and the process has not found an English translation of that category. In the source element we can see that there is a non selected category titled 'Growers' that looks like it is the English translation of 'Productores'. The process probably has not found it because it is not associated with 'Productores' (not in the same set of translations). The inconsistency is resolved either associating 'Growers' with 'Productores' on the same set of translations if indeed both are translations of each other, or by creating a new translation.

Possible actions to be taken are described in the information displayed on the screen obtained by clicking on the link in the warning message at the top of the screen or in the column Info & Actions in the inconsistency row:

No translation found – Selected second screen

 

    • 6. Not selected – Selected

This case is very similar to the previous one except that the process has found that 'Productores' is the Spanish translation of 'Growers', but nevertheless 'Growers' is not selected in the source element.

Possible actions to be taken are described in the information displayed on the screen obtained by clicking on the link in the warning message at the top of the screen or in the column Info & Actions in the inconsistency row:

Not selected – Selected

 

    • 7. Trashed – Selected

This inconsistency is only detected when the component option "Detect inconsistencies for trashed elements" is set to 'Yes'

Appears when the field is a multiple choice field and an item is selected in the source element for which a translation into the target element has been found and is selected but the element selected in the field of the source element is in the trash. Being in the trash it can not be seen as a selectable option in the field of the source element.

Possible actions to be taken are described in the information displayed on the screen obtained by clicking on the link in the warning message at the top of the screen or in the column Info & Actions in the inconsistency row:

Trashed – Selected

 

    • 8. Archived – Selected

This inconsistency is only detected when the component option "Detect inconsistencies for archived elements" is set to 'Yes'

It is very similar to the previous one when the item is archived.

Possible actions to be taken are described in the information displayed on the screen obtained by clicking on the link in the warning message at the top of the screen or in the column Info & Actions in the inconsistency row:

Archived – Selected

 

    • 9. Selected – Not equal to the source

Indicates that the field value in the source element is not equal to the field value in the translated element and they should be equal. An example is the translation of a menu item whose type must match the type of the source menu item:

Selected – Not equal to the source

 

As seen in the figure the field 'Menu Item Type' contains 'Single Article' in the source element and the same field in the target element contains 'List All Categories'. If associations be created using always KMFasTrans this wouldn't be the case because KMFasTrans don't allow it to occur. But since there is an automatic synchronization among Joomla menu items associations and KMFasTrans menu items associations it is possible to do a wrong menu items association in Joomla and transfer the error to KMFasTrans.

 

All inconsistencies described above are also displayed when editing items using the native editor in Joomla administration area as shown by the following examples:

    • 1. Self inconsistency example

Self inconsistency example

 

    • 2. Translation inconsistency example

In this example it is interesting to note that the source element with ID: 275 is not visible on the screen because it is the element in the reference language that is associated with the one visible (ID: 757).

Translation inconsistency example

 

The first inconsistency indicates that the source element (ID: 275) is set to the value 'About Joomla' as the 'Menu Location' in fieldset 'Details', and a translation of 'About Joomla' into Spanish has been found titled 'Acerca de Joomla' (ID: 9), but the translation is not selected as the 'Menu Location' in the target element (ID: 757).

The second inconsistency indicates that the source element (ID: 275) is set to the value 'Contact Component' as 'Parent Item' in fieldset 'Details', and a translation of 'Contact Component' into Spanish has been found titled 'Componente de Contactos' (ID: 755), but the translation is not selected as 'Parent item' in the target element (ID: 757).

 

Inconsistencies of articles are also displayed when editing articles in the front-end as shown in the following example:

Translation inconsistencies in the front-end

 

As in the previous example the source element is the element in the reference language (ID: 25) which is not visible on the screen. The inconsistency indicates that the category of the source element, the article 'Koala' (ID:25), is 'Animals' and its Spanish translation titled 'Animales' with ID: 91 is not the category of the article in Spanish titled Koala-es (ID:96) (the translated element). This inconsistency would be resolved simply by selecting the value 'Animales' as the 'Category' in the translated element.

 

Detecting Translation Inconsistencies

To detect translation inconsistencies there are two ways (it is understood that the item is associated, i.e. belongs to a set of translations since otherwise it is not possible to detect translation inconsistencies, only self-inconsistencies):

    • 1. When creating or editing a translation the detection of inconsistencies is performed on all associated elements displaying those of the target element only. If there are other elements associated in other languages with translation inconsistencies, the links on the language tabs on the lefthand side will be red coloured and disabled as shown in the figure.

Detecting Translation Inconsistencies example

 

    • 2. Manually at any time you can launch a process that detects translation inconsistencies of one or more components for all languages. This process is launched from the screen obtained by pressing the icon 'Verify Incons' of the Translation Dashboard. This screen is described in detail later on.

 

Showing Inconsistencies in the Translations Dashboard

The Translation Management Dashboard shows inconsistencies as follows:

    • 1. The ID of the element in the ID column is in red color and framed in a box when there is an inconsistency in that element. Hovering on the ID, information on the inconsistency is displayed.

Examples:

Showing Inconsistencies in the Translations Dashboard example1

 

Showing Inconsistencies in the Translations Dashboard example2

 

    • 2. The ID of the element in the column of its language is framed in a box with a yellow background. This indicates that the ID contains inconsistencies.

Showing Inconsistencies in the Translations Dashboard example3

 

    • 3. The column 'Set Status' contains a warning icon indicating that some element of the set contains inconsistencies. This is useful when the element containing the inconsistency is in a language not shown on the screen as in the following example:

Showing Inconsistencies in the Translations Dashboard example4

 

This example also shows the filter 'Inconsistencies only' that can be used to display only those items that present inconsistencies.

 

Note:

In the Dashboard only the inconsistencies of associated elements are shown. The inconsistencies of non-associated elements, ie not belonging to any set of translations are shown only in the editing screen (and of course in the process of Verifying inconsistencies), and since they are not associated only self inconsistencies can occur.

 

Verifying Inconsistencies Process

The inconsistencies Verify process is a process that can be launched manually at any time. This process recalculates self inconsistencies or translation inconsistencies and builds a report with the result of the last time he was launched.

The process is launched from the dashboard clicking the 'Verify Incons' button. The screen that is obtained by clicking on that link is:

Verifying Inconsistencies Screen

 

As seen in this screen you can recalculate the two types of inconsistencies but separately. For self-inconsistencies you have to select a language and click 'Verify'. For translation inconsistencies you have to check the box 'Verify' and one or more components in the box below and then click 'Verify'.

Keep in mind that if you don't select all components, you may have false positives for the inconsistencies that an element can have. Yet it is useful to reduce the time required to recalculate inconsistencies when you know what you are doing. When in doubt the best thing is to select all components although the process takes a little longer.

When the process ends the results are displayed in the upper part of the screen as shown in the following example:

Verifying Inconsistencies Screen results

 

Inconsistencies are shown for each component (in this case we recalculated translation inconsistencies), and the total is also shown. To see the details of the inconsistencies found you can click on the 'View Last Report' button on the right side of the screen. The following information will display:

Verifying Translations Inconsistencies report

 

The display shows for each item the same information displayed in the edit screen. This screen allows you to filter by most of its columns to easily obtain the desired information.

If what we have recalculated are self inconsistencies, we can see the report result by selecting the language and clicking on "View Last Report" on the lefthand side of the screen obtaining the following:

Verifying Self Inconsistencies report


Synchronizing Associations

Synchronizing Associations is only supported on KMFasTrans PRO. Subscribe now!..

KMFasTrans PRO 1.4.0 includes synchronizing associations between KMFasTrans and native Joomla. In version 2.5 of Joomla, there are menu items associations only and these are the ones that are synchronized with KMFasTrans associations. The Joomla 3.x version introduces new associations that will also be synchronized with KMFasTrans associations when the component is ready for that Joomla version.

Synchronization of menu items associations contains two subfunctions:

    • 1. The creation or modification of KMFasTrans associations when creating Joomla associations and vice versa.

Each time you edit a menu item using the Joomla native editor, a set of translations is modified created or destroyed to reflect the associations created with the editor. If you have added a new menu item to a group of menu items, the corresponding set of translations of KMFasTrans will be updated adding the element to the set. If the association has been removed in Joomla, the corresponding menu item in the set of translations of KMFasTrans will be removed (and the set destroyed if no associations remained).

Each time you create or modify a set of translations in KMFasTrans, either by editing one of its elements or by the association or dissociation of a member of the set, you also create or modify the corresponding menu items associations in Joomla. (Remember that in previous KMFasTrans versions there was only one-way association KMFasTrans -> Joomla and only when creating or editing sets in the editing screen).

    • 2. The creation or modification of KMFasTrans associations based on existing Joomla associations and vice versa.

There is a process that can be launched at any time that builds KMFasTrans sets of translations based on existing menu items associations in Joomla, or build menu items associations in Joomla based on KMFasTrans existing sets of translations. In either case are sets or associations modified if they are not affected, for example a set won't be destroyed because its associations doesn't exist as Joomla associations. In order to do a full synchronization you have to run both processes.

The process is launched from the screen obtained by pressing the button 'Synch Assoc' on the Translation Dashboard toolbar. This screen is as follows:

Synchronizing associations

 


Management of Translations Items

The management of Translation Items is fully described in the following online help documents:


Productivity Tools

Productivity Tools are only supported on KMFasTrans PRO. Subscribe now!..

The latest version of KMFasTrans PRO includes the following productivity tools:

    • 1. The administration module 'KMFasTrans Dashboard Link'.

This module inserts a link to the Translations Management Dashboard screen to the right of the administration menu. So you can go to the KMFasTrans Dashboard at any time with a single click. The module is created, published and located in the position 'menu' during the component install process (only on the first installation in which the module is supported). You can unpublish it after that if you want.

modulo dashboard-j25

modulo dashboard

    • 2. The administration module 'KMFasTrans Translate'.

This module inserts a drop-down list of languages to the right of the administration menu to translate elements from the Joomla item listing or from the Joomla edit form. The module is created, activated and located in the position 'menu' during the component install process (only on the first installation in which the module is supported). You can unpublish it after that if you want.

modulo translate1-j25

modulo translate1

a). From the Joomla items listing: you have to select the item that is going to be translated by checking the checkbox in the item row. Then you select the language you want to translate the article in the drop down list of languages.

modulo translate2-j25

modulo translate2

Doing so the KMFasTrans translation editing form will display with all its parameters pre-selected (source language, target language, and all language-dependent fields). If there is a translation into the target language, that translation will be shown in the right hand side. If there isn't any translation into the target language, a blank form to create the translation will be shown. Clicking any of the buttons Save, Save & Close or Cancel will execute the action an return to the Joomla listing of items.

 modulo translate3-j25

modulo translate3

b). From the Joomla editing form: this is the same as above except it is not necessary to select the source element as it is the one being edited. The return from KMFasTrans is, in this case, the Joomla edit form.

    • 3. A 'New' button to create items from the KMFasTrans Translations Management Dashboard.

A 'New' button is available in the toolbar of the screen 'Translations Management Dashboard'.

dashboard 13-j25

dashboard 13

Pressing the button redirects to the Joomla native editing form with some preselected parameters as follows:

      • a). The type of item you are creating (articles, categories, modules, etc..) is the one selected in the drop-down list "- Select Element Type -".
      • b). The preset parameters depend on the type of element as follows:
        • b1). Categories: the category extension is preset with the following value:
          • b11).The extension selected in the drop-down "- Select Extension -" if any.
          • b12).The extension of the first row shown in the list if it shows any rows and none is selected in b11).
          • b13).'Articles' if none is selected in b11) and no rows are shown in b12).
        • b2). Menu Items: The menu is preset to the following value:
          • b21). The menu selected in the drop-down "- Select Menu -" if any
          • b22). The menu of the first row shown in the list if it shows any rows and none is selected in b21).
          • b23). No pre-selected menu if none is selected in b21) and no rows are shown in b22).
        • b3). Modules: The module type is preset to the following value:
          • b31). The module type selected in the drop-down "- Select Module Type -" if any
          • b32). No pre-selected module type if none is selected in b31).
        • b4). Other element types: no pre-selected parameters

After creating the item in native Joomla you can quickly return to the KMFasTrans Dashboard using the link supplied by the module "KMFasTrans Dashboard Link" to the right of the administration menu