Sorry, I haven't had the time to look at this recently - been busy travelling and then with other (non-Pleco related) mini-projects.
No problem, I just wanted to make sure it's not forgotten
EDIT: Just finally got around to testing the .pqb version and for some reason it lacks tone indication completely for me (neither numbers nor diacritics). Can't quite pinpoint why because I can't inspect the code by trying to edit a card anymore.
I don't think we'd make them official Pleco dictionaries unless/until we add official support for the relevant romanizations to Pleco, which is unlikely to happen for at least a year. In fact it's likely we'll have the ability to add searchable custom fields to user dictionaries before we support any new romanizations officially in our own dictionaries. Only MoE thing we're likely to release officially in the near future is LACD.
I see, it's understandable (although regrettable from my perspective of course) that Minnan support isn't your top priority considering that the demand for other things is higher.
There is one thing I noticed recently though: Pleco converts numbers to diacritics even if the field text has "@" prefixed to it (so "@ting1" is displayed as "@tīng"). This is somewhat unfortunate for this dictionary project because the tone diacritics in Minnan are in most cases not the same as in Hanyu Pinyin (the macron marks the 7th tone for example). I thought the point in using the "@" prefix was to prevent Pleco from interpreting the field as Pinyin and applying conversions accordingly. And indeed, it does do that for all other Pinyin correction rules, just the tone conversion is still applied. Is that intentional? And if so, what is the reason for it? Would it be possible to turn that off (or add an option to do so) in future versions?