[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Best practise with no-break spaces in strings?
From:       Burkhard =?ISO-8859-1?Q?L=FCck?= <lueck () hube-lueck ! de>
Date:       2016-04-12 11:48:25
Message-ID: 2022610.lugTByTZ7m () tuxedo
[Download RAW message or body]

Am Monday 11 April 2016, 19:15:25 schrieb Friedrich W. H. Kossebau:
> Hi,
> 
> what is the recommended way to get parts of strings (like composed names) to
> be not wrapped in the UI, and also have translations follow that?
> 
> I found two options:
> a) xi18n with &nbsp;
> b) i18n with U+00A0 (NO-BREAK SPACE)
> 
> a) has more run-time costs, but might be more obvious to the translators
> than b).
> 
wcgrep "&nbsp;" l10n-kf5/templates/ 384 hits
And &nbsp; can be translated = copied from msgig to msgstr with the shortcut 
Ctrl+T
-> fast and less error prone

wcgrep "U+" l10n-kf5/templates/ 12 hits

> What should I do? I was going for b) but was not sure.
> 
How many strings do you have in mind - 10, 100, 1000 or more ;-)

-- 
Burkhard Lück

[prev in list] [next in list] [prev in thread] [next in thread]