Last modified: 2011-09-19 04:26:54 UTC
It's quite unintuitive that Gardiner codes will only be interpreted if
capitalized. Using capital letters for the default is a particularly odd
choice; in the short example A1-B1-!-C1-D1, the shift key must be pressed and
released five times, which is likely to introduce frequent typos (1 <-> !, - <->
_, etc.) as well as aggravate RSI, bad for accessibility. It's like CamelCase
but worse. If lowercase codes were allowed, one could quickly type
a1-b1-!-c1-d1, pressing ''shift'' once.
(Why all these hyphens, anyway? Spaces are easier to read. And wouldn't it
make more sense to use actual newlines for new lines?)
Removing parser keyword, this is an issue with the extension and not the parser.
Could this not be easily fixed with strtoupper() some where (if it is still an issue)? Or am I missing something?
strtoupper() will only work for main hieroglyph codes but not for aliases, e.g. <hiero>A</hiero> and <hiero>a</hiero> produce different hieroglyphs, G1 and D36 respectively. So what can we do here, stuff like a1 --> A1?
Going ahead and closing it. We can't make phonemes case-insensitive, so establishing this rule just for hieroglyphs will be extremely misleading. All sources on Gardiner's list use upper case anyway.
The legalisation of spaces as delimiters will be addressed shortly in my tokenizer rewrite, I'll also consider making newlines work, but only if it will not break existing texts.