Forum Discussion
Localization friendly request
I'd like to kindly request that the emoji be removed from the "Bye!" string.
When the label is exported to XLF, the emoji becomes gibberish and this becomes an issue in translation. Especially since the gibberish isn't recognized as an emoji on import. We then have to communicate to our clients that if they like the emoji, it won't be there when they import their translated labels from us, they will need to manually copy-paste it from another course.
Secondly, re-affirming a now 4-year-old+ discussion from elsewhere, that there should not be character limits in any fields. Scroll bars are a viable solution when over a certain count. When we translate content from our clients, they routinely use the full character counts, and many languages takes more 'words' to convey the same meaning. This leads to condensed translations that don't allow for the full meaning.
Function over form. When "looks" are placed before effective communication, it's a fail ('looks' has been the reason often cited by support for the character limits).
Thank you.
- KarlMullerCommunity Member
Hi Matt,
You can remove the Emoji yourself.
Open the Label set and go all the way to the bottom.
Delete the emoji in the right column in front of Bye!
- MattGartonCommunity Member
The problem is, we get shared dozens of courses a week. And every time we get a new one, the labels revert to default EN (along with publish settings), which means it re-appears. There's basically not a permanent solution to this currently as we've seen.
- LeaSAgatoStaff
Hi, Matt! If you edit the label on your account, all your courses using the same label set will be affected by the change. Have you removed the icon from your label sets? If you want to use the same label used by the author of the course, they can export the label and send you a copy that you can import. You can check out the detailed steps in this article. I hope this helps!
- MattGartonCommunity Member
Can you import and exported label set though? We've tried a few times and it always fails, since the export only has the <source> populated and not target.
For now we are leaving it. If we delete it from our EN then we won't be able to copy it back in if there's a client that does actually want it. What would be really nice is if Rise detected the "giberish" and made it back into an emoji on import.