Emoji on the website has been standardized as Twemoji
To date, many diagnoses have been created using emoji such as 😃, but such emoji were being displayed differently depending on the device in question. When content featuring emoji was shared on Twitter, the emoji were converted into those provided by Twitter before being displayed.
Therefore, we have introduced Twemoji (https://twemoji.twitter.com/), which is provided by Twitter, to ensure that the same emoji is displayed on all devices.
For instance, the following image is an example of a diagnosis result for a diagnosis in which emoji are used. The diagnosis result was displayed differently on different devices, as you can see below.
Windows
Android
Mac/iOS
With the introduction of Twemoji, the diagnosis result will be displayed as follows regardless of the device on which it is viewed.
Twemoji
Twemoji is a system in which the emoji displayed are converted into emoji images provided by Twitter via JavaScript. Therefore, the native emoji on the device used will be displayed in the following cases.
- Emoji in input forms, such as the diagnosis creation screen or the tweet submission screen
- Emoji displayed in charts for chart diagnoses
- Emoji not supported by Twemoji
We hope you can take advantage of this feature moving forward.
The issue of consecutive half-width spaces not being applied in diagnosis results has been fixed.
The necessary steps were taken to remove consecutive half-width spaces when our website was revamped in April 2021. However, this resulted in issues such as broken layouts in diagnosis results when consecutive half-width spaces were removed from ASCII art, etc. This issue only occurred on the diagnosis results page, and there were no broken layouts for content shared on Twitter, etc.
This issue has been fixed in this update. We apologize for the delay in addressing this issue.
For instance, the following image is an example of a diagnosis result for a diagnosis in which consecutive spaces are used. The result looks different before and after the issue was fixed.
Before the issue was fixed
After the issue was fixed
This is the end of this announcement.
We look forward to your continued support of ShindanMaker.
