[Vtigercrm-developers] Vtiger 6 Update - Jul 2013:: es_es translation

[Joe Bordes]

This brings up a doubt I have and that is happening now in the 5.x versions.
I have translated all modules, mandatory and optional, if you select all 
these modules and the es_es language during install, there is no 
problem, the modules are installed and then the language pack fills in 
the translations into place, but if somebody decides not to install some 
optional module then the language pack creates the language directory 
for it and the optional module can't be installed after or somebody 
deletes the directory and they lose the translation.

I see this problem disappears with the new structure of just one 
language directory for all modules and base system. So I'm not sure if 
you are bringing back this problem or not by maintaining per-module 
language files.



El 16/07/13 20:05, Prasad escribió:
> Joe,
>
>     Looking at the structure proposed I don't understand why files
>     like Assets or Import have been moved to their own module
>     structure and eliminated from the language directory. I mean in
>     the previous svn Assets.php was in the main en_us directory and in
>     this new svn it has been eliminated from there and put inside the
>     Assets package structure. Then others like Google are only in
>     their package directory....
>
>
> Module zip found under packages/ folder are installed at run-time 
> using vtlib package API (their source are available in pkg/ of SVN). 
> We plan to a model where modules/ folder will have some pre-installed 
> (bootstrap) files and then rest be installed as packages. Assets, 
> Google, ... are a step in this direction.
>




Joe
TSolucio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20130716/ce694325/attachment.html>