Created packages doesn't work about com_localise HOT 5 CLOSED

@javier
I guess you were mistaking in your test.
It does not work completely (see my comment in #94
But it does for the files we can choose in the field (here is a screnshot of part of the files)

from com_localise.

Adding some important comments to take into account when creating the Package feature:

One idea suggested was that you should be able to create Joomla language packages for:

• Site,
• Admin
• and Site & Admin togethere.

The reason is that there is some tranlsations of Joomla that are only done for frontend. However @infograf768 suggest that we don't do Site or Admin individual packages but always Full packages:

[05/06/14 18:48:34] infograf768: we need always a full pack, even if some files are not included in admin
[05/06/14 18:48:54] infograf768: because of the way we Update or propose languages to install in J
[05/06/14 18:49:40] infograf768: the automatic cron needs that specific name for the zip as well as the version
[05/06/14 18:50:04] infograf768: fr-FR_joomla_lang_full_3.3.1v1.zip
[05/06/14 18:50:25] infograf768: is what I now get with com_localise as is in develop branch
[05/06/14 18:50:42] infograf768: but I need 3.3.1.1 as version in the xml

cc: @hikashop-nicolas

from com_localise.

For core, indeed. All core translations for Joomla HAVE to include some admin translated files as explained here: http://docs.joomla.org/J3.x:Making_a_Language_Pack_for_Joomla#The_Site-only_pack

from com_localise.

Also: since we have implemented the format for core files with its manifest, we prevent Uninstalling languages per se (as site or admin), only full packs can be Uninstalled, as this was creating issues.

from com_localise.

Please find here #103 a temporary solution that lets create a fully usable core pack (if the xx-XX.localise.php is present)

from com_localise.