Hi there,
I noticed there are still some translations for gtk+ and epiphany that
incorrectly translate strings with context ("this is context|this is the
string") to include either the literal context ("this is context|") or
even translate the context!
The following translations are concerned:
E
On სამ, 2006-09-12 at 20:52 +0200, Christian Persch wrote:
> Hi there,
>
> I noticed there are still some translations for gtk+ and epiphany that
> incorrectly translate strings with context ("this is context|this is the
> string") to include either the literal context ("this is context|") or
> ev
On 9/13/06, Christian Persch <[EMAIL PROTECTED]> wrote:
I noticed there are still some translations for gtk+ and epiphany that
incorrectly translate strings with context ("this is context|this is the
string") to include either the literal context ("this is context|") or
even translate the context
On Wed, 13 Sep 2006 02:15:19 +0100, Abel Cheung <[EMAIL PROTECTED]>
wrote:
> On 9/13/06, Christian Persch <[EMAIL PROTECTED]> wrote:
>> I noticed there are still some translations for gtk+ and epiphany that
>> incorrectly translate strings with context ("this is context|this is the
>> string") to
Christian Persch wrote:
>Hi there,
>
>I noticed there are still some translations for gtk+ and epiphany that
>incorrectly translate strings with context ("this is context|this is the
>string") to include either the literal context ("this is context|") or
>even translate the context!
>
>The followi
Fixed in pt_BR, awaiting upload to CVS. Bug #355748.
Leonardo Ferreira Fontenelle
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
On 9/13/06, David Lodge <[EMAIL PROTECTED]> wrote:
> This does lead to an interesting question though. gok has a selection of
> strings for extra characters on the keyboard, which may or may not exist,
> these are given a context. Translation of the first few levels is easy, as
> this is the normal
På Thu, Sep 14, 2006 at 01:19:42AM +0800, Abel Cheung skrev:
> On 9/13/06, David Lodge <[EMAIL PROTECTED]> wrote:
> > This does lead to an interesting question though. gok has a selection of
> > strings for extra characters on the keyboard, which may or may not exist,
> > these are given a context.
Wouter Bolsterlee wrote:
> På Thu, Sep 14, 2006 at 01:19:42AM +0800, Abel Cheung skrev:
>
>> On 9/13/06, David Lodge <[EMAIL PROTECTED]> wrote:
>>
>>>
>>>
>>> So I'm now getting "untranslated" strings on gok. (well only one as I
>>> added the Euro symbol to level2 :-) Any idea of how these
Hi,
On Thu, 2006-09-14 at 09:20 +0530, Runa B wrote:
> In case the msgstr is untranslated or fuzzy, doesnt the original msgid
> string show up on the interface? Hence if these strings are left blank
> the original msgid i.e. "some prefix|" would be used in the display,
> which beats the purpos
Sven Neumann wrote:
> Hi,
>
> On Thu, 2006-09-14 at 09:20 +0530, Runa B wrote:
>
>
>> In case the msgstr is untranslated or fuzzy, doesnt the original msgid
>> string show up on the interface? Hence if these strings are left blank
>> the original msgid i.e. "some prefix|" would be used in the
Runa B quoth on 14. sep 2006 05:50:
> In case the msgstr is untranslated or fuzzy, doesnt the original msgid
> string show up on the interface? Hence if these strings are left blank
> the original msgid i.e. "some prefix|" would be used in the display,
> which beats the purpose of leaving out t
12 matches
Mail list logo
