[vako]

Hi Stephan,

 

Please share exactly which theme strings you want to translate and their definitions(translated versions) in your preferred language.

 

Kind Regards

[Sabine Jordan]

I would like to add to the thread that I have been reading here. I have encountered the same issues as all the other users. Fixing the problem with Loco translate didn’t solve the problem. So after realizing that the Loco translate will not work correctly for the Ashe Pro theme I started to modify the theme directly. Please note that there are not only issues with the comment area. Also the search field will show English text instead of German. I know  fixing it in the theme editor is cumbersome since I have to do it every time the theme is updated but it works. The best way to solve the issue would be to review the translation for the Ashe Pro theme and add the missing terms for German. If help is needed I am willing to provide support with the translation.

Best regards

Sabine

[vako]

Hi Sabine,

 

To be honest, we dont know why users find it hard to use the Loco Translate plugin, we use mentioned plugin for years and had no issue, it’s a very simple process to translate with loco and changes will be saved after update too.

We help our users to make translations, all we need is string names and their translated version, dashboard access via secured login URL and that’s it.

 

Kind Regards

[Sabine Jordan]

Hi Vako, it is not complicated to use the Loco Translate plugin, I have successfully used it for other themes. However there is an issue with the Ashe Pro theme file in Loco Translate. It is missing certain strings like no comments. Please see below: 

However, you will find the term No comments in the following string:<h2  class=”comment-title”>

<?php comments_number( esc_html__( ‘No Comments’, ‘ashe-pro’ ), esc_html__( ‘One Comment’, ‘ashe-pro’ ), esc_html__( ‘% Comments’, ‘ashe-pro’ ) ); ?>

</h2>

Does this information help?

Best regards

 

Sabine

[Stephan]

That is exactly what i try so clarify: why are there strings which can be realized by loco and be translated like the dynamic homepage title – and why other strings which are dynamic too like the heading blocks in some widgets which are then not realized by loco because they aren’t defined by you in the code.

It is NOT the solution to ask every customer for every not translated word and then you do it by hand in the backend…the solution should be to provide all strings to loco (for example). The hardcoded and the dynamicles too.

If you offer a string field in a widget block where we can put in text for header (its an example!) Then this string should get a declaration in code for loco too.

 

And by the way: if you wonder why so many people habe problems with loco in combination with your theme (there are a few more topics in this board) maybe you should ask yourself: could it be a problem in the theme?!

[vako]

Hi Sabine,

 

Weird, we were able to find your mentioned strings when we are using loco translate, please see the screenshot: https://nimb.ws/HAykzb

Anyway I will redirect this topic to the developer’s board and they will check  the case

 

Kind Regards

[vako]

Hi Stephan,

 

The home page title and widget titles are not theme strings, both can be managed and changed manually, so there is no need to translate them via Loco translate.

Users as you mentioned here: “And by the way: if you wonder why so many people have problems with loco in combination with your theme” in most cases have issues with loco translate and not with the theme, most of them don’t know how to use plugin correctly and which translate files to chose during the setup.

To not confuse our users and save their time, we are translating theme strings, to be honest, plugin setup and functionalities are beyond the scope of our support but we respect our users and provide help if we can handle the request.

 

Kind Regards

[Stephan]

Ok Vako,

 

you’re right, if i title the page then I do this in customizer under “Website-Information”. This doesn’t appear in Loco…but it appears in dashboard under “Languages” in “Translations”. There I can translate the name of the page and this changes the HeaderText too. (I think this is from PolyLang)

But look at Screen1, there I give the headlines for the sidebar widget directly.

How to translate this automaticly when the language of the page is switched?

In this example:”Keine Kommentare vorhanden” was translated right by Loco because there exists a list value for that, but “Newer Comments” is not translated, because it doesn’t appear in the Loco List (I think because I give the text in the text-field and its writen as plain text in html-code and not as a value). So I think that is not a problem of loco…what do you think?

Now I’m not sure if it was the right decision to buy the theme, it looks nice and so I thought to buy it, but haven’t researched the compability to Loco or PolyLang before.

There are many themes on market which are completly translate-able by the mentioned plug-ins. It should be possible to put every fixed string and every dynamicle string in the ashe-pot file or not?

https://ibb.co/NWZ8Js9

 

[vako]

Hi Stephan,

 

Please check again the screenshot we shared, mentioned sting name “No comments” cab be found when using the Loco translate if you can find it that’s the case we ask for the safe and secured login URL to access users dashboard.

https://nimb.ws/HAykzb

Polylang plugin can translate pages and content, but if you are using the free version of the plugin you cant translate the widgets and some more dynamic strings, please contact the Polylang support team and ask them for the functionalities you mentioned.

 

Kind Regards

[Stephan]

Hello Vako,

 

1.) please take a look at the following screens. They show the part you mentioned:

https://ibb.co/nzdjkZd

https://ibb.co/bRXyQtn

https://ibb.co/LJHP1DZ

https://ibb.co/wRmbv2x

https://ibb.co/r73rmwn

As you see I already have found the “No comment” string in Loco, BUT now see the result at my page:

 

https://ibb.co/gFKqXx0

So why?

 

2.) And as you also can see the problem right…yes I may translate the “Newer Posts” and the “Newer Comments” directly in the customizer, but then there is no possibity to change back to englisch when someone switches the language of the page. The Blogs have to be done twice by me for each language (seperate blogs for each)…thats clarified.

[vako]

Hi Stephan,

 

If you want to have a multilingual website and string, you need to use WPML or Polylang plugin, with loco it’s not possible as I know, we use loco translate in case if you users want to translate strings only on 1 static lenguage.

 

Kind Regards

[Stephan]

Ok…as i understood now loco is not for multilanguage pages but for translating themes and plugins in one fixed language.

But whats about the “no comments” problem? Still not solved…you didn’t answers that part of my last post.

[vako]

Hi Stephan,

 

We answered we shared a screenshot where we show that mentioned string can be found and translated, if the issue appears on your let us check your website from the back end using safe/no login info needed login URL

 

Kind Regards

[Stephan]

This reply has been marked as private.

[Stephan]

Did you use the backend yet?

[Author]

Posts