Translations problems and suggestions

Hello,

Thanks for your message. We are aware of the situation, and not so long ago we changed the “Stable tag” from “trunk” to the actual latest version of the plugin.

We have always kept the “tags” directory empty, because translating the “Development version” of the plugin produces the same result. It is our responsibility to make sure older versions of the plugin will not be harmed by the most updated translation.

Therefore, it is safe to translate the “Development version”, as we have never maintained the “tags” directory.

Thank you,
The VikWP Team

Hello again,
I am Global PTE in France and I would like to suggest you to try to follow the best practices which say to put in the tags directory the versions so that they appear on translate in the stable part of translate.
This simplifies our task since we focus on the version in production. So the chance for your users to have an up-to-date translation increases.
In your current setup, strings validated in dev go to stable (and thus to end users) if and only if they exist in stable. If there is a change in the dev that does not match the stable it stays in the dev.
If you modify it again we will translate it again but the previous work is taken for nothing.
Moreover I remind you that the Language Pack is generated at 90% of the stable. We have no visibility on it if it doesn’t appear.
I think it would not take you hours to add this into your process and would save us translation (for all locales) time, efficiency and work quality.
Thank you

Hello,

Thanks for your message. It is definitely a quick operation, all we need to do is to clone the “trunk” directory and place it in the “tags” directory under the proper version.

We are about to release the new major release for Vik Booking (v1.6.0), and so we will definitely take care of the “tags” directory with the very next SVN commit.

Thank you,
The VikWP Team