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

List:       kde-i18n-doc
Subject:    Re: Backporting r1209192 to 4.6 (missing i18n -> i18nc)
From:       Frederik Schwarzer <schwarzerf () gmail ! com>
Date:       2010-12-25 20:55:59
Message-ID: 201012252155.59668.schwarzerf () gmail ! com
[Download RAW message or body]

[Raphael Kubo da Costa - Saturday 25 December 2010 19:28:01] 
> (Plase keep me CC'ed as I'm not subscribed to the list)
> 
> Hi there,
> 
> I have just realized that when I committed some changes a few months
> ago that introduced contexts and added semantic tags to some i18n
> calls in Ark I did not replace i18n() with i18nc(), which resulted in
> the messages ending up being weirdly formatted.
> 
> I've committed r1209192 [1] to trunk, and would like to know what
> should be done to the 4.6 branch: pino said the i18nc() calls would
> change the strings, so backporting this commit now might be a no-go
> since 4.6 is almost out. Should I backport it after 4.6.0 or should I
> not backport it at all, leaving the messages in 4.6 looking a bit
> weird?

Out of curiosity:
In what way does putting "@info" in the context change the
appearing of the message?

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