Suki

Thank you for your consideration.

There is no hurry at all… I think we can still enjoy your wonderful plugin despite this….

Hello,

Congratulations! It is admirable how you have avoided answering the questions posed. Instead, you talk about things that have nothing to do with the issue raised ??

I loved how, despite the fact that no one here has talked about “performance” or “loading speed”, you put all your answer around this fact.

The additional image size will be used in srcset for all images (non-TP too) but that does not increase the site’s page loading time.

Oh, and thank you very much for thinking that maybe there are people who do not know that stored images (that are not loaded), do not affect the loading speed! It seems obvious to everyone… but of course, you never know!

There is no real concern about performance because the image size we register is really small so it doesn’t occupy a lot of space on servers.

Exactly the same with the size of the images… Thanks for explaining that an image of 18px x 18px occupies little!

And finally, thank you very much for giving us the code to avoid the generation of thumbnails… Although there are several plugins and ways to do it (just ask Google or chat gpt for it) you have bothered to put a code. An admirable job. Again, thanks for everything.

Well, now that we all know that thumbnails are indeed very small, and that the files stored on the server don’t affect loading speed, and we also know there are codes and plugins to prevent thumbnail generation in WordPress… let’s try to get back to the original topic:

Is this behavior necessary and user-friendly?

You mentioned, “We will stick to the existing way of just adding the image size all the time.” But this is not accurate. There are other ways to handle this, according to www.ads-software.com. The issue here is not “how to create thumbnails” but rather whether it is necessary to “create thumbnails for the entire gallery,” “without notifying the user,” and “without offering an option to avoid it,” especially if no one is ever going to use a thumbnail-sized flag!

For example, here are a few alternatives, all of which are consistent with www.ads-software.com standards:

1. Simply making it optional. Let the user decide whether they want to generate 20,000 thumbnail images for their entire gallery.
2. At the very least, notifying the user that your plugin will create thumbnails for their entire gallery, so they can choose not to install it.
3. Or asking the user to upload custom flags in the required size (or resize with css..)

But, as another user who previously complained about this issue already said:

You are the boss. Do how you want. It was just a feedback and tried to understand what makes it indispensable. I just mentioned that this non-vital feature is nonsense.

@birtakimseyler says 1 year, 10 months ago

This problem has been unresolved for almost 5 years.

Yes, Translatepress translates “strings”, we know. but…

In automatic translation, string selection should skip “minor” or “decorative” tags such as <strong>, <a>, <b>, etc. and only consider “block” or “sentence” tags like <div> or <p>.

As simple as that.

Sorry but thus is false.

You have automatic translation in Translatepress

just set “Remove coupon form from checkout page” to “Move to the checkout page”

go to the checkout page and you will see the text “Click here to enter your coupon code”?

in the wp-admin dashboard these messages do not appear. They only appear inside the woocommerce plugin.

Anyway, it seems to have fixed itself and is now working.

thanks

WooCommerce 8.8.3

Woo Subscriptions 6.2.0

WooCommerce Stripe Gateway 8.2.0

note: if customers re-enter the IBAN numbers of the bank, the problems seem to be solved.

Hello,

Same problem, the favicon is not showing in Bing results.

?Is it still relevant?

Bearing in mind that:
1- The problem has been reported for more than 4 years by multiple users.
3- You have not solved it

The problem is still RELEVANT, of course.

You can also change its status back to unresolved and let us know by replying to this topic if your request still needs attention.

The problem remains, so this tiket should not be marked as solved in any case.

Please leave it open.

?we encourage you to leave this ticket as it is and open a new one where to mention the issue again and ask for support.

It makes no sense to open another ticket to write exactly the same problem.

Thank you for responding, but despite the length of your reply, you bring NOTHING NEW to the table.

We would be happy to hear about developments and solutions.

PS: This ticket should remain open until then.

Hello,

Thank you for your response.

1. First of all, allow me to make a point:

…sometimes may cause deviation from the original sentence structure when HTML tags such as bold and links are present within the text.

In relation to this, indicate that the problem is not “sometimes”, nor is it a “deviation”, it happens “ALWAYS”, and the result is an INCORRECT, NOT VALID AND MEANINGLESS TRANSLATION.

If we add to that the fact that the use of bold and links on a web page is highly frequent, the result is a DISASTER.

2. About the possible solution you suggest:

One approach would be to wrap the page’s content with a translation block:
https://translatepress.com/docs/translation-editor/#translation-blocks

We have tried adding the “translation-block” class to the paragraphs, and it seems to work well. But how do we apply that to hundreds of pages and thousands of paragraphs?

3. Just a thought for your developers:

I am not a professional programmer, and I understand the Translatepress translate by strings, but…

…Could the option be added for automatic translation to omit, in the selection of strings, the “minor” or “decorative” tags like <strong> <a> <b> etc. and only consider “block” or “sentence” tags like <div> or <p>?

In fact, that should be the normal use of Translatepress. Who would want to translate a bold word in the middle of a sentence separately, and then translate the other two parts of the sentence separately as well? Doesn’t that make any sense?

Of course, apologies if I’m being a bit rude, but I had high expectations of you guys, and I’ve defended you several times from people who love WPML, and now the world has fallen on me.

——-

PS: Final note for readers who arrive here and don’t quite know what we’re talking about.

This is how TranslatePress “translates” (or tries to) the following sentence:

"Buy a pink elephant on this web page."

Separate and translate separately:

1. Buy
2. a pink
3. elefant on this
4. web page

and then put it all together and hope it makes sense?

In Spanish, as expected, disaster struck:

"Comprar a rosa elefante en este página web." 

(four or five spelling mistakes and a serious grammatical one, in a sentence of 8 words!)

Something like translating “I am Tarzan and you are Jane” into “Me Tarzan, you Jane”.

It seems that the Translatepress team has known about this problem for 4 YEARS !!!!

• During these 4 years the problem has been reported numerous times:
• https://www.ads-software.com/support/topic/translatepress-messes-up-content-around-hyperlinks-urls/
• https://www.ads-software.com/support/topic/translation-doesnt-work-with-links/
• https://www.ads-software.com/support/topic/spaces-inbetween-different-strings-especially-around-hyperlinks-or-bold-text/
• https://www.ads-software.com/support/topic/no-space-after-links-in-copy/
• etc.

And this list is just the list of some users who have reported the problem through www.ads-software.com support, but how many more people have experienced and reported the problem through paid support, and how many have experienced the problem, but after a search on this forum it seems to be solved, when in fact it is still happening.

In all cases, it seems that the team considers the problem to be solved, when in fact it is still happening.

In my opinion, this is a problem that completely affects the translation, which is the main purpose of the plugin, so I think it should be considered VERY SERIOUS and URGENT.

There are already many users that after spending a lot of effort in the plugin configuration, even spending money for the translation APIs, we find this problem that makes TRANSLATEPRESS INSERVABLE.

If the purpose of traslatepresss is to make translations, we can conclude that TRANSLATEPRESS DOES NOT WORK, because the result is not a translation of the original sentence, but a completely different and meaningless sentence.

I understand that I have been MISLEAD BY TRANSLATEPRESS, as they advertise features that do not work.

I am sorry to write such a “harsh” text, but after discovering that TRANSLATEPRESS has known about the problem for 4 years and has not even included a warning in the description of the plugin or in the FAQ, it seems to me a huge lack of professionalism and honesty.

It is good to help to improve.

https://aioseo.com/docs/how-to-remove-all-settings-and-data-when-you-uninstall-all-in-one-seo/

And capabilities remain after

Ps: If “we haven’t heard back from you in a couple of days, I’m going to go ahead”… ??

• This reply was modified 1 year, 3 months ago by Suki.

a couple of days to respond or they close the ticket!

I had heard of “fast food”, but this “fast ticket” thing is new to me!

Any reason for such a rush?