Gnucash & macOS High Sierra.

[Pam Dooner]

Thank you very much for resending this. The message had gone into my spam
box and I’d deleted it before I realised it wasn’t spam. I’d hoped to not
have to delete the old scheduled transactions but looks like that’s what is
required.

Le mer. 13 déc. 2017 à 20:17, Dave H <hellvee at gmail.com> a écrit :

> John Ralls replied to Pam's original other posting a couple of days ago
> with a wiki link to changing langauage and other locale settings as follows
> ...
>
> Cheers Dave H.
>
>
> > On Dec 11, 2017, at 9:54 AM, Pam Dooner <pamdooner at gmail.com> wrote:
> >
> > Hi. I just upgraded to High Sierra and while gnucash opens and is usable,
> > trying to open the scheduled transaction editor crashes the editor and
> > gnush has to be force-quit. I get a parsing error on opening if there are
> > any scheduled transactions run since last opened so I wanted to edit the
> > transactions as the program no longer accepts the full stop as a decimal
> > separator since my locale is in euros. I then thought I'd just create new
> > scheduled transactions but that crashes too. After the parsing error
> > message the program opens but the amount of the entry is blank and it
> keeps
> > repeating this each time I open the program. It means I have to enter
> each
> > of my scheduled transactions manually, which is a bit of pain to say the
> > least, since I have 2 separate bank accounts! Any solution, workaround?
>
> Did you delete the old scheduled transactions, the ones with dots for
> decimal separators?
>
> Regards,
> John Ralls
>
> [1]
> http://wiki.gnucash.org/wiki/Locale_Settings#Changing_the_Language_on_OSX
>
>
>
> On 14 December 2017 at 04:58, Derek Atkins <derek at ihtfp.com> wrote:
>
>> Changing the currency is not sufficient. You need to change how numbers
>> are printed. I'm not sure how to do that on your platform.
>>
>> -derek
>> Sent using my mobile device. Please excuse any typos.
>>
>> On December 13, 2017 1:44:52 PM Pam Dooner <pamdooner at gmail.com> wrote:
>>
>>> Changing the locale seems only to affect new accounts. I have tried to
>>> ask for GBP but nothing has changed.
>>> Pam
>>>
>>>
>>> *Pam Dooner*
>>>
>>> On 13 December 2017 at 19:39, Derek Atkins <derek at ihtfp.com> wrote:
>>>
>>>> Yes, if you change your locale back to the old locale it should work
>>>> again.
>>>>
>>>> -derek
>>>>
>>>> On Wed, December 13, 2017 1:34 pm, Pam Dooner wrote:
>>>> > Thank you for this explanation. If I change my locale to UK, will
>>>> > everything then be OK? Otherwise how do I change the SX definitions?
>>>> > Regards,
>>>> > Pam
>>>> >
>>>> >
>>>> > *Pam Dooner*
>>>> >
>>>> > On 13 December 2017 at 16:30, Derek Atkins <warlord at mit.edu> wrote:
>>>> >
>>>> >> Hi,
>>>> >>
>>>> >> Pam Dooner <pamdooner at gmail.com> writes:
>>>> >>
>>>> >> > yes, definitely 2.6.18. Just tried again and this time managed to
>>>> get
>>>> >> a
>>>> >> > pop-up saying "An error occurred while processing 0.99"
>>>> >> > I am trying to change all my decimal points to commas to coincide
>>>> with
>>>> >> the
>>>> >> > euro locale that I have to use now it seems. In the older versions,
>>>> >> there
>>>> >> > was no issue with commas and points. I have UK accounts and
>>>> european
>>>> >> > accounts so ought to be able to use both but this version (and the
>>>> >> previous
>>>> >> > one) seem to cause the error if I try to use a decimal point. So
>>>> I'll
>>>> >> have
>>>> >> > to try to edit the file elsewhere and re-import it. I had hoped
>>>> there
>>>> >> might
>>>> >> > have been a way of globally changing all previous entries with a
>>>> >> decimal
>>>> >> > point to commas. In the actual accounts, it has changed them all to
>>>> >> commas
>>>> >> > but not in scheduled transactions!
>>>> >> > Pam
>>>> >>
>>>> >> Scheduled Transactions do not survive a locale change, specifically a
>>>> >> change where the decimal separator changes characters.  The reason is
>>>> >> that the SX data is stored as text, not as a numeric, so "99/100"
>>>> gets
>>>> >> stored as 0.99 and then it expects to be parsed as 0.99 -- however if
>>>> >> you change your locale so that a comma is a decimal separator then
>>>> >> GnuCash expects to read back 0,99.  But when it sees 0.99 it doesn't
>>>> >> know how to interpret that.
>>>> >>
>>>> >> The only fix is to change the SX definitions, or to change your
>>>> locale
>>>> >> specification of (IIRC) LC_NUMERIC back to the old style.
>>>> >>
>>>> >> I don't know if there is a way change the character from within the
>>>> >> program.
>>>> >>
>>>> >> > *Pam Dooner*
>>>> >>
>>>> >> > Please remember to CC this list on all your replies.
>>>> >> > You can do this by using Reply-To-List or Reply-All.
>>>> >>
>>>> >> -derek
>>>> >> --
>>>> >>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>>> >>        Member, MIT Student Information Processing Board  (SIPB)
>>>> >>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>>>> >>        warlord at MIT.EDU                        PGP key available
>>>> >>
>>>> >
>>>>
>>>>
>>>> --
>>>>        Derek Atkins                 617-623-3745
>>>>        derek at ihtfp.com             www.ihtfp.com
>>>>        Computer and Internet Security Consultant
>>>>
>>>>
>>>
> --
Sent from Pam’s iPhone