Hi,
thanks for your post, and sorry for the trouble.
Why are you saying that TablePress is not compatible to WPML and not that WPML is not compatible to TablePress 😉
A good and solid approach here is to simply maintain one table per language. Just pre- or postfix the table ID with the language abbreviation (“en-products” and “de-products” for example) and use the correct ID in the Shortcode of the translated page.
Another idea would be to work with the TablePress Row Filter Extension from https://tablepress.org/extensions/row-filter/ here. You would just copy each row for each language and use the language abbreviation as the filter term, e.g. in an an extra but hidden first column.
Regards,
Tobias
Maybe “compatible” was not the proper term to describe, that TablePress could need an additional feature in its code for easier translation with WPML.
Your proposal to maintain one table per language was already in my mind. But it does not solve my problem. My problem is the translation of the content of the table.
I can copy an existing table_de. I rename the copied table into table_en. But the content in the copied table is still in the original language. Now I have to go in my WordPress back end to translate the content of the copied table. In order to translate I have to struggle through the complete table content, formatted with HTML tags and CSS style tags. That is very arduous.
I am not a programmer, but I believe, that if TablePress would have “gettext calls”, then the WPML plugin could extract the text content from the table. Translating only text content extract is very easy for human and machine translators.
Hopefully I could explain my problem a little more understandably.
Hi,
I’m afraid that I can’t offer a different solution here. gettext calls don’t make sense with user-generated table content.
Having one manually translated table per language is the best way here.
Regards,
Tobias
Hi @tobiasbg,
the Contact Form 7 multi lingual extension allows for translation of custom contact forms (with custom field labels etc). This is very handy, as you only have to define your structure once…
This would be equally handy for your table plugin.
But i get that it would mean tons of extra work for you 🙂
Thanks for the already very (very!) useful plugin.
Regards,
Patrice.
Hi Patrice,
yes, this looks like a nice solution, but I don’t have plans to integrate something like that into TablePress at this time. Sorry.
Regards,
Tobias
