Neat idea but completely unusable on Firefox mobile due to the context menu that pops up whenever text is selected and obscures the site's menu that does the same.
Show HN: unicode.style
51–60 of 70 posts
Re: Show HN: unicode.style
#52Neat. Suggestion: maybe don’t “underline” characters such as y or g
Re: Show HN: unicode.style
#53There is something about rendering these unicode code points that seems to make Firefox jank more than usual (when scrolling this page up and down). Are rendering these code points especially costly for some reason?
Re: Show HN: unicode.style
#54On iOS, the selection popover interferes with the one you designed.
Good point. I’m planning on implementing a static (always-enabled) toolbar for mobile devices — hopefully that’ll make it better.
Maybe if your options appeared below the selection rather than above they wouldn’t interfere.
Re: Show HN: unicode.style
#55This is entertaining but it's completely broken on Chrome mobile in a way I've never seen before.
Re: Show HN: unicode.style
#56Screen readers don’t do very well with this, so please only use it for novelty purposes. Otherwise you will unnecessarily be locking people out from what you write.
To be fair, combining some of the HN comments: $ python Python 3.7.0 (default, Jul 22 2018, 21:11:34) [Clang 9.1.0 (clang-902.0.39.2)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import unicodedata as ud >>> ud.normalize('NFKD', '''It's a kinda ascii-art thing that 𝔩𝔢𝔱𝔰 𝔶𝔬𝔲 𝔞𝔫𝔰𝔴𝔢𝔯 𝔥𝔫 𝔠𝔬𝔪𝔪𝔢𝔫𝔱𝔰 𝔞𝔩𝔩 𝔣𝔞𝔫𝔠𝔶 𝔩𝔦𝔨𝔢 𝔱𝔥𝔦𝔰. 𝕆𝕣 𝕝𝕚𝕜𝕖 𝕥𝕙𝕚𝕤 𝕚…
As a counterpoint, selecting that text and choosing “speak” from the pop up menu doesn’t speak that text on iOS.
VoiceOver on iOS doesn’t speak it, either.
Re: Show HN: unicode.style
#57I'm having trouble understanding what this does. Apparently there's a popover when you select the text you typed. I had to go to https://github.com/ekmartin/unicode-style to figure this out.
Also seems to support the "standard" shortcuts for formatting (Ctrl+I/U/B, perhaps others), but yeah, the introduction might be lacking.
Re: Show HN: unicode.style
#58Earlier quoted context omitted.
It’s really not a screenreader’s job to guess what a character might be being pressed into service to represent in a given scenario, and to try to work out when that’s inappropriate and it should be using the original specified meaning.
Well, it kind of is. In my mind, a screen reader should read anything that a healthy human can. Ideally even text in images and any sort of weirdness.
Then again different healthy humans read texts differently. There's no such thing as a canonical reading and any reading bring in prior semantics.
There was a sign posted in the break room of a lab I used to work at. It read, " is easy for you to read, but not for everyone. Volunteer to read for the blind." It was a good double whammy.
Re: Show HN: unicode.style
#59Is it just me, or does the BB style render the most interesting characters as rectangles? (Chrome on OS X)
𝔸 𝔹 𝔻 𝔼 𝔽 𝔾 𝕀 𝕁 𝕂 𝕃 𝕄 𝕆 𝕊 𝕋 𝕌 𝕍 𝕎 𝕏 𝕐
Re: Show HN: unicode.style
#60Earlier quoted context omitted.
That really has to get fixed though.
It doesn't and shouldn't. The whole point of having Mathematical Alphanumeric Symbols as separate unicode code points, rather than just using normal latin characters with style markup, is so they can be used when the different letters have semantically different meanings -- in particular in maths when 𝘹 and 𝘅 can be in the same formula, representing different concepts. They're not a replacement for style markup. In…
How do screen readers handle other aspects of mathematical equations? For example, if I have an equation like "A equals B to the C", how do I represent this such that a screen reader will say it correctly? As far as I can tell, I can't.
I see the FAQ you linked states that I'm supposed to use markup for this. Unfortunately, that means the screen reader needs to understand math markup to work correctly. If that's the case, it seems like we could just include other concerns like Bold X vs X in the math markup as well.