Forum: CAT Tools Technical Help
Topic: WordPress site translation
Poster: Samuel Murray
Post title: @Noel
[quote]Noel McCourt wrote:
For the licensed version, ideally the client would need to purchase this as it's tied to the domain and needs to be renewed (I think every 2 years?) - so you don't want to be doing that. [/quote]
From what I understood from various YouTube videos, you only need to renew the license if you intend to continue doing translations using the plugin. If this project is a once-off translation or if the client is willing to use a different translation method in future, e.g. some other free plugin, there is no need to renew the WPML license. I'm not 100% sure about this, but that is how I understood it.
[quote]Noel McCourt wrote:
There is also a free connector available on my website:
[url removed]
I'm not promoting this connector over any others but the steps are explained in detail in that link and process is quite similar with most other connectors. [/quote]
Thanks for that, Noel. From what I can see, in its current state, the LocServe connector sends the source text to the LocServe translation agency for translation. However, it is GPL2, so presumably anyone with some skill should be able to edit the source code to take LocServe out of the loop.
FWIW, I googled a bit and saw that Memsource does have a Wordpress connector. To use Memsource in this way requires one to buy WPML anyway and it also requires at least a "Team" subscription of Memsource, which is $200 per month. So, it looks great for large, ongoing projects with dedicated project managers and multiple translators, but not really something for a freelancer with just one medium to small site to translate.
I found that [url= [url removed] ]Smartcat[/url] also has a Wordpress connector, and it looks as if the free freelance version of Smartcat can be used for this. It too requires that you buy WPML, but if one finds Smartcat easy to use, then it may be a useful way of managing the translation. I'm just speculating here.
[Edited at 2020-09-19 10:59 GMT]
Topic: WordPress site translation
Poster: Samuel Murray
Post title: @Noel
[quote]Noel McCourt wrote:
For the licensed version, ideally the client would need to purchase this as it's tied to the domain and needs to be renewed (I think every 2 years?) - so you don't want to be doing that. [/quote]
From what I understood from various YouTube videos, you only need to renew the license if you intend to continue doing translations using the plugin. If this project is a once-off translation or if the client is willing to use a different translation method in future, e.g. some other free plugin, there is no need to renew the WPML license. I'm not 100% sure about this, but that is how I understood it.
[quote]Noel McCourt wrote:
There is also a free connector available on my website:
[url removed]
I'm not promoting this connector over any others but the steps are explained in detail in that link and process is quite similar with most other connectors. [/quote]
Thanks for that, Noel. From what I can see, in its current state, the LocServe connector sends the source text to the LocServe translation agency for translation. However, it is GPL2, so presumably anyone with some skill should be able to edit the source code to take LocServe out of the loop.
FWIW, I googled a bit and saw that Memsource does have a Wordpress connector. To use Memsource in this way requires one to buy WPML anyway and it also requires at least a "Team" subscription of Memsource, which is $200 per month. So, it looks great for large, ongoing projects with dedicated project managers and multiple translators, but not really something for a freelancer with just one medium to small site to translate.
I found that [url= [url removed] ]Smartcat[/url] also has a Wordpress connector, and it looks as if the free freelance version of Smartcat can be used for this. It too requires that you buy WPML, but if one finds Smartcat easy to use, then it may be a useful way of managing the translation. I'm just speculating here.
[Edited at 2020-09-19 10:59 GMT]