Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming > #4184 > unrolled thread

Colons in internationalized UI

Started byVictor Porton <porton@narod.ru>
First post2014-04-03 18:25 +0300
Last post2014-04-04 20:40 +0300
Articles 3 — 2 participants

Back to article view | Back to comp.programming


Contents

  Colons in internationalized UI Victor Porton <porton@narod.ru> - 2014-04-03 18:25 +0300
    Re: Colons in internationalized UI "BartC" <bc@freeuk.com> - 2014-04-04 16:04 +0100
      Re: Colons in internationalized UI Victor Porton <porton@narod.ru> - 2014-04-04 20:40 +0300

#4184 — Colons in internationalized UI

FromVictor Porton <porton@narod.ru>
Date2014-04-03 18:25 +0300
SubjectColons in internationalized UI
Message-ID<lhjugs$bs7$1@speranza.aioe.org>
I have asked this question at Programmers.StackExchange and received two 
answers which contradict each other:

http://goo.gl/MRbROp

My question:

When using gettext or a similar framework, should the translation strings 
include ':' (like "Label:") for generating labels for UI or should I add ':' 
in UI code itself?

Please discuss arguments for both using or not using colons in i18n strings.

-- 
Victor Porton - http://portonvictor.org

[toc] | [next] | [standalone]


#4186

From"BartC" <bc@freeuk.com>
Date2014-04-04 16:04 +0100
Message-ID<gSz%u.72161$%U7.29330@fx05.am4>
In reply to#4184

"Victor Porton" <porton@narod.ru> wrote in message
news:lhjugs$bs7$1@speranza.aioe.org...
> I have asked this question at Programmers.StackExchange and received two
> answers which contradict each other:
>
> http://goo.gl/MRbROp
>
> My question:
>
> When using gettext or a similar framework, should the translation strings
> include ':' (like "Label:") for generating labels for UI or should I add
> ':'
> in UI code itself?

> Please discuss arguments for both using or not using colons in i18n
> strings.

I've added another reply to stackexchange, explaining my approach, which 
involves the translation data not storing the colon. So it's presumably now 
2:1 against having the colon.

-- 
Bartc 

[toc] | [prev] | [next] | [standalone]


#4187

FromVictor Porton <porton@narod.ru>
Date2014-04-04 20:40 +0300
Message-ID<lhmqqo$a7k$1@speranza.aioe.org>
In reply to#4186
BartC wrote:
> "Victor Porton" <porton@narod.ru> wrote in message
> news:lhjugs$bs7$1@speranza.aioe.org...
>> I have asked this question at Programmers.StackExchange and received two
>> answers which contradict each other:
>>
>> http://goo.gl/MRbROp
>>
>> My question:
>>
>> When using gettext or a similar framework, should the translation strings
>> include ':' (like "Label:") for generating labels for UI or should I add
>> ':'
>> in UI code itself?
> 
>> Please discuss arguments for both using or not using colons in i18n
>> strings.
> 
> I've added another reply to stackexchange, explaining my approach, which
> involves the translation data not storing the colon. So it's presumably
> now 2:1 against having the colon.

I've finally decided to use entire strings (strings with colons in this 
case) in my i18n files.

The reason for this that in French there should be a space before colon. So 
the best way to encode French is to put colons (with spaces before) in 
translation strings.

No, we do not translate to French. But this is an example for a general rule 
of behavior: Put colons in translation strings, not in UI code.

-- 
Victor Porton - http://portonvictor.org

[toc] | [prev] | [standalone]


Back to top | Article view | comp.programming


csiph-web