When you implement command line switches you will probably want --help to emit a translated message.
On Fri, May 3, 2019 at 1:51 PM Wayne Stambaugh <stambau...@gmail.com> wrote: > On 5/3/2019 11:27 AM, Dick Hollenbeck wrote: > > On 5/3/19 9:41 AM, Wayne Stambaugh wrote: > >> There is a secondary goal of removing wxWidgets from our low level > >> objects. Maybe some day we can build the low level KiCad non-ui > >> libraries sans wxWdigets. My thinking is that wxString should only come > >> into play at the UI level when dealing with wxWidgets UI code. Being > >> able to use a standard C++ string implementation would (may?) go a long > >> way in helping with that goal. > > > > That goal is what I had in mind when I wrote the UTF8 class, and its > bidirectional > > conversions to and from wxString. I think you can pass instances of > UTF8 to wx functions > > in many cases, and assign to UTF8 on function returns. > > > > But, you don't have all the nice translation support there. You could > through use wx > > translation support and simply assign to UTF8, however. > > > > I don't think translations are an issue because AFAIK we don't have any > strings in the low level non-ui objects that needs translated but I > could be wrong. > > _______________________________________________ > 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
