I spent too much time on a decent C# MVP (model-view-presenter) pattern based application framework. It's a struggle to be a good software architect when you're on the learn it yourself program with no formal education or mentor on the matter. I'm still not sure how well the framework will scale, but I gave it a best shot. My error manager and handling framework needs some work for sure, but I'm not really sure how to do it better. Any C# professionals out there with MVP design pattern experience?
I started beefing up my table library to support all the features that have been discussed for
the standard. Supports flexible formatting (\n\r\t), end tokens, linked entries, and UTF-8 just fine.

I've been been testing it and it's working well so far. It ignores lines it doesn't recognize as supported features and errors out on those that should be supported, but are malformed and unable to be parsed. I thought that was a better approach than spitting out errors on any table that might contain a dump bookmark or other unsupported feature. Both Unix and Windows newlines are supported OK too I think.
I am working on incorporating support for Atlas's address modes (LoROM00, LoROM80, HiROM, GB, Linear).
I'm likely going to have selectable encoding so scripts/tables can be ASCII, S-JIS, UTF-8, or EUC. UTF-8 will be the default.
I've got a host of other potential features I'd like to have for the dumper when I get into it soon. But, I'm going to start small. I'm not sure how much time I want to invest in this.
While it will have Atlas compatible output, I'm trying to have an Inserter built-in as well. Though figuring out the logistics for an equally flexible inserter on par with Atlas is difficult. It may end up with Atlas only output at first and decide if it's worthwhile to develop further.
So, things are moving along. I'd like to get back to progress on Tenshi soon. I haven't been able to touch it since March which spurred my need for better 'universal' approaches and tools.