If we add html code in input table row, the translation feature for that row does not work.

  • Profile Image
    Pumba1987
    Asked on October 11, 2017 at 10:03 AM

    Hi

    We tried to use forms with different language (German and French) but there some field they aren't translated and rest in main language. But in options we translated this field.

    Do you have a idea?

  • Profile Image
    ashwin_d
    Answered on October 11, 2017 at 11:32 AM

    I did test your form and I am able to replicate the issue. I am not sure if it is caused because of the html <br> code you have. 

    I will test the issue further and get back to you soon.

  • Profile Image
    Pumba1987
    Answered on October 17, 2017 at 05:11 AM

    Do you have any update? I tested it without html codes and then the translation works.

    Is it not possible to use html codes in a form with different languages? That would be very sad because it is so much easier when you can use html codes and also we don't need to create a form for german and one for french.

  • Profile Image
    ashwin_d
    Answered on October 17, 2017 at 07:20 AM

    Please accept my apology for the delay. I did test your form again. It seems you have now removed the html code from the "Input table" field and that seems to have solved this issue. When you add html code in the options/ input table row, that causes the translation to break for the option/ input table row where you have added html code.

    I am not sure if this is a bug but let me report it to our backend team. We will get back to you as soon as we have any update from them.

    For now, I would suggest you to please continue without adding html code and that should solve your problem.


  • Profile Image
    Pumba1987
    Answered on October 17, 2017 at 07:26 AM

    Hi

    Thanks for your update. Yes, i deleted html codes in first input table for testing it. 

    Thanks for looking with your backend team, that would be great if this would work with html codes.

  • Profile Image
    ashwin_d
    Answered on October 17, 2017 at 09:04 AM

    I have already reported this to our backend team. Upon checking the ticket status, I found that one of our developer is already looking into this issue. We will get back to you as soon as we have any update on this.