Le 06/10/2015 22:17, Guillaume Munch a écrit :
I think you might be mixing issues. One thing is allowing to have UTF-8
string literals especially in translations, another one is deciding that
we now use … instead of ... in the interface to be consistent with Qt.
What would be worse than using ... in the UI would be to use a random
mix of ... and … (look Ma, I managed to type it with my compose key!) in
the UI. By doing this change, we put more pressure on our translators to
do thing right.
An alternative would be the attached hack.
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
