Hi Francesco,
To clarify a few points in your message. Xerces-C++ has always been
effectively UTF-16-only. Previously the 16-bit type used to represent
XMLCh was one of several possible types, including char16_t, wchar_t,
uint16_t, unsigned short or unsigned int or possibly others,
On 7/16/20, 9:15 AM, "Francesco Pretto" wrote:
> Are you really sure you want to pursue this direction?
Well, I think there's very little chance, bordering on zero, that if there
isn't the will to actually convert the internals to UTF-8 *now*, there isn't
going to be.
Even so, all it takes a
Migrating XMLChar to char16_t basically means setting in stone and
forever that xerces-c is an utf-16 only library so it's going in a
radically different direction than I was suggesting, so I'm not very
happy to hear about it. I think it can be safely stated that this move
actually closes more
On 7/16/20, 8:07 AM, "Francesco Pretto" wrote:
>Thank you, and thank you for frankness! Probably of the two the utf-8
>for internal encoding would be more oriented towards c++ modernization
>changes, as you said, but probably a big change touching all the code
>base.
It's
On Thu, 16 Jul 2020 at 13:52, Cantor, Scott wrote:
> Look in JIRA if you want to see what's scheduled for it. [...] As for your
> suggestions, unless you're volunteering, you probably need to recalibrate
> your expectations.
>
Thank you, and thank you for frankness! Probably of the two the
On 7/16/20, 5:53 AM, "Francesco Pretto" wrote:
>I notice there is some work towards a 4.0.0 version. Can you point me
>to features that you are planning for this release?
Look in JIRA if you want to see what's scheduled for it. It's primarily C++
modernization changes.
As for your
Hello,
I notice there is some work towards a 4.0.0 version. Can you point me
to features that you are planning for this release? Since XML has been
losing its momentum for years, I suggest the next release to be truly
innovative and helpful for developers to justify the major version
step. This
