On Tue, Jun 12, 2018 at 08:43:53AM -0400, Wayne Stambaugh wrote:
> Hey Carsten,
>
> On 6/12/2018 8:28 AM, Carsten Schoenert wrote:
> > Hello Wayne,
> >
> > Am 12.06.2018 um 14:07 schrieb Wayne Stambaugh:
> >> I'm thinking we should probably wait until after v5 and back port the
> >> fix to the v5
Hey Carsten,
On 6/12/2018 8:28 AM, Carsten Schoenert wrote:
> Hello Wayne,
>
> Am 12.06.2018 um 14:07 schrieb Wayne Stambaugh:
>> I'm thinking we should probably wait until after v5 and back port the
>> fix to the v5 branch but the string example you noted should definitely
>> be translated. I d
Hello Wayne,
Am 12.06.2018 um 14:07 schrieb Wayne Stambaugh:
> I'm thinking we should probably wait until after v5 and back port the
> fix to the v5 branch but the string example you noted should definitely
> be translated. I don't know how much grief this would cause our
> translators this late
I'm thinking we should probably wait until after v5 and back port the
fix to the v5 branch but the string example you noted should definitely
be translated. I don't know how much grief this would cause our
translators this late in the game. Would any of our translators care to
comment on this?
C
I think this would be ok as it does not change anything from the user even
if the translation is not updated. But I am not really a translator, so
there might be some subtle thing I have missed.
2018-06-12 5:28 GMT+02:00 Seth Hillbrand :
> Hi Devs-
>
> We're in string freeze but I've run across
Hi Devs-
We're in string freeze but I've run across a couple of strings that are
wxT() instead of _(). Example: cvpcb/display_footprints_frame.cpp:435.
I have a preference for converting these to _(), even at this stage as
worst-case is that they remain untranslated as they are now. Does anyo
6 matches
Mail list logo
