Pixel Crushers Forum

Hello Tony,

I have a dialogue entry I am importing from articy that contains an \n character to do a break line. When the actual dialogue entry is displayed on screen, I actually see a \n and not a break line. I even tested using <br> in articy, and I see <br> instead of a break line. However, if I go in the TMP UGUI text box in the editor when I see my sentence and I add a space randomly, it looks like TMP parses correctly the escape characters now. Is there something I forgot to setup to make it work?

My UGUI component has Rich Text and Parse Escape Characters checked. In fact, articy dialogue entries using <b> and <color> are working correctly, but not <br> or \n.

Hi Maxime,

I just messaged you a patch. I'll include it in the next full release, too.

Hey Tony, the patch worked perfectly. Thanks a lot!

Glad to help! Thanks for letting me know about the issue.

Hello Tony,

I'm getting the same issue again, this time with data imported from I2 Loc. FYI, here is my loc workflow:
1) I import from articy in xml file.
2) I copy my data to I2 Loc.
3) I export to Google Sheet to add localization languages.
4) I import back into I2 Loc.
5) I export back into Dialogue System.

It seems like \n are displayed as \n and not as an actual line break. I did select the text in my TMP UGUI Text field and copy/paste it back and line break appeared instead of \n. My guess is that maybe the issue is with the parsing from I2 Loc back into Dialogue System. I am running 2.2.5.

Hi!

The Dialogue System Extras page has an updated i2 Localization integration package that automatically translates "\n" into newlines.

Hello Tony, just updated to 2.2.6 with the I2 Loc update package. It is working great. Thanks a lot!

Glad to help!