Open NJJ96 opened 1 month ago
I failed to specify: the images are from a Windows desktop, but the behavior does appear to replicate on iOS, at least.
Hey, well we can try to trim spaces this but it might break other people formatting that uses spaces. The space are inserted by Mecab, not by the plugin, and we don't have control over Mecab development (which stopped long time ago...). We are just hacking our way through Mecab outputs 😢
I'll try to give it a try next time I'm working on the plugin!
Much appreciated! If it helps at all, I think that I’ve managed to apply some styling that at least somewhat addresses the horizontal and vertical spacing on desktop, and seems to address only the horizontal spacing on mobile (at least for iOS).
Also hoping that this is helpful without adding complexity, I’ve noticed a few more things while tinkering around:
text-size
styling property on the fields with kanji after the add-on has applied the furigana will reintroduce spacing issues, regardless of additional styling.
It would seem to be the case that there is occasionally some extra space between furigana characters, especially at larger font sizes, and with different fonts. This is kind of a nitpick, but it can become something of a nuisance at times, visually-and-aesthetically-speaking. It's entirely possible that I'm not styling something properly or failing to properly account for font customizations; hopefully the images below serve to illustrate the issue that I'm trying to convey:
Anticipated spacing and seemingly appropriate character width, as seen from Browse window (with default Arial font applied to the relevant field):
Anticipated spacing and seemingly appropriate character width, as seen from the Browse window (with Yu Gothic UI Semibold font applied to the relevant field):
Actual spacing and actual character width, with highlights on the individual furigana characters, as seen on the card preview on desktop (with Yu Gothic UI Semibold font applied; perceived extra spacing seems to transfer to mobile as well)
Are there any particular methods for addressing this, or is this a valid issue?