Last modified: 2011-09-19 04:26:54 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1005 - Gardiner codes in WikiHiero are case sensitive
Gardiner codes in WikiHiero are case sensitive
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
WikiHiero (Other open bugs)
unspecified
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-12-05 04:55 UTC by Leah
Modified: 2011-09-19 04:26 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Leah 2004-12-05 04:55:59 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?)
Comment 1 Ævar Arnfjörð Bjarmason 2005-06-21 14:06:03 UTC
Removing parser keyword, this is an issue with the extension and not the parser.
Comment 2 Micke Nordin 2009-05-08 13:23:10 UTC
Could this not be easily fixed with strtoupper() some where (if it is still an issue)? Or am I missing something?
Comment 3 Max Semenik 2011-09-04 10:38:10 UTC
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?
Comment 4 Max Semenik 2011-09-19 04:17:01 UTC
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.
Comment 5 Max Semenik 2011-09-19 04:26:54 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links