If I have two pointers pointing to the same string, Cartographer gives me two copies of the string. If I have one pointer pointing to a string and a second pointer pointing to a word within that string, Cartographer gives me the entire string from the first pointer and then an extra copy of the same string starting from the second pointer. I can sort of detect the first case by examining the comments (e.g. //POINTER #0 @ $0 - STRING #0 @ $0 and //POINTER #1 @ $2 - STRING #1 @ $0 are clearly two pointers pointing to the same string), but if the source text is compressed in any way (even just DTE) there's no reliable way to detect the second case from the output.

UHR (which rather spectacularly fails to install on my new computer) uses different syntax but does essentially this for the first case:

#W16($0)
#W16($2)
This is a string.<END>

and this for the second case:

#W16($4)
This is a string that says
#W16($6)
"BOO!"<END>

On the other side of the coin, is there any way to show gaps in an otherwise continuous block of text? I have at least one string that appears to have been prematurely terminated, and the extra bits don't show up in the output. UHR does that case something like this:

#W16($8)
This is a string that ends.<END> But there's still extra text that's just sitting here without anything pointing to it!<END>

Are these things that Cartographer can do? #METHOD: POINTER and related all seem to start from the pointer table and add the text, so I'm guessing the answer is no. I'm looking for something that starts from the text and adds pointers. I haven't seen Cartographer's code, but I suspect that kind of a change would be fairly fundamental. If they turn out to be easy to add, does anyone else think these would be useful features? If not, does anyone know of another utility that will do what I want? Or maybe I should just spend more time convincing UHR that my computer isn't that bad a place to hang out?

(Yeah, I know I can just RAW dump the pointer table and text in straight hex and then do the string length comparisons myself, but that's annoying. Also, I like Cartographer enough to want it to be even better  )

Those would be awesome additions. It would be kinda cool if it also could detect pointers that pointed to separate but identical strings and let you know. The program is amazingly helpful though, I love it and use it all the time.