"invalid glyph override" when using unicode characters with display_char in init. txt

[kribjo]

This issue is with version 0.16.1 on Android 5.0.2 (Nexus 7 v2).

I was originally trying to use the "include = old_unicode_glyphs.txt" command in the init file. This did not work because the old_unicode_glyphs file is not included. I put the file there (with root) and tried but then I get the error "invalid glyph override". To make sure it is not a problem with file encodings or similar I remove the include from the init file and add these lines: display_char = wall:9618 display_char = permawall:9619 display_char = wall_magic:9617 display_char = floor:183 display_char = floor_magic:9702 display_char = door_open:39 display_char = door_closed:9724 display_char = trap:94 display_char = stairs_down:62 display_char = stairs_up:60 display_char = grate:35 display_char = altar:31 display_char = arch:8745 display_char = fountain:8992 display_char = wavy:8776 display_char = statue:8 display_char = invis_exposed:123 display_char = item_detected:8710 display_char = item_orb:48 display_char = item_rune:966 display_char = item_weapon:41 display_char = item_armour:91 display_char = item_wand:47 display_char = item_food:37 display_char = item_scroll:63 display_char = item_ring:61 display_char = item_potion:33 display_char = item_missile:40 display_char = item_book:8734 display_char = item_staff:124 display_char = item_rod:124 display_char = item_miscellany:125 display_char = item_corpse:37 display_char = item_skeleton:37 display_char = item_gold:36 display_char = item_amulet:34 display_char = cloud:167 display_char = tree:9827 display_char = teleporter:169 display_char = fired_flask:33 display_char = fired_bolt:35 display_char = fired_chunk:37 display_char = fired_book:43 display_char = fired_weapon:41 display_char = fired_zap:42 display_char = fired_burst:247 display_char = fired_stick:47 display_char = fired_trinket:61 display_char = fired_scroll:63 display_char = fired_debug:88 display_char = fired_armour:91 display_char = fired_missile:96 display_char = explosion:35 display_char = frame_horiz:9552 display_char = frame_vert:9553 display_char = frame_top_left:9556 display_char = frame_top_right:9559 display_char = frame_bottom_left:9562 display_char = frame_bottom_right:9565

These should mimic the old_unicode_glyphs.txt functionality but instead of the expected change if display chars I get this error output on game (not app) start (numbers here are in hex and correspond to (some of) dec numbers above): Invalid glyph override: 2592; Invalid glyph override: 2593 Invalid glyph override: 2591; Invalid glyph override: B7 Invalid glyph override: 25E6; Invalid glyph override: 25FC Invalid glyph override: 1F; Invalid glyph override: 2229 Invalid glyph override: 2320; Invalid glyph override: 2248 Invalid glyph override: 2206; Invalid glyph override: 3C6 Invalid glyph override: 221E; Invalid glyph override: A7 Invalid glyph override: 2663; Invalid glyph override: A9 Invalid glyph override: F7; Invalid glyph override: 2550 Invalid glyph override: 2551; Invalid glyph override: 2554 Invalid glyph override: 2557; Invalid glyph override: 255A Invalid glyph override: 255D

Perhaps I'm trying to do something that is not supposed to work? Is it futile to expect these unicode characters to work on the Android platform? Or is it just a matter of DCSS choking on the system not being able to supply the width of the characters or something similar that might be worked around? It certainly seems Android has these characters available when I use a unicode browser app like https://play.google.com/store/apps/details?id=org.madore.android.unicodeMap .

[kribjo]

Just a note to add the perhaps obvious fact that for the display_char lines which do not give an error the result is as expected with the displayed characters changed accordingly. My earlier post was stating that no change of display chars occur, but that was not my meaning.

[kribjo]

Almost a year later I would like to add that it would be most appreciated with a response regarding if this is indeed a futile expectation ("by design") or if there is an intention for this to work? (Note that I have not tried the "unicode" set glyphs on newer versions since the orignal post above.)

[michaelbarlow7]

Hey man, I haven't really looked at this, but from what I can tell it looks fairly complicated and there doesn't seem to be enough demand for me to actually fix this. Sorry. That said, I'll gladly accept a pull request if someone fixes this. On 6 Apr 2016 6:15 am, "kribjo" notifications@github.com wrote:

Almost a year later I would like to add that it would be most appreciated with a response regarding if this is indeed a futile expectation ("by design") or if there is an intention for this to work? (Note that I have not tried the "unicode" set glyphs on newer versions since the orignal post above.)

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/michaelbarlow7/dungeon-crawl-android/issues/54#issuecomment-205972717

[kribjo]

Just a note for information that this has not changed in most recent (0.22) version. In case anyone with better skill than me cares to try to fix it. :)

[erkin]

I don't know if this helps but I encountered this issue on desktop when my locales were screwed up. Regenerating them fixed it.

[kribjo]

I have actually made some new discoveries about this in my attempts to find a fix. The understandings have mostly lessened my hope though. I'll write a bit more as soon as I can find the time.

[kribjo]

Apparently I never found the time. Sorry about that. And now I don't know what I was thinking about. :(