Re: [bug-gettext] A new option to msgen to make translations no longer identical?

[John Cowan]

Nguyen Thai Ngoc Duy scripsit:

> While the fake translation must not be identical to original strings,
> it should remain intelligible otherwise developers won't know how to
> control the applicaton. I'm thinking of changing just the letter case.
> For example, "this is an example" may become "tHiS iS aN eXamPle".
> Leetspeak [1] may be even better. If a command line app tries to test
> if a string is translated, changing  case only may get past "grep -i",
> leetspeak won't.

Support for the three Microsoft pseudo-locales would be much better, I
think: they flush out all sorts of i18n bugs while remaining readable to
anglophone developers.  There are three of them: the qps-base locale,
which has strings like "[Шěđлеśđαỳ !!!], 8 ōf [Μäŕςћ !!] ōf 2006"
instead of "Wednesday, 8 March 2006"; the qps-mirr locale, which uses
right-to-left characters; and the qps-asia locale, which exploits
CJK characters.  (These names are not valid BCP 47 strings; an "-x-"
should be added after "qps".)

In addition, these locales have multi-character separators, documented
at http://blogs.msdn.com/b/michkap/archive/2010/03/02/9971296.aspx .

Google has a pseudo-localization library at
https://code.google.com/p/pseudolocalization-tool/ .  There's also an
on-line pseudo-translator at http://www.inter-locale.com/demos/pseudo.jsp
.

-- 
John Cowan    http://ccil.org/~cowan    address@hidden
[T]here is a Darwinian explanation for the refusal to accept Darwin.
Given the very pessimistic conclusions about moral purpose to which his
theory drives us, and given the importance of a sense of moral purpose
in helping us cope with life, a refusal to believe Darwin's theory may
have important survival value. --Ian Johnston