Website: Request to avoid look similar characters in the generation of a URL for a route

there are many of us who’s eyesight is pretty good but not what it used to be.

Is there any way to request that the generated URL shortcut for a route
avoid the “look similar” characters of:

The above request would aide readability, avoid much confusion, while still leaving a vast universe of character permutations to draw from.


Thanks for the proposal, that is indeed something I wanted to have a look at as well.

I think we could avoid to use “I” (i) and “l” (L) and also 0 and O.

I am not sure if we should also do this for “i” and “j” or “g” and “q”?

Such a small thing but so much impact! What a great suggestion

1 Like

My experience with some devices and fonts I am forced to use is…

  • lowercase “l” / number “1” / Capital “I” all can be confused with each other
  • upcase “O” / number “0” / lowercase “o” all can be confused with each other
  • lower “i” and lowercase “j” are “skinny” and have a dot, if font is small thats all the eyes see.

Boldtrn suggested lowercase “g” and lowercase “q”
I have not seen this to be an issue but if others have this issue
then yes, include these in the radioactive character set.

Assuming all ten of the above characters are made radioactive
that still leaves 52 other characters legal.

abcdef h k mn p rstuvwxyz


Thanks for the nice idea. I updated the service to not use:

  • I1l
  • O0o
  • ij

If there is anything other character that we should change, please let me know. This doesn’t change exiting urls.

1 Like

I had reason to generate 4 URL’s today.
All four were devoid of the look similar characters.

The above limited test appears to confirm success of the code change.
Thanks again.

1 Like