Re: SVN 1704 completely broke libedif

2023-06-06 Thread Chris Moller
Hi, Xtian, Just pushed a fix for edif if you want to give it a try.  Works for me on SVN 1706 and yesterday's SVN 1708. --cm On 6/5/23 03:33, Christian Robert wrote: SVN 1704 completely broke libedif Juergen made UCS_string (const char *)  a private member of the class so a lot of compile e

Re: SVN 1704 completely broke libedif

2023-06-06 Thread Christian Robert
Hi Chris, work as well as it used to ! many thanks for fixing this. I had to edit the generated ./libtool and change from: # Which release of libtool.m4 was used? macro_version=2.4.7 macro_revision=2.4.7 to: # Which release of libtool.m4 was used? macro_version=2.4.6 macro_revision=2.4.6

Re: SVN 1704 completely broke libedif

2023-06-06 Thread Chris Moller
Glad it works. It's probably a better idea to run ./configure before building. That way the Makefiles will exactly match your environment.  The downside of having a choice of Linux distros is that they're all a little different. --cm On 6/6/23 15:34, Christian Robert wrote: Hi Chris,  work

Re: SVN 1704 completely broke libedif

2023-06-06 Thread Dr . Jürgen Sauermann
Hi, sorry for that. The reason for making it private is to entirely prevent its usage. The former implementation of of it only worked for ASCII strings. There was a note about that in the header file, but I have seen quite a few incorrect usages of it (read: with UTF8-encoded strings) which the

Re: SVN 1704 completely broke libedif

2023-06-06 Thread Chris Moller
Yeah, I saw your comment in one of the .hh files. What I did was wrap all the edif ASCII strings in UTF8_string() calls.  That works, but if it's circumventing what you're trying to do, let me know and I'll think of something else. Even after a lot of years, I'm still not sure of the differenc