Re: SVN 1704 completely broke libedif

2023-06-07 Thread Dr . Jürgen Sauermann
Hi Chris, wrapping arbitrary (= UTF8-encoded) strings into UTF8_string first is the proper way to go. Consider the differences between: * **1.  UCS_string yyy(UTF8_string(xxx));   // almost proper, but ambiguous (most vexing parse error)** **2.  UCS_string yyy(xxx);    // now privat

Re: SVN 1704 completely broke libedif

2023-06-07 Thread Chris Moller
Thanks for the explanation--very much appreciated. I more or less stumbled onto 1. and am using that in every relevant circumstance, but I'll revise to 4.  (I can't generally use 5. because some of the strings use what I assume are non-ASCII characters like "←".) Thanks again, Chris On 6/7/