On 2012-10-01 13:58, Michael Stahl wrote:
On 01/10/12 13:25, Michael Meeks wrote:
The only problem with a change there is our ABI - which explicitly
exposes the encoding of that.
the right time to do it is for LO4. sadly nobody has signed up for that
yet :( ... (while there are volunteers for far sillier proposals, like
getting rid of com.sun.star...)
Perhaps we need to split out some preparatory tasks?
For example
- fix code that directly accesses the underlying buffer
- create an external iterator class (which would currently be a thin
wrapper around int) for looping over the buffer and indexing into it
- fix code that indexes into an OUString to use the new external iterator
Once those tasks are taken care of, the actual conversion to using UTF-8
internally will become a great deal simpler.
Disclaimer: http://www.peralex.com/disclaimer.html
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.