Viewing 12 replies - 1 through 12 (of 12 total)
  • I also really need to know if this will be solved now.
    I cannot migrate to Business if Deepl is not working properly. Using the Deepl api is the biggest benefit of the business account.

    Hello there,

    Thanks for reaching out to us!

    We are currently aware of this issue and our team is working on it!

    I will let you know as soon as there is any improvement on this matter!

    You are right about the translation block work around but this is currently the easiest way you can avoid this.

    Best Regards!

    Thread Starter kozmonauta

    (@kozmonauta)

    Hi @andrei202
    Can you give me an approximate deadline for this resolution?

    If I purchase the business plugin this week and translate approximately 500 pages, when this resolution comes out, will all of my 500 translated pages create the spacing automatically or will I have to manually re-space each paragraph of the translated pages?

    My fear is that after doing hundreds of translations and corrections, I will have to delete them and start all over again because of this spacing. By my count it would be almost 10000 spacings.

    I really hope that if I purchase the plugin these spacings of the translations already done will be done automatically.

    Thank you.

    I am also interested in a deadline, and to know if when this fix comes out, all my translations previously done with Deepl will have their spacing fixed.

    Plugin Author Cristian Antohe

    (@sareiodata)

    Hello,

    I wish I would have better news, but I don’t. We’ve set aside some time next week to talk with our dev team regarding this, but there are issues that are not straight forward to solve.

    In the mean time you could add a small padding to bold content with CSS. With a bit of tweaking it could look ok.

    .post-content strong{
    padding: 0 3px;
    }

    If the fix comes out, I can’t tell you if we’ll be able to apply it to previous existing translations.

    Best Regards!

    Thread Starter kozmonauta

    (@kozmonauta)

    @sareiodata
    Did you manage to solve this?
    You don’t know if when the solution comes the previous translations will be fixed, so I’m still waiting for you to fix this error to use TranslatePress. But I cannot continue with my site without translation, if this is not resolved unfortunately I will have to choose another plugin.

    I’ve been very patient, but 2 months of no response is really bad.
    In reality, it’s not just months, if you look at past messages from the links, it’s years. That’s a little scary.

    I am using the free version of Translatepress. I am going across the same issue “spacing issue between words”. Especially, Any link under the word or any bold word or line showing issue.

    Check this page (https://codepaperclient.com/ccffa/fr/goats/). This page has a lot of spacing issue.

    Please resolve this or let me know the solution for future

    Thread Starter kozmonauta

    (@kozmonauta)

    @andrei202 @sareiodata
    Did you manage to solve this problem?

    Any update on this?

    Hello,

    Has this problem been fix ?

    I just bought the Business version and I have this issue. Even when I edit manually it comes back.

    This topic was open 18 months ago, I hope I can be refunded if nothing happend.

    Is this problem solved? I’d like to take out a developer license but it seems essential to me that this problem is no longer present. We use translatepress for automation and if we have to add classes or go back behind it, we might as well take out a competitor who at least doesn’t let a problem linger for two years.

    Plugin Author Cristian Antohe

    (@sareiodata)

    Hi,

    This particular issue was treated and fixed. There can be some usecases that manifest like this particular one, but have a different base case, like different encoding for spaces in the original language then an actual space, etc.

    Best Regards,

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘TranslatePress Spacing Error.’ is closed to new replies.