OK. I have renounced for a long time to even try to understand coders' reasoning.

The issue may not have gone away because it was never discussed in this forum but on other medias and we have no tutorial to refer to...
One can't expect that a private or semi-private conversation/decision be known from thousands of users...
Let's try to move on though.
There are still 2 things you could do, to make things easier for all.1. As the xml should only install an admin language file, the install code should be consistent with other extensions.
i.e.
today, the admin ini file is uploaded with the following code, the file being at the same level as the xml:
Quote:
en-GB.plg_myplugin.ini
fr-FR.plg_myplugin.ini
instead of, as for others extensions, ini in an admin folder and code being
Quote:
en-GB.plg_myplugin.ini
fr-FR.plg_myplugin.ini
2. As you guys consider the use of frontend strings as an exception and there is a fix which is, if I understand well (correct me if wrong)
a) add a second ini file to load in admin/languages/ of the type en-GB.plg_frontend_myplugin.ini
b) add the following code in myplugin.php
Quote:
$lang = & JFactory::getLanguage();
$lang->load('plg_frontend_myplugin', JPATH_ADMINISTRATOR);
Then this should be documented somewhere as a tutorial for all to know. This would avoid useless questions.
3. Let me quote you Rob
Quote:
I have written several plug-ins for Joomla! 1.5 and I have had to deal with this issue only once.
It would be useful to have access to these as samples of what can be done as we do not have any in core with these solutions.
I guess these plugins are GPL.
Side Note:
You surely have understood that it is not as a coder that I raised this issue but as someone trying to help users on language matters.
_________________
Jean-Marie Simonet / infograf ·
http://www.info-graf.fr Multilanguage in 1.7/2.5: http://help.joomla.org/files/EN-GB_mult ... torial.pdf---------------------------------
Joomla Translation Coordination Team • Joomla! Production Working Group