kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #36121
Re: Untranslated strings
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxx>
-
Date:
Tue, 12 Jun 2018 08:07:15 -0400
-
In-reply-to:
<CALHbTmZJzJE8eTr4UWQ5O06-2Lg2CyKmkxUuTsE=aYi25k8kWg@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
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?
Cheers,
Wayne
On 6/11/2018 11:28 PM, Seth Hillbrand wrote:
> 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
> anyone object to this plan? Is there a good reason to stay with wxT
> until after v5?
>
> -Seth
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References