Deprecate alternate spellings of hebrew characters #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had two alternate spellings largely because there was no mechanism for deprecation at the time. I'm not opposed to maintaining more than one name for a symbol if they're fundamentally different and there's a good reason for it, but different romanizations is many steps too far in my opinion. A similar example came up recently for the Mongolian currency, which you can find references to as tugrik, tughrik, tugrug, togrog, tögrög, and I'm sure even more.
A search for "alef" on arxiv brings up mostly a bunch of results relating to an author with the last name "Alef" https://arxiv.org/search/?query=alef&searchtype=all, while "aleph" has many relevant results https://arxiv.org/search/?query=aleph&searchtype=all (even excluding the matches to "\aleph").
This is similar to the situation with the greek letters, where "alfa" would have been preferred if we want by romanization.
LaTeX uses \aleph, \beth, \gimel and \daleth
HTML uses &aleph, &beth, &gimel and &daleth