Major 
[CMS-3870] i18n key problem in the sitemap tool after adding languages
Raphaël Franchet
added a comment - The icon issue will not be backported to 3.4 but will works fine in 3.5
Icon are in the same plugin as the i18nkey in resources/img/flag/[small|medium|large]/flag-[code].png
Or if the catalogue is not a plugin (application for example) it will be in WEB-INF/param/flag_resources/[small|medium|large]/flag-[code].png
Raphaël Franchet
added a comment - The icon issue will not be backported to 3.4 but will works fine in 3.5
Icon are in the same plugin as the i18nkey in resources/img/flag/ [small|medium|large] /flag- [code] .png
Or if the catalogue is not a plugin (application for example) it will be in WEB-INF/param/flag_resources/ [small|medium|large] /flag- [code] .png Still nothing about icons, but LanguageManager was generalized for 3.5.
Raphaël Franchet
added a comment - - edited Still nothing about icons, but LanguageManager was generalized for 3.5. Raphaël Franchet
added a comment - Done for the i18n:keys. Still have to handle flags Raphaël Franchet
added a comment - As you can imagine we are not going to add every code for the moment.
Since 3.4, you can add key to an existing catalogue... do it! 
The remaining missing feature is to set the flag
(by the way in your languages.xml, you should use i18n keys)
Raphaël Franchet
added a comment - As you can imagine we are not going to add every code for the moment.
Since 3.4, you can add key to an existing catalogue... do it!
The remaining missing feature is to set the flag
(by the way in your languages.xml, you should use i18n keys) 
Laurence Perier
added a comment - Ok
It would be nice to add the key : <message key="PLUGINS_WEB_ADMINISTRATOR_SITES_LANG_CA">Catalan</message> in the plugin web.
Laurence Perier
added a comment - Ok
It would be nice to add the key : <message key="PLUGINS_WEB_ADMINISTRATOR_SITES_LANG_CA">Catalan</message> in the plugin web. Raphaël Franchet
added a comment - to start, you should not create your own codes, but use international ones... for example, castillan is spanish : es.
Raphaël Franchet
added a comment - to start, you should not create your own codes, but use international ones... for example, castillan is spanish : es. Laurence Perier
added a comment - Since 3.4 it is possible to add new languages in a configuration file languages.xml like:
<?xml version="1.0" encoding="UTF-8"?>
<languages>
<language code="fr" i18n="false">Français</language>
<language code="cas" i18n="false">Castillan</language>
<language code="cat" i18n="false">Catalan</language>
</languages>
but in the sitemap tool there is an error.
It would be nice to be able to set this key and the flag
Laurence Perier
added a comment - Since 3.4 it is possible to add new languages in a configuration file languages.xml like:
<?xml version="1.0" encoding="UTF-8"?>
<languages>
<language code="fr" i18n="false">Français</language>
<language code="cas" i18n="false">Castillan</language>
<language code="cat" i18n="false">Catalan</language>
</languages>
but in the sitemap tool there is an error.
It would be nice to be able to set this key and the flag 
I created
CMS-3941to talk about images. This ticket finally only talks about i18n keys and is backported to 3.4