DaleStan wrote:The biggest issue, as I see it (stop me if I'm way off here) is the not-entirely-obvious mix of Latin-TTD and UTF-8 with TTD private characters.
Therefore, the most necessary feature in an NFO editor is the ability to handle this weird encoding properly. Better would be one that can save strings that fit into Latin-TTD as Latin-TTD, instead of a simplistic always-UTF-8 scheme.
A custom-built editor could do this, but it seems rather like at least re-inventing the wheel, if not reinventing the square wheel. There are editors that provide massive scripting power, and I would say that one or more of them, fit with the appropriate script(s)[0] would be the best solution. I suspect that (X)Emacs would provide the scripting power necessary to make that happen, but I don't know enough about it to be sure.
[0] I'd say that it's only necessary to parse actions 4, 8, B, F, and 13 for string conversion.
It would be really useful if someone would provide a customisation for some editor to edit NFOs
I'd with pleasure use it if the editor would support (a must list):
- multi-line simple/regexp find and replace
- vertical blocks select/copy/cut/paste with keyboard
- remembering the last edited position on next open