🚀 go-pugleaf

When editing a structured document in FM7, I encountered a very strange bug: Importing any kind of TIFF or JPEG image by a graphics element works fine - in principal.
Problem #1:
The document contents changes, some graphic imports are obsolet. FM does not manage to remove the corresponding !ENTITY ... - definitions in the header, but instead removes all lines defining a NOTATION instead when saving the file. Result: Parse error when reopening the file. Weak workaround: After inserting the missing NOTATION line by text editor, the document can be reopened once but will be destroyed again the next time. Strong workaround: Remove all unused ENTITY definitions by text editor, restore notation lines.

Problem #2: Until today I thought that I can fix all those errors by removing unused entities, but unfortunately, it does not work for one special document! Even more strange: Everything seems ok up to a certain number of image references. This number cannot be exceeded, but if you remove an arbitrary ENTITY definition (along with the using element of course), the error does not show up. For the mentioned document, the error is most obstinately reproducable such that 12 (no joke!) or less ENTITIES are ok but any more brings up the error.

After trying several hours to find another workaround, I got it: There seems to be a problem with the length of the path name where the images are located. Using no path at all or path name with only one character, everything is fine. Using longer path names, even only 8 characters, immediately leads to the error. As I was successful in the past by removing unused entities, I now believe that there is a total limit of space for all names that is responsible for the error (or what special 'design pattern' ever may have been implemented there ...).

Can somebody please tell me how I can make sure that this bug will be fixed most urgently because I am really upset that a professional-price product teases its users with such beginner-style programming bugs.