Juanjo ReSa
Forum Replies Created
-
Perdon, pero yo no he entrado en tu grupo de Facebook, y no hay problema, dejare de molestarte porque con desarrolladores endiosados que se creen no se lo que no merece perder el tiempo en traducir sus plugins.
Asi que por favor, cierra todos los comentarios o mejor borralos a igual que los archivos po/mo del plugin PRO traducidos por mi al Español.
Y si, esta traducido con el traductor de Google, por eso te envio este texto original por si tienes un traductor mejor y lo entiendes.
Gracias y un saludo
========================================================================================
Sorry, but I have not entered your Facebook group, and no problem, I will stop bothering you because with deified developers who believe they do not know what they do not deserve to waste time translating their plugins.
So please, close all the comments or better delete them just like the po / mo files of the PRO plugin translated by me into Spanish.
And yes, it’s translated with the Google translator, that’s why I sent you this original text in case you have a better translator and you understand it.
Thanks and best regards
If you check the top list of the 200 most well-used plugins, you will see that almost all of them have the Development (trunk) translation file. That means something, no ????
https://translate.wordpress.org/locale/es/default/stats/plugins/
- This reply was modified 4 years, 10 months ago by Juanjo ReSa.
And because you do not use https://translate.wordpress.org/locale/it/default/wp-plugins/gmap-embed of the Italian language and so the follow up of the translations is simpler and you are not always anchored to the translation of a person but facilitate teamwork
In reality the translations have to be done in the “Development (trunk)” project, with the “Stable (latest release)” being the one that inherits the translated strings and the ones that WordPress takes for the updates. This way every time you translate something in the (trunk), the plugin’s chains are automatically updated when the (stable) inherits those chains.
If you translate the (stable) directly every time the developer updates the plugin the text strings are overwritten and it is not worthwhile translating them every time. It is also not necessary to include the different languages in the plugin, but they are updated once the plugin is installed.
In short, the translation teams of each language translate “Development (trunk)”, the “Stable (latest release)” inherits the translated strings and WordPress updates the language files from it, it does not harm you at all, and you go to facilitate the ability to translate your plugin for several people (not depend on one per language), improve translations being up to date and most importantly, that can be translated into many more languages.
What else do you want??
- This reply was modified 6 years, 3 months ago by Juanjo ReSa.