Re: [Kicad-developers] The problems with wxString

2014-01-04 Thread Maciej Sumiński
On 01/02/2014 07:04 PM, Dick Hollenbeck wrote: In my opinion if the class is specifically designed for UTF8, we could drop the std::string iterator. It is, but it is for strings, not UTF8 character manipulation. Its best use is at the edge of the system in helping with serialization and

Re: [Kicad-developers] The problems with wxString

2014-01-02 Thread Lorenzo Marcantonio
On Thu, Jan 02, 2014 at 12:04:36PM -0600, Dick Hollenbeck wrote: > It is, but it is for strings, not UTF8 character manipulation. Its best use > is at the > edge of the system in helping with serialization and de-serialization to > disk, clipboard, > other byte oriented peripherals TBD. Futurer

Re: [Kicad-developers] The problems with wxString

2014-01-02 Thread Dick Hollenbeck
> In my opinion if the class is specifically designed for >> UTF8, we could drop the std::string iterator. It is, but it is for strings, not UTF8 character manipulation. Its best use is at the edge of the system in helping with serialization and de-serialization to disk, clipboard, other byt

Re: [Kicad-developers] The problems with wxString

2014-01-02 Thread Dick Hollenbeck
On 01/02/2014 10:42 AM, Maciej Sumiński wrote: > On 01/01/2014 07:58 AM, Dick Hollenbeck wrote: >> On 11/21/2013 02:16 PM, Dick Hollenbeck wrote: >>> >>> 1) wx >= 2.9 has these constructors >>> >>> >>> wxString( const char* ) >>> wxString( std::string ) >>> >>> whereas wx 2.8 does not. >>>

Re: [Kicad-developers] The problems with wxString

2014-01-02 Thread Maciej Sumiński
On 01/01/2014 07:58 AM, Dick Hollenbeck wrote: On 11/21/2013 02:16 PM, Dick Hollenbeck wrote: 1) wx >= 2.9 has these constructors wxString( const char* ) wxString( std::string ) whereas wx 2.8 does not. Both offer: wxString( const char*, wxConvUTF8 ); but this cannot be us

Re: [Kicad-developers] The problems with wxString

2014-01-01 Thread Lorenzo Marcantonio
On Wed, Jan 01, 2014 at 12:58:15AM -0600, Dick Hollenbeck wrote: > > encoding cannot be assumed to be UTF8, even though it often is on linux. > > You just cannot > > assume it. Yep, sadly Latin-1 is not distinguishable from UTF-8, except by heuristics... > > In summary, I don't see any easy imm

Re: [Kicad-developers] The problems with wxString

2013-12-31 Thread Dick Hollenbeck
On 11/21/2013 02:16 PM, Dick Hollenbeck wrote: > > 1) wx >= 2.9 has these constructors > > > wxString( const char* ) > wxString( std::string ) > > whereas wx 2.8 does not. > > Both offer: > > wxString( const char*, wxConvUTF8 ); > > but this cannot be used in a default "type prom

Re: [Kicad-developers] The problems with wxString

2013-11-22 Thread Wayne Stambaugh
On 11/21/2013 3:16 PM, Dick Hollenbeck wrote: > > 1) wx >= 2.9 has these constructors > > > wxString( const char* ) > wxString( std::string ) > > whereas wx 2.8 does not. > > Both offer: > > wxString( const char*, wxConvUTF8 ); > > but this cannot be used in a default "type promo

[Kicad-developers] The problems with wxString

2013-11-21 Thread Dick Hollenbeck
1) wx >= 2.9 has these constructors wxString( const char* ) wxString( std::string ) whereas wx 2.8 does not. Both offer: wxString( const char*, wxConvUTF8 ); but this cannot be used in a default "type promotion" situation, this constructor must be invoked explicitly. 2) Th