DMX 5.3.4 has been released at Feb 22, 2024. The DMX Webclient now has dedicated emoji support: on all major platforms and browsers emojis are rendered nice and in color.
Extensions of the plugin development framework made it possible to offer 2 more DMX plugins (optional installations). These offer fulltext search for PDF files. For scanned image-only PDFs the Tesseract OCR engine is integrated.
For detailed information about this release see the Changelog.
Thank you @jri for your continued good work. I just upgraded my DMX instance to the new version. There is a problem rendering topics in the web client, see GitHub issue. @jpn
Confirmed! Since DMX 5.3.4 in conjunction with its emoji support there is an issue with canvas rendering. Your screenshot shows that erroneously different fonts are used for both the topic header and the topic content:
The problem is that the header is rendered before the proper web font (“Ubuntu”) is loaded. For the body he problem does not occur as a different rending approach is used there. For details see:
I’ll fix this very soon and release DMX 5.3.5 then.
@RalfBarkow meanwhile I did some examination and can say it’s not a synchronization issue as I thought (rendering before font is loaded) but a browser-specific problem (related to Web fonts, SVG-images, data-URLs, HTML5 canvas).
In my environment, with both Firefox 126 and Chrome 125 on macOS 10.15.7 the problem does not occur. Note that same font (“Ubuntu”) is used for both topic header and topic body:
I can reproduce the problem with Safari 15.6.1 (on macOS) though:
But still it looks a bit different than your screenshot, in particular the dots in the topic header:
What browser and OS did you use? Can you try different browser?
I’m still tracking down the problem and try finding a fix.
DMX 5.3.4’s topic label rendering problem is now fixed. It works properly in all browsers now. Here Safari 15.6.1 on macOS. Note that the same font is in effect for both, topic label and topic details:
Or you can try our DMX dev-installation (login as admin w/o password): https://dev.dmx.systems
The problem was related to the SVG engine of certain browsers in conjunction with web fonts. Within a SVG image some browsers does not render text using web fonts but fall back to another font installed locally. They do this for security reasons as a web font is an external resource, possibly retrieved from non-trusted origin. Since DMX 5.3.4 the Webclient utilizes a web font for all text rendering.
The solution was to refactor the DMX topicmap renderer in a way no SVG rendering takes place at all. Instead the topic label (and icon) are now rendered as DOM, just like the topic details.
Please test the fixed topicmap renderer and let us know if you notice any problem or oddity. Also open the browser console to lookout for error/warning messages.
