I have to admit that I did not understand Abdel's idea %-|
I understood it that way: to present the ellipsis character in the UI
there is no need to put that character with unicode in the source code.
It is possible to translate the sequence "..." to the character "…"
within the I18N process. I think the po files were not in the scope
of this discussion - they don't count as "source" files here.
Then it is exactly what my "hack" does. I attach it again for reference.
It probably needs a bit more polish, but the idea is here.
JMarc
>From c48e487a7c1ba98061d55d6b2d0f2b2a0a219986 Mon Sep 17 00:00:00 2001
From: Jean-Marc Lasgouttes <lasgout...@lyx.org>
Date: Wed, 7 Oct 2015 10:34:06 +0200
Subject: [PATCH] Transform ... to proper ellipsis in translations
---
src/support/Messages.cpp | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/support/Messages.cpp b/src/support/Messages.cpp
index da1c3cc..177436f 100644
--- a/src/support/Messages.cpp
+++ b/src/support/Messages.cpp
@@ -94,6 +94,7 @@
#endif
using namespace std;
+using namespace lyx::support;
using boost::uint32_t;
namespace lyx {
@@ -125,6 +126,10 @@ void cleanTranslation(docstring & trans)
}
break;
}
+
+ static docstring const threedots = from_ascii("...");
+ static docstring const ellipsis = docstring(1, 0x2026);
+ trans = subst(trans, threedots, ellipsis);
}
} // lyx
@@ -132,8 +137,6 @@ void cleanTranslation(docstring & trans)
#ifdef ENABLE_NLS
-using namespace lyx::support;
-
namespace lyx {
std::string Messages::gui_lang_;
--
1.7.9.5
