Hello feliperguez,
The error you get is because you are installing the extension that is already installed and you will find it in Components, or the component folder was deleted without uninstalling and the remains of it appear.
You can choose to remove via FTP or NinjaXplorer the /components/com_translationsmanager/ folder and then install the extension again.
I personally disagree that translating Joomla! With Translations Manager being the best option, I find the extension unstable, and in cases such as the installation of an extension previously translated locally or already translated by the developer, we run the risk of Translations Manager overwriting the .ini files and leaving them in English without saying a word, something that can ruin hours of translation line by line, according to the method of this extension.
I trust more in manual work, downloading the corresponding version, taking the .ini of (en-GB) which should always be the language by reference to start any translation of extensions, adding the corresponding entries of the .ini (es-ES) created as new language files in the corresponding .xml, pack the result and install.
For me, this methodology allows for more manual but controlled version control, and in the case of untranslated strings, resort to extensions like NinjaXplorer to edit the corresponding .ini and translate those pending strings.
This whole process is more manual and artisan, but I think it provides a control that Translations Manager does not have, and I say this from experience, after having lost .ini files with more than 1800 lines of translations on several occasions when trying to reread them with the extension that concerns us.
As I said, it is my personal vision of the situation, and based on the fact that unfortunately .ini files are not supported by to carry out translations open to the community, as is the case of open source code applications (GNU /Linux) you have to settle for more manual but safe methods.
Cheers
Answered: 07/08/2010 10:21 pm
Facebook Comments
Disqus