Version: 188.8.131.52.alpha1+ (x64)
Build ID: b35e797ca0e2c7e7ad6dbccea6b92208b209677c
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-11-02_22:21:21
Should the hexadecimal digits A..E be in uppercase?
For example, the Unicode Character 'HYPHEN-MINUS' (U+002D)
I don't think this is important. It certainly doesn't matter for the function itself. Both uppercase and lowercase are legitimate Hex representations. The Alt-X feature just used the standard OUString() function used everywhere in LO, and that defaults to representing hexidecimaal using lowercase. I don't see any reason to change that.
Thank you Justin L for your comment.
Yes both uppercase and lowercase are legitimate Hex representations. However, the Unicode planes and used code point ranges are shown in uppercase.
If you think it is not important to follow the uppercase convention, feel free to close this bug.
Justin: what about this patch?
diff --git a/i18nutil/source/utility/unicode.cxx b/i18nutil/source/utility/unicode.cxx
index 8b56239..1d92b43 100644
@@ -1242,7 +1242,7 @@ OUString ToggleUnicodeCodepoint::ReplacementString()
sal_Int32 nPos = 0;
while( nPos < sIn.getLength() )
- OUStringBuffer aTmp = OUString::number(sIn.iterateCodePoints(&nPos),16);
+ OUStringBuffer aTmp = OUString::number(sIn.iterateCodePoints(&nPos),16).toAsciiUpperCase();
//pad with zeros - minimum length of 4.
for( sal_Int32 i = 4 - aTmp.getLength(); i > 0; --i )
aTmp.insert( 0,"0" );
(of course qa part should be changed too)
Indeed, if hexa can be made in uppercase or lowercase, it seems that, in general, hexa are displayed with uppercase.
Closing as NOTABUG since it’s just a style of representation that does not affect the output in any way. Unicode does not mandate hexadecimal numbers to be uppercase.