Re: Colons in internationalized UI

From	Victor Porton <porton@narod.ru>
Newsgroups	comp.programming
Subject	Re: Colons in internationalized UI
Date	2014-04-04 20:40 +0300
Organization	Aioe.org NNTP Server
Message-ID	<lhmqqo$a7k$1@speranza.aioe.org> (permalink)
References	<lhjugs$bs7$1@speranza.aioe.org> <gSz%u.72161$%U7.29330@fx05.am4>

Show all headers | View raw

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

Back to comp.programming | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

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

csiph-web