tsurukame
tsurukame copied to clipboard
Font Size
I’ve been using your app for quite a while and loved it. I increased the font size to largest size but didn’t see any change. I’m low vision so font size is important to me. Anyway, just this morning, it was like, WHOA! It’s giant! But, the rest is still not correct. I mean, if I made a typo, the info it displayed - the definition and kana are still too small (or remain unchanged.)
![Uploading 5C99884E-A9E1-4723-92CE-79C93D50EF62.png…]
. I use iPad Pro, by the way.
Just wanted to clarify that while font size works great for the main kanji. What I would like to see is ability to change fonts for the rest, such as the meaning and kana, etc. Does that make sense?
Thanks,
Jeremy
Sent from my iPad
On Mar 29, 2020, at 4:55 PM, turtlemaster19 [email protected] wrote:
@sagecedar Yep, that's the font size. We can tell it's an iPad Pro, but I agree the font size setting could be better done. Leaving this open to comments from others...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
@sagecedar Definitely, that's why I don't want it to close, since that screenshot looks awful on the iPad with that font size.
This is due to the implementation in #294
Totally agree. On an iPad pro's large screen, the text is illegibly small at times. I can read the English, but cannot make out the complex Kanji, especially with the low contrast red on dark grey motif.
For size comparison, look at the clock and "< Back" button in the upper left. These are the smallest fonts generally used on iPad – and only in this simple case for controls which should not get your attention.
The main font for this app is smaller than the "< Back" button. For iPad pro, roughly double would be considered normal.
For comparison...
By the way... another font size slider probably isn't needed, as most apps don't have one. Just make the default text size relative to the screen size...
PS: I know the blurred out text is intentionally illegible in the first screen shot. I wasn't referring to that :-)
@sagecedar I noticed that the text is seems more legible with the "light" theme. This might be a quick improvement for you :-)
@jeff8v7 I don't think that makes much of a difference. :P
Really? My eyes must be pretty bad..
@jeff8v7 I finally saw what you meant when I tried it on my phone without glasses today. I couldn't say it was super noticeable on the iPad, because the screen size was so large, that the effect was diminished. (Maybe that's just because I am nearsighted...)
Those are some good points you made, and I hope that we can fix this soon...
Bumping this up - I use Tsurukame on an iPad mini and the text is tiny. I made the text size bigger in the iPad settings but Tsurukame doesn't seem to respect this as it has no effect (I've noticed it changes the text size in some but not all apps). I don't really care whether Tsurukame respects the iOS text settings or has its own setting but would be really great to support larger text throughout the app.
The font size setting seems to apply to the item being tested only. On a large iPad, the item is actually uncomfortably large, while all other text is uncomfortable small.
On Apr 13, 2021, at 2:53 AM, Aaron Meyers @.***> wrote:
Bumping this up - I use Tsurukame on an iPad mini and the text is tiny. I made the text size bigger in the iPad settings but Tsurukame doesn't seem to respect this as it has no effect (I've noticed it changes the text size in some but not all apps). I don't really care whether Tsurukame respects the iOS text settings or has its own setting but would be really great to support larger text throughout the app.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Is it possible to utilize Dynamic Font features? So that any text can be dynamically scaled using built-in a11y features of the iOS? I found some related article: https://mobilea11y.com/guides/swiftui/swiftui-dynamic-type/ I could give it a try with the support from the authors (because I have no experience in iOS development, only web-dev).
@geerk We do some of that already.