https://dgcommunity.pulsemicro.com/topic2470-fonts-coming-out-missing-stitches.aspx Tajima DG by Pulse Community - DG16 Bug Reports - Fonts coming out missing stitches - Messages en-us http://blogs.law.harvard.edu/tech/rss Jitbit AspNetForum Mon, 01 Jun 2026 15:08:18 GMT Mon, 01 Jun 2026 15:08:18 GMT https://dgcommunity.pulsemicro.com/topic2470-fonts-coming-out-missing-stitches.aspx KJDAF3df this issue should be resolved in the latest official maintenance release 7683. Please let us know if that's not the case.]]> Mon, 01 Jun 2026 15:08:18 GMT https://dgcommunity.pulsemicro.com/topic2470-fonts-coming-out-missing-stitches.aspx
Same issue with ROMAN 3 font, see the G below.

]]> Mon, 01 Jun 2026 09:29:39 GMT https://dgcommunity.pulsemicro.com/topic2470-fonts-coming-out-missing-stitches.aspx MrLogoSD. There was a bug in the software that caused the "J" in the font Jiggles to not generate in 7683.


This will be corrected in the next maintenance release.


Please try our fonts page to help with your project: https://www.tajimasoftware.com/dg-fonts]]> Tue, 19 May 2026 20:37:04 GMT https://dgcommunity.pulsemicro.com/topic2470-fonts-coming-out-missing-stitches.aspx
I've reported this before here, but didn't have the proper file as proof. It just replicated today and here is the file. We are making a catalog page to demonstrate our font capabilities, and while copy pasting the HEARTS font above it, when we Modified Text it came out like this below. Nothing I do will fix that segment besides erasing it and restarting. I fear the file itself gets corrupted so I have to start over from the beginning, but thankfully this wasn't much, and there was no data lost in this case, but during my first report, data was lost and I had to replicate it by memory, which is not ideal. The solution given last time was to try and place the fonts in their native size based on the font catalog, but this was done on it's native size when it is first generated. No changes to size have been made.

Edit 2: I just went back and deleted the segment, and did it from scratch. Not a copy paste this time and the issue replicated. So yes, my original belief that the entire file is now corrupted seems to be true.

Edit 3: It's permanently corrupted now, I think because I saved it to provide here as proof. Prior to this it would just revert back to normal as long as I did not save it. Restarting the program did not fix it, nor did restarting my PC.

edited by MrLogoSD on 5/19/2026
edited by MrLogoSD on 5/19/2026
edited by MrLogoSD on 5/19/2026]]> Tue, 19 May 2026 19:47:48 GMT