1
Bugs and Issues / Re: Document generation broken in v16.1
« on: January 27, 2025, 09:23:54 pm »
After fiddling around with templates for many (>20) years, almost dealing with workarounds for unexpected rendering results.
I recently gave up moving towards v16.1, again.
Besides being restricted to letter size pages, Sparx's EA is not able to render German characters, at least on fields like {ElemTest.Notes} or {PackageGlossaryMeaning} and, perhaps others. I see them rendered escaped (ä) or escorted by curious switching of font styles and -sizes. Maybe the root cause of other effects as well.
And now again, no surprise, with v17.0.1704 Sparxs introduces new varieties: Header and Footer are not rendered any more, unless a cover page is defined.
To make it clear: Linear RTF/PDF documents are still the most important interface between me and my customers and will be. THEY ARE NOT A NICE TO HAVE!
So: Should I stay with Sparx/EA? 6 license renewals later we're still stuck with Version 15.2 and 32-Bit.
Gruß
Jens
I recently gave up moving towards v16.1, again.
Besides being restricted to letter size pages, Sparx's EA is not able to render German characters, at least on fields like {ElemTest.Notes} or {PackageGlossaryMeaning} and, perhaps others. I see them rendered escaped (ä) or escorted by curious switching of font styles and -sizes. Maybe the root cause of other effects as well.
And now again, no surprise, with v17.0.1704 Sparxs introduces new varieties: Header and Footer are not rendered any more, unless a cover page is defined.
To make it clear: Linear RTF/PDF documents are still the most important interface between me and my customers and will be. THEY ARE NOT A NICE TO HAVE!
So: Should I stay with Sparx/EA? 6 license renewals later we're still stuck with Version 15.2 and 32-Bit.
Gruß
Jens