141–150 of 172 posts
HN is a plain-text site, so we originally buried this. But then we got an email we couldn't refuse (see below). So have at it. All: Please don't submit stories with non-plaintext titles, and please don't post non-plaintext comments in other threads. Thanks! ------------------------------------- 𝕀 𝕣𝕖𝕔𝕖𝕟𝕥𝕝𝕪 𝕡𝕠𝕤𝕥𝕖𝕕 𝕒 𝕡𝕣𝕠𝕛𝕖𝕔𝕥 𝕥𝕠 𝕊𝕙𝕠𝕨 ℍℕ, 𝒶 𝓌ℯ𝒷𝓈𝒾𝓉ℯ 𝓉𝒽𝒶𝓉 𝒸ℴ𝓃𝓋ℯ𝓇𝓉𝓈 𝓉ℯ𝓍𝓉 𝒾𝓃𝓉ℴ…
𝒞ℯ𝒸𝒾 𝓃'ℯ𝓈𝓉 𝓅𝒶𝓈 𝓊𝓃 𝒻ℴ𝓃𝓉
This is (ab)using unicode, for example the F is actually a Mathematical Bold Fraktur Capital F: https://www.compart.com/en/unicode/U+1D571 This is terrible for screen readers and the like which are unable to read or understand these unicode characters making accessibility a real concern.
> This is terrible for screen readers and the like which are unable to read or understand these unicode characters making accessibility a real concern Yes, Firefox for Android doesn't render it properly.
Interesting, looks like Firefox automatically resolves these to the real letters in the address bar, but leaves them as is for google search. Nice job aggregating these into an easy-to-use font.
I'm guessing you mean on a desktop? On my Android phone, Firefox renders each letter as a grey box. Had to switch to Chrome to see the actual text :(
Earlier quoted context omitted.
> This is terrible for screen readers and the like which are unable to read or understand these unicode characters making accessibility a real concern Yes, Firefox for Android doesn't render it properly.
Here it works fine, what do you mean?
Earlier quoted context omitted.
I'd kind of expect screen readers to be able to apply Unicode compatibility decomposition http://unicode.org/reports/tr15/#Canon_Compat_Equivalence since there are many characters that are just visual variants. Ligatures like ffl or the like are at least somewhat common e.g. in PDFs. On the other hand, maybe that breaks other stuff and only whitelisted characters are converted. Maybe a HN reader using a screen reader c…
That implies that PDFs work with glyph indices, not Unicode code points. How do PDFs work for shaped languages like Hindi? In a script like that, you may have glyphs without any corresponding Unicode code point. Or does the PDF perhaps store the original unshaped text?
However, few PDF generators do this, and not all PDF readers have good support for it. So results vary depending on the specific tools and use-case.
Earlier quoted context omitted.
I'm guessing you mean on a desktop? On my Android phone, Firefox renders each letter as a grey box. Had to switch to Chrome to see the actual text :(
Seen a few comments like this. Old Version of Android? Because my FF on Android 8.1 renders it flawlessly.
Earlier quoted context omitted.
It's less "can they render them" and more "do they maintain their meaning in alternate renderings". For example, it's common in these to use non-latin characters that visually resemble latin characters. But if you were to try and substitute them literally, either as their actual phonetic sound, or a latin equivalent that is semantically similar but visually different, you risk breaking the meaning. It's a bit like wh…
>It's less "can they render them" and more "do they maintain their meaning in alternate renderings". I just entered "this is a test" on the site in Safari and enabled VoiceOver. It reads it as "Mathematical Bold Fraktur Small t. Mathematical Bold Fraktur Small h" and so on. Completely broken for those who rely on VoiceOver as a screenreader.
You can use this as an example: ěščřžýáíasdfghjk