But isn't this only a partial solution? There's currently no way to export aparatus symbols correctly in unicode, and not even as non-unicode unless one first manually installs Accordance fonts into one of the fonts folders. It seems to me the unicode way long has been, and will certainly be, the way of the future. I think Accordance should develop a set of high quality unicode fonts that get installed as part of Accordance installation, rather than leaving it for the users to hunt down suitable fonts. And I do not think the Font Fixer is a solution either. If I remember correctly, the Font Fixer was first released to address a problem that showed up a few versions ago. I had hoped to see the root cause of the issue dealt with, rather than keeping alive the workaround for the problem.
The issue in the original post seems to be related to how text is exported from Accordance via RTF flavors; one which has been reported before and is on the list to be addressed.
Regarding Unicode, unless I'm mistaken, there are code points that support all the sigla used in text criticism. Whether there are free fonts that map these to the correct characters is another story. I believe Cardo and SBL Hebrew probably are the best free ones for Hebrew (others in the field can verify exact mileage). Whether we should bundle these in the app, or provide better support for the use of Unicode export from Accordance seems to be a separate discussion. I can see how it might help, but ultimately it's the user's preference as to what fonts they want to use. But, I admit it can be confusing and we could probably help in the process; just don't know exactly what that looks like at this point.