Geert, Thanks for looking into this and coming up with a fix.
Just out of curiosity, what is the fix that you’ve put in? Cheers, David > On Sep 4, 2018, at 5:34 AM, Geert Janssens <geert.gnuc...@kobaltwit.be> wrote: > > Op dinsdag 4 september 2018 10:36:11 CEST schreef Andy Brown via gnucash-user: >> Tried TextEdit. It does have a UTF-8 option but it won't correct the EOL >> character, (as far as I can make out from a one file test). I will try and >> find a hex editor and investigate the exact source of the problem when I >> have time. >> >> Andy > > Thanks for the feedback. The exact source of the problem is in the difference > in line-endings. GnuCash currently expects "LF" (the C++ default), but some > files can have "CRLF" (Windows) or "CR" (Macos) as line ending. > > I have made changes to the code to fix this for gnucash 3.3. > > Geert > > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.