> On Aug 24, 2018, at 1:36 PM, Colin Law <clan...@gmail.com> wrote: > > In Fri, 24 Aug 2018 at 17:58, Megagrumpy <megagru...@hotmail.com> wrote: >> >> SUCCESS!!! It turns out that I was very carefully ensuring that I was saving >> the file from Excel in "CSV UTF-8 (Comma delimited)" format as I thought >> this was the closest match to the Encoding required for the import tool. >> Changing to the option "CSV (comma delimited)" works. Or, as you suggested, >> changing to Western (ASCII) also works. > > I think that would possibly count as a bug in the importer would it not?
Maybe, though I suspect it’s a bug in Excel. Microsoft is well known for not really understanding UTF-8, and there’s always the possibility that Excel tried to write UTF-8 and Windows gratuitously transcoded it to the locale’s codepage. Regards, John Ralls _______________________________________________ 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.
