Herbert Duerr wrote:
Stephan Bergmann wrote:
Herbert Duerr wrote:
To support characters outside of the unicode base plane I'd like to add a
new sal_UCS4 type to OpenOffice.
[...]
See the thread at
<http://www.openoffice.org/servlets/ReadMsg?listName=dev&msgNo=18462>
for ideas how to change interfaces (sometimes it is better to replace
sal_Unicode with rtl::OUString etc.).
Of course the complete string context is preferable to the current
16bit-sal_Unicode interface, but...
the rework cost to change all this is overkill in a lot of situations
though, e.g. to get a character directionality, to get the character
attributes needed for vertical layout, to get the mirrored character, to
get the spacing attribute (needed for "word underline"), to get a character
digit's localized equivalent, etc.
Note the "sometimes."
[...]
sal_Unicode represents a UTF-16 code unit (without any ambiguity).
I hope we can agree that an interface a single UTF-16 code unit is a broken
design regarding characters outside the unicode base plane.
Of course. Fixing that brokenness is what this thread is all about.
[...]
Did I miss any important issues against adding a sal_UCS4 type?
Would that be "sal_UCS4" or "sal_Ucs4"?
I'd prefer sal_UCS4 because I've never seen the abbreviation for "Universal
Character Set" spelled in non-caps.
There are conventions to title-case even (normally all-uppercase)
acronyms when they are (part of) programming language identifiers (like
"URI" vs. "rtl_getUriCharClass"). OOo does not seem to consistently
follow any convention here, however.
-Stephan
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
