summaryrefslogtreecommitdiff
path: root/cui/source/dialogs/cuicharmap.cxx
diff options
context:
space:
mode:
authorAdolfo Jayme Barrientos <fitojb@ubuntu.com>2018-09-12 16:14:28 -0500
committerAdolfo Jayme Barrientos <fitojb@ubuntu.com>2018-10-15 01:46:59 +0200
commitcf2825d9f8af86a73aae5ac4216966504b320184 (patch)
tree5174b0d631b336eadd4eb84b4b8c7e78f30e1385 /cui/source/dialogs/cuicharmap.cxx
parent26c7c10d2de625f616d34897fa45c1b9b22c50a8 (diff)
The code doesn’t check for glyphs, but for code points (i.e., characters)
This string was a little misleading. A typical pair of OS-provided fonts can encode glyphs at different code points (e.g., the f+i ligature is encoded at U+F001 (legacy position) in Arial Black but at U+FB01 in Comic Sans MS. Change-Id: I6ca93e9ad247f62e1674a03d6ab1bc0800df3612 Reviewed-on: https://gerrit.libreoffice.org/60419 Tested-by: Jenkins Reviewed-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>
Diffstat (limited to 'cui/source/dialogs/cuicharmap.cxx')
-rw-r--r--cui/source/dialogs/cuicharmap.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/cui/source/dialogs/cuicharmap.cxx b/cui/source/dialogs/cuicharmap.cxx
index 4ffc213003ca..64581f5f5165 100644
--- a/cui/source/dialogs/cuicharmap.cxx
+++ b/cui/source/dialogs/cuicharmap.cxx
@@ -1049,7 +1049,7 @@ void SvxCharacterMap::selectCharByCode(Radix radix)
// Select the corresponding character
SetChar(cChar);
else {
- m_xCharName->set_label(CuiResId(RID_SVXSTR_MISSING_GLYPH));
+ m_xCharName->set_label(CuiResId(RID_SVXSTR_MISSING_CHAR));
m_aShowChar.SetText(" ");
switch(radix)
{