Good improvements so far.
We only discussed a few options. I think it would be a good idea for you to go through and expand upon the functionality of rest of the options in the same manner. I could generate the same type of questions for most other options since there is no details about what they do specifically. Unfortunately, I don't have any time to go through further specific items as it was some time ago that I studied Kruptar and I only had notes of certain cases.
Both pointers should have the same format.
Right, that's one big area where Kruptar is no good for me. This basically a two-level pointer hierarchy. Often pointers to pointers are not the same format. In fact, there are typically even more levels of pointers to get to the text (say 3 or 4 levels). In addition, the end result may not be an individual string at all, but a string table (group of strings with no individual pointers). Kruptar does not handle string tables in a 'ptPtrToPtr' type context. It will only handle string tables one by one as a group each as far as I am aware.
When I insert scripts like this, I need all pointers in the hierarchy (sometimes of several different formats) to be updated accordingly. These are items that are a little more 'fancy' that I refer to, but very common for me nonetheless. Kruptar is good at abstracting basic individualized string and pointer tables, but it starts to fall short when the organizational structure becomes more complex. Some concepts like 'ptPtrToPtr' are a good band-aid way to add some support for these types of things, but it quickly becomes limited.
Where I have tried improve upon Kruptar is taking the 'Group' concept farther. There needs to be more building blocks and more levels (beyond just one level Groups) to be able to build more complex structures. If only Kruptar was open source, I'd probably have built upon it rather than start another utility.
Supports multi byte and multi character entries, \n sequence, no linked entries and control codes.
Since you mention Cartographer and Atlas by name, you might want to mention the differences and things Kruptar does not do that they do such as the linked entries and what not.
Pascal strings are perfectly handled by standard plugin, which is always distributed with Kruptar. You just need to choose it in grPlugin.
I don't believe so. Since there is no string terminator, how can Kruptar know if is a pascal style string or terminated string? Secondly, pascal style strings can come in two flavors where the length byte itself may be included or not included in the length. Also, the length 'byte' may actually be multi-byte in some games. It would be impossible for Kruptar to handle these situations without some specific configuration settings for these items so Kruptar knows what to do.
It seems like the last version of Kruptar was from 2011. Is it dead?