[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] typo in source

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] typo in source
Date: Thu, 11 Feb 2010 00:03:46 +0100

> I am just realizing that the offending strings seem locatable only in the
> translation file, and not in any program source files.

You figured that part out by yourself :-)

> I am wondering
> therefore whether the source may exist in some slightly different form,

It does subject to the .po translation files being generated from the
source code on demand only.

> evading
> search on "findthat" and whether what we witness is some artifact of the
> translation technology (maybe just Launchpad) that accounts for it.

Nope, it's fixed in the definitive source source.

>       grep -e "find*that" -n -r .
> yields the same and
>       grep -e "find that" -n -r .
> yields nothing.
> ??

That's because in the python source the string's split between lines
such that "find that" doesn't match.

That is also the reason of the run-together:

The Python source had

'... find'
'that ...'

which gettext found, recognized as being one single Python type string
continued over a line break, and thus concatenated it for the .po file
into just that - a continuous string: '... findthat ...'.

The Python source *should* have read

'... find\n'
'that ...'

which would have become '...find\nthat', canonically, which would then
have been intelligently rendered by translation software.

Makes sense ?


GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]