plugin language file names are not logical - why?

the names of the plugin language files will make problems:

when I download them from transifex, they are:

for_use_cbinvites_admin_language_de_DE.php
but you need to rename it e.g. as:
cbinvites-admin_language.php

but for profilebook:
for_use_cbprofilebook_admin_language_de_DE.php
you need to rename to:
cb.profilebook-admin_language.php

would it not be easier to name them all in the same way?

jojo12 wrote: the names of the plugin language files will make problems:

when I download them from transifex, they are:

for_use_cbinvites_admin_language_de_DE.php
but you need to rename it e.g. as:
cbinvites-admin_language.php

but for profilebook:
for_use_cbprofilebook_admin_language_de_DE.php
you need to rename to:
cb.profilebook-admin_language.php

would it not be easier to name them all in the same way?

Thanks for noticing and asking.

Unfortunately transifex does not allow '.' in its slug names for resources.

So for old plugins (e.g., CB Profilebook that have element names like cb.profilebook) this is an issue. Don;t want to change element names of existing plugins, so you will have to live with this.

As mentioned before (in other posts), on our new site we will be automating the building and continuous releasing of language plugins.

Until then I will be manually building and publishing new language builds on the files area of each language project of our forge:

forge.joomlapolis.com/projects/lan-cb