Re: diagnostics: prefer "…" to "..." if the locale supports it

[Akim Demaille]

Hi Paul,

> Le 12 oct. 2019 à 08:22, Paul Eggert <address@hidden> a écrit :
> 
> Since the confusion might be locale-dependent, perhaps all that’s needed is 
> to modify the translator comment to not insist on U+2026 so strongly. That 
> is, instead of saying “TRANSLATORS: use the appropriate character (e.g. "…") 
> if available.” it could say something like “TRANSLATORS: Use an ellipsis 
> appropriate for your language, remembering that "…" (U+2026 HORIZONTAL 
> ELLIPSIS) sometimes misdisplays and that "..." (three ASCII periods) is a 
> safer choice in some locales.”

I've installed this, thanks!

commit d9d37a11963f969a84865f1196ce018adf63085b
Author: Akim Demaille <address@hidden>
Date:   Sat Oct 12 10:43:53 2019 +0200

    i18n: don't push too hard for '…'
    
    Suggested by Paul Eggert.
    
    * src/location.c (ellipsis): Clarify comment for translators.

diff --git a/src/location.c b/src/location.c
index 4a0ae1cc..4d545472 100644
--- a/src/location.c
+++ b/src/location.c
@@ -242,8 +242,11 @@ static struct
 void caret_init (void)
 {
   screen_width = columns ();
-  /* TRANSLATORS: use the appropriate character (e.g. "…") if
-     available.  */
+  /* TRANSLATORS: This is used when a line is too long, and is
+     displayed truncated.  Use an ellipsis appropriate for your
+     language, remembering that "…" (U+2026 HORIZONTAL ELLIPSIS)
+     sometimes misdisplays and that "..." (three ASCII periods) is a
+     safer choice in some locales.  */
   ellipsis = _("...");
   ellipsize = mbswidth (ellipsis, 0);
 }