Hi Michael;
The message was meant for some other committer that may want to try it.
We could change it fairly easily for all UNIX/Linux variants.
OTOH, we may want to keep consistency in the Windows port as well.
Maintaining compatibility with the local python is not as important as
keeping comp
Hi Pedro,
Thanks for your reply.
I have given up trying to build this myself, because I kept running into
cryptic errors. So, I was kind of hoping that the change could be built
into the configuration for generating the AOO debian packages (which
work fine).
Best, Michael
On 10/03/16 03:00
FWIW,
On FreeBSD we use UCS4 too, but it doesn't matter much because we always use
the system python.
The change should be trivial, just add the enable flag to
CONFIGURE_ACTION (line 76)
in main/python/makefile.mk.
I have no time for testing though.
Cheers,
Pedro.
--
FWIW,
On FreeBSD we use UCS4 too, but it doesn't matter much because we always use
the system python.
The change should be trivial, just add the enable flag to
CONFIGURE_ACTION (line 76)
in main/python/makefile.mk.
I have not time for testing though.
Cheers,
Pedro.
---
Hello,
On Debian and AFAIK all other major Linuxes, Python is compiled with
--enable-unicode=ucs4
From my testing of the Python bundled with AOO, it uses UCS2 rather
than UCS4. Any chance that the above compilation flag could be used?
That way, it would be easier to use python libraries insta
