You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, I want to thank the entire Only Office team and everyone else involved with it for their passionate work to deliver an open-source and increasingly feature-rich office experience for Android, a platform that's full of proprietary options but otherwise practically untouched by other FOSS office solutions.
That being said I think full Unicode character set support is a major obstacle towards being able to utilize OO in a productive environment.
Some emojis work, but they are displayed as legacy Unicode characters with monochrome equivalents, like the smiling emoji 😀 turning into
Some characters, for example 🥼 outright don't display at all since there are no legacy monochrome equivalents.
Tested using Only Office 8.2.0 on a Samsung Galaxy Tab S7+ (One UI 5.1.1, Android 13)
Font used: Roboto (I picked Google's modern font to rule out the font being the culprit)
The text was updated successfully, but these errors were encountered:
Firstly, I want to thank the entire Only Office team and everyone else involved with it for their passionate work to deliver an open-source and increasingly feature-rich office experience for Android, a platform that's full of proprietary options but otherwise practically untouched by other FOSS office solutions.
That being said I think full Unicode character set support is a major obstacle towards being able to utilize OO in a productive environment.
Some emojis work, but they are displayed as legacy Unicode characters with monochrome equivalents, like the smiling emoji 😀 turning into
Some characters, for example 🥼 outright don't display at all since there are no legacy monochrome equivalents.
Tested using Only Office 8.2.0 on a Samsung Galaxy Tab S7+ (One UI 5.1.1, Android 13)
Font used: Roboto (I picked Google's modern font to rule out the font being the culprit)
The text was updated successfully, but these errors were encountered: