Hacker News new | past | comments | ask | show | jobs | submit login

> a simple reference input string, examples of how it gets broken, and what to do to fix them.

I really like this idea. Just have a standard set of strings covering all edge cases (even the sprawling labyrinth that is bidi) with a visual reference that shows how the correct rendering of each string would look like. Each entry would also have a description of the problem and suggested solutions.

Unlike the solutions in OP, this one is pragmatic and is actually actionable for the vast majority developers. I'm kinda surprised that something like this doesn't already exist given the substantial amount of material and visual examples already available that covers the bidi algorithm.

- https://www.w3.org/International/articles/inline-bidi-markup... - https://www.w3.org/International/articles/inline-bidi-markup... - https://www.w3.org/International/articles/inline-bidi-markup...




I'm not sure I understand the idea. It sounds insane to me because I feel like there's probably trillions of combinations (and it would be insane to expect to be able to cover every specific example of incorrect text), and I thought the website was pretty clear and provided good examples.


As I understand it, the idea is just to make an Arabic test suite with enough examples (maybe a few dozen to a few hundred) such that if your program correctly renders all those examples, it’ll probably work fine with most Arabic text found in the wild. It sounds like there’s a lot of very broken software out there. Testing any Arabic input would be a big improvement for a lot of software.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: