Translations list on the plugin page

Hi,

Because the translations in your plugin folder are only imported into translate.wordpress on initial import (so only once).

You should now do all translations via link above. You can also leave the German po/mo in your plugin folder but why should you?

Guido

Hi Guido,

Understood, thanks a lot for response!

Hi Ivan,

You’re welcome. Some additional info:

Before a translation is shipped with your plugin it should be approved by a PTE (Project Translation Editor).

Currently you cannot become a PTE for other languages besides your native language.

More info on the Polyglots page.

You can post a request there to become a PTE for your native language. You should try to find other users who become your PTE for other languages such as German. Or wait until it gets approved by a so called Global Translation Editor.

A translation should be 100% (and approved) before it’s shippped with your plugin. It will be loaded into the global translations folder in wp-content.

Guido

Hi Guido,

Thanks again for very detailed response!

Are you interested in any copperation in this area?

For example, I can review your translations to Russian, while you can review my translations to your native language (I am guessing this is Dutch?).

I plan to hire translators, so it will be just review / approve prepared translation.

Yeah, no problem.
I hope your theme/plugin does not contain 100+ strings ;-).

Currently I don’t have PTE’s for other locales (so I have 100% control over my plugin) but I still wait for approval of several locales for 1-2 months now.. that’s the downside of not having own PTE’s for other locales.

But as far as I know everybody can translate strings of my/your themes/plugins.

Guido

Great, thank you!

I will prepare Dutch translation.

Feel free to add me ( @ivanweb ) as Russian language PTE to your projects, also I can help with some translations (not only review).

Hi Ivan,

The next couple of days I will try to start translating it. Don’t have to be PTE for this, everybody can contribute.

I have installed your plugin and notice you’ve added all examples on tab ‘Popup form’ including HTML (ul, li). I advice you to make seperate strings and leave the HTML outside the strings.

And the title of your (php) files in folder ‘templates’ contain .tpl (= old file format?).

My most popular plugin is Very Simple Contact Form.

Guido

Hi Guido,

The next couple of days I will try to start translating it. Don’t have to be PTE for this, everybody can contribute.

Great, thank you!

I have installed your plugin and notice you’ve added all examples on tab ‘Popup form’ including HTML (ul, li). I advice you to make seperate strings and leave the HTML outside the strings.

OK, I will rebuild it.

And the title of your (php) files in folder ‘templates’ contain .tpl (= old file format?).

No, this is usual PHP code (not something like Smarty), .tpl extension is used just for easy differentiate templates (“view”) files from “code” files.

My most popular plugin is Very Simple Contact Form.

OK, I looked Russian translation and I have added lacking translations:
https://translate.www.ads-software.com/projects/wp-plugins/very-simple-contact-form/dev/ru/default?page=1

Perhaps better to use something like ‘Fill in number (%s)’ for string
“label_captcha”, because different languages may have different word order.

Also I have translated few strings from readme (not finished yet).

Hi Guido,

I think translation readme isn’t very important (but let me know if want translate readme too).

I am ready to translate some another your plugin ??

Hi Ivan,

Use a printf for ‘fill in number’ is better indeed… thanks for the suggestion.

I also never translate a readme, so no problem. Translation will be shipped without readme, so this is not necessary to translate.

You don’t have to translate other plugins, but if you have some spare time, my second poular plugin is Very Simple Event List.

About your plugin, I notice soms double strings such as ‘web stat’. With and without capitals. And you mention for example ‘name’ and ‘your name’. In order to make the list of strings as little as possible the best thing to do is check whole plugin for duplicates and make those strings the same.

Guido

Здравствуйте))EM

простите,что вмешиваюсь в переписку,мне просто очень нужен человек,который работает с Word Press!!

мне нужно подвязать рассылку к Smartresponder.
можете мне кого-то посоветовать??

Спасибо с уважением Наталия))

Please visit the Russian support forum for this.

Guido

Hi Guido,

About your plugin, I notice soms double strings such as ‘web stat’. With and without capitals. And you mention for example ‘name’ and ‘your name’. In order to make the list of strings as little as possible the best thing to do is check whole plugin for duplicates and make those strings the same.

Thank you, I will reduce list of string.

Also I discovered better way to deal with front-end forms translations – just add options for them in wp-admin, so users speaking by any possible of hundreds languages can manually translate it. And users don’t have to wait translation from my side.

Options stored in the database, so it will not be overwritten during updates.

You don’t have to translate other plugins, but if you have some spare time, my second poular plugin is Very Simple Event List.

OK, I just finished it.

Thank you very much for your help!

Thanks for translation of the other plugin. If you also have other themes/plugins let me know.

The translate option in dashboard sounds great, so everyone can use it and you don’t have to wait till it’s translated. Let me know when new strings are available for translation.

Guido

Hi Guido,

Now I become PTE for your plugins, so I translated/approved few new strings in VSEL / VSCF.

BTW, I found couple of issues in VSEL:

1. Using plugin name instead text domain.
For example, __( ‘Uninstall’, ‘Very Simple Event List’ ), instead __( ‘Uninstall’, ‘very-simple-event-list’ )

2. Perhaps better to reduce repeating plugin names in settings page. For example, “Translate VSEL” => replace to just “Translate” to reduce translation work. Plugin name mentioned in the header, so user will understand what plugin mentioned.