Funny timeline and hilarious CEO post:
https://forum.xojo.com/t/unicode-characters-on-pdf/74570
That thread started in February 2023!
1 year later
After the second post is amazing.
OMG a second “1 year later“. ![]()
This is why what they have have just hooked into an open source library so more features would there and just write an Xojo API for it…
- Karen
They could hav adopted library pretty easily and just skipped writing all their own code
And that is not even the only alternative they could have used. This shows that they really in a problematical situation: their Idea of writing software is not following the most simple way but the most terrible CEO ideas. This males it a problem to workout stuffs like pdf. In fact they have no idea how to get to the success they want to have.
it’s 2025 and they cannot unicode? Wow, that’s a professional tool for 1K bucks per year.
WTF!
Solution: MBS Addon or helper app, Why this sounds so familiar to me. For over 10 years the same lame excuses.
That’s why I can only tell to the people: change your development environment. I for example had to suffer exact one time their policy of changing things which they promised different to handle. That resulted in a vaadin WebApp. And what shall I say? The Vaadin App is much more powerful and can handle more stuffs, can use the entire ecosystem of Java. Their Idea of Software are different to the Idea professional devs have. They make it like they want it. All time different.
The PDF development in Xojo is over.
They invested time and got quite far.
anyone needing more already moved on. Whether they use Einhugur plugins, MBS plugins, some external app like a python script, latex or even some open source pdf class for Xojo. Or maybe even call to java stuff or some microservice.
Beside proofing they can do it, there is nothing for Xojo inc to win. They got PDF already on the feature list. Implementing Unicode will not make one more license move. And users in America will not run in an issue as they may never miss Unicode characters.
Don‘t Americans use emojis? ![]()
Not4 in XoJo based PDF
seems the wait is over !
The wait for someone else to do it was over long ago IF a person was OK with third party code
MBS has had full support of all these features for many years
I think the real question was “When is Xojo Inc going to add this to their offering ?”
And the answer seems to be they’re not going to any time soon
That is unless you want to donate your work to them ?
Thanks for your work as this is yet another option along with MBS, Einhugurs & a couple other means people have created (wkhtmltopdf etc)
Options are nice to have
Yes, Xojo needs to be appreciative of the community who provide third-party solutions, to fill in Xojo’s gaps. Whether they are, I’m unsure. They’ve already given Sam the shaft.
TBH building a community isnt something they ever worked hard at
Its not JUST users but add on vendors like MBS, Einhugur, users, consultants and so much more
MS got that and its what made VB such a big hit
Heck places I worked where we used it spent way more on all those add ons than they ever did on VB and it helped driver the community & expanded the use of VB like mad
I’ve never understood Xojo’s unwillingness to invest in building that kind of community
Which is exactly why I suggested they make the third-party developers shareholders with Xojo concentrating on what only THEY can improve (the core product) instead of producing half-baked “controls and features”, and the third party developers doing what they do best (dealing with the rest that Xojo has neither the manpower nor the expertise for). Best of Both Worlds.
Could have saved Xojo but for the CEO’s ego.
If y memory serve, there was a (multiple) beta (s) years ago, and one day… no news since.
The rule of thumbs is: “never wait”.
All I wanted was to update and improve their Mac framework, making better Xojo made apps and helping to make them more modern (ScrollView has been around 20+ years), and competitive. Y’all know how that panned out.
Exzellent initiative and great work, @JeanYves !
This does unfortunately not repair Xojo’s genuine lack of Unicode support. This was the first thing I stumbled upon when evaluating Xojo, and Xojo Inc’s workarounds and negligent behaviour regarding the issue were telling.
From a modern programming language I expect native Unicode support, like in Swift.
it’s even getting more worse when you consider how old unicode is ![]()
