does works great (posts, menus, woocommerce and more)

Hi,

Thanks for your nice message, i try to make another way to make WordPress multilanguage system. Not duplicate everything.
The problem you have with Gutemberg is strange you can write me directly to see what’s wrong.
What is your old multilanguage system, i have make a tool to migrate qTranslteX site.

Stéphane

I did use wpglobus, don’t bother integrating it just for me though ??

But was not happy with it not supporting woocommerce, nor the way it stored the translations in the text strings with syntactic sugars that would mess with other plugins.

Falang is doing a good job with woocommerce translation, congratulations. Is there a way I could translate attributes values as well (aka product variations?)

Issue with the gutenberg copy-paste seems to be related to the fact gutenberg uses html annotation (ie <!– wp:paragraph –>) that seem to be lost in the copy-paste process… so even though linebreak are brought over the final text is displayed as a single paragraph.

Not sure it’s relating to gutenberg/classic editor, but in some translation boxes copy-pasting either text with styles or html code doesn’t seem to work from translation backend:
See eg at https://news.vunderatert.lu/de/product/saisonales-gemuese/ where the HTML a href code in the description field shows, whereas switching to FR language shows the source value as a working link: https://news.vunderatert.lu/product/legumes-de-saison/
I found no way to get a “rich text editor” to copy that description to, I guess this translation field is handeld as raw text and thus does not handle html tags.

Another feature suggestion: transversal translation of the same text box into multiple languages. I use deepl.com online translator for more complex texts translations, and copy-paste de translated text to the different languages. Having a single page allowing me to copy-paste that text into the 3 active languages would be faster than juggling between multiple tabs (one per language)… but don’t put it too high on your priority list ’cause with different active tabs does the job too, and makes editing boxes big enough to check for problems.

woodcommerce is supported directly with Falang

1)You can translate variation too but you have to go in the falang “translation post”
you can filter by product_variation.Actually the variation is not translatable directly from the wc product view

2) yes you can translate product attribute , you will see on each wc product attribute an input for name/slug/description BUT you have to enable the tranlation for them
Falang > Settings > Translate Option (tab) > Translate Taxonomies you have to check it.

1) the copy past need to be done in text mode. i will fix the copy past in html mode.
I know i have fixed the bug of gutenberg in a previous version.

2) bug with the descrition field can you contact me with my contact form on https://www.faboba.com to see what’s wrong on your site directly.

3) the rich editor are for description but it’s right some input need this rich editor too, i have put this in the todolist.
Actually you have just to copy the html text in a text area
4)translation service
You can configure yandex but since some week it’s not free anymore, i will add other automatic translation for help like bing, google, deepl and lingvanex

Try to use the Falang Transaltion page with filter , you have a clear view of all translation , publish status …

Stéphane

Thanks Stéphane for your quite complete answer and great plugin feature.

I confirm all of these suggestions do work, great support, thus change my vote to 5 stars !

another quick suggestion: would be really nice to have “inplace” editing of the translation strings directly from the Falang translation place, at least for “short” simple texts. Ideally double click would be captured just like the current “click on edit”, and a single click would allow to edit the string in place, ajax-like.

Thanks again for the wonderful support !

Berteh.

• This reply was modified 4 years ago by berteh.
• This reply was modified 4 years ago by berteh.

Hi,

Thanks for changing your vote.
To be honest i have found a problem due to the autop when you copy a translation in falang for a post in the text mode and you save it all is working but if you change from text to visual in the editor you loose the <p>
It’s know problem with WordPress i try to find a solution since this afternoon

Stéphane

Wonderful, thanks !

another thought: my menu items mostly come from readily translated elements (pages or posts titles), yet Falang asks me to translate them again in the Menu translations. Would it be possible to dynamically use the “original” translations for the menu, unless I overwrite them to make them a bit shorter ?

Thanks again for the wonderful support !

I added a link to Falang in my website footer, and won’t hesitate to recommend it wholehearteadly.

Berteh.

at least I have probably found the solution, i will publish a new version with a new parameter to keep <p> in classic edition translation

It’s not necessary to translate a menu item or a post/page by default the original is displayed.
Falang in the menu translation only display menu translated or not but it’s not necessary to translate it.
ex: the “home” menu item is generally not translated, we keep it “home”

Thanks for the link on the footer, the best for helping falang is to speak about it on forums and blogs

Stéphane

• This reply was modified 4 years ago by sbouey. Reason: typo

Great about the <p>, thanks !

For the menu I meant the opposite: I want to have the translated titles show in the menu by default, not the original.

EG: on my (german) page https://news.vunderatert.lu/de/contact/plan-dacces/
the title is in german (Anfahrtsskizze), but the related menu item (top menu > en pratique > plan d’accès) is displayed in french (Plan d’accès)… and so is the whole menu while most pages have translated titles.

Would it be possible for you to make Falang use the translated texts for the menus by default, and not just the main language ?

Berteh.

Hi,

It’s depends of the menu item but you have to translate the menu title and the page title
I send you a mail to see how you configure it in backend.

Stéphane