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@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp