Re: Gnucash & macOS High Sierra.

[Maf. King]

On Thursday, 14 December 2017 10:48:25 GMT Pam Dooner wrote:
> Now, how do unsubscribe from the list
> without losing permanent access, just in case I need help in the future?
> Regards
> 
> 
> *Pam Dooner*

> 
> ___
> https://lists.gnucash.org/mailman/listinfo/gnucash-user


Hi Pam.

go to the list management page as shown above (and probably below, too!)

there are options there about how you receive the list emails.

HTH,
Maf.

___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Pam Dooner]

Looks like changing back to en_GB has solved it. Don't need to have commas!
Thing is I never changed it to FR in the first place!
Thank you very much for your help. Now, how do unsubscribe from the list
without losing permanent access, just in case I need help in the future?
Regards


*Pam Dooner*

On 14 December 2017 at 02:32, John Ralls  wrote:

> The base currency of the book is completely separate from the LC_MONETARY
> setting in the environment, so you can have a Euro account and still have
> LC_MONETARY set to en_GB so that you have dots for the decimal separator.
>
> As for storing 99/100 as ‘0.99’, that’s backwards. GnuCash always stores
> numbers as rationals and the SX string parser knows how to parse rationals
> so I think that if you actually write “99/100” in your SX formula it will
> be locale-safe. You might try switching back to en_GB, editing the SXes to
> use rationals instead of decimals, and then switch back to fr_FR for the
> commas (assuming that you actually want to “go native” and use commas for
> the decimal separator). That should resolve the problem without having to
> delete and recreate the scheduled transactions.
>
> One more thing: The list is archived at https://lists.gnucash.org/
> mailman/listinfo/gnucash-user so even if you do accidentally delete a
> message you can still read it there.
>
> Regards,
> John Ralls
>
> On Dec 13, 2017, at 1:11 PM, Pam Dooner  wrote:
>
> Just to clarify. My OS is in English but I live in France !
>
> Le mer. 13 déc. 2017 à 21:38, Pam Dooner  a écrit :
>
> 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  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  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  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  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  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  wrote:
>
> Hi,
>
> Pam Dooner  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, specificall

Re: Gnucash & macOS High Sierra.

[John Ralls]

The base currency of the book is completely separate from the LC_MONETARY 
setting in the environment, so you can have a Euro account and still have 
LC_MONETARY set to en_GB so that you have dots for the decimal separator.

As for storing 99/100 as ‘0.99’, that’s backwards. GnuCash always stores 
numbers as rationals and the SX string parser knows how to parse rationals so I 
think that if you actually write “99/100” in your SX formula it will be 
locale-safe. You might try switching back to en_GB, editing the SXes to use 
rationals instead of decimals, and then switch back to fr_FR for the commas 
(assuming that you actually want to “go native” and use commas for the decimal 
separator). That should resolve the problem without having to delete and 
recreate the scheduled transactions.

One more thing: The list is archived at 
https://lists.gnucash.org/mailman/listinfo/gnucash-user 
 so even if you do 
accidentally delete a message you can still read it there.

Regards,
John Ralls

> On Dec 13, 2017, at 1:11 PM, Pam Dooner  wrote:
> 
> Just to clarify. My OS is in English but I live in France !
> 
> Le mer. 13 déc. 2017 à 21:38, Pam Dooner  > a écrit :
> 
>> 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  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  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  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  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  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  wrote:
>>> 
 Hi,
 
 Pam Dooner  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
 com

Re: Gnucash & macOS High Sierra.

[Pam Dooner]

Just to clarify. My OS is in English but I live in France !

Le mer. 13 déc. 2017 à 21:38, Pam Dooner  a écrit :

> 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  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  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  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  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  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  wrote:
> >
> >> Hi,
> >>
> >> Pam Dooner  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)
>>

Re: 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  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  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  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  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  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  wrote:
 >
 >> Hi,
 >>
 >> Pam Dooner  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
 >>warl...@mit.eduPGP key available
 >>
 >


 --
Derek Atkins 617-623-3745
de...@ihtfp.com www.ihtfp.com
  

Re: Gnucash & macOS High Sierra.

[Dave H]

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  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  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  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  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  wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> Pam Dooner  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
>>> >>warl...@mit.eduPGP key available
>>> >>
>>> >
>>>
>>>
>>> --
>>>Derek Atkins 617-623-3745
>>>de...@ihtfp.com www.ihtfp.com
>>>Computer and Internet Security Consultant
>>>
>>>
>>
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Derek Atkins]

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  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  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  wrote:
>
>> Hi,
>>
>> Pam Dooner  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
>>warl...@mit.eduPGP key available
>>
>


--
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant



___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Pam Dooner]

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  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  wrote:
> >
> >> Hi,
> >>
> >> Pam Dooner  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
> >>warl...@mit.eduPGP key available
> >>
> >
>
>
> --
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Derek Atkins]

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  wrote:
>
>> Hi,
>>
>> Pam Dooner  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
>>warl...@mit.eduPGP key available
>>
>


-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Pam Dooner]

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  wrote:

> Hi,
>
> Pam Dooner  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
>warl...@mit.eduPGP key available
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Derek Atkins]

Hi,

Pam Dooner  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
   warl...@mit.eduPGP key available
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Maf. King]

On Wednesday, 13 December 2017 11:39:10 GMT Pam Dooner wrote:
> 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

Hi Pam,

I believe that any version of GC would cause you grief in the situation you 
describe.

I think I read on this list that the template transaction amounts in a 
scheduled transaction are stored as alphanumeric strings, so if there is a 
comma or decimal point in those, they really are those physical characters.

whereas, the numbers in the registers are stored as numbers, so the comma/
decimal point isn't stored as a physical character, software effectively puts 
it  in automatically to make the numbers meaningful to a human as it displays 
them. 

I know it doesn't help your pain, but I thought it might offer some context. 

Maf.


___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[David T. via gnucash-user]

So, that sounds like a problem with a change in locale settings, and not a 
problem with Sierra. 
I doubt the original poster is encountering the same problem as you. 
David
 
 
  On Wed, Dec 13, 2017 at 16:39, Pam Dooner wrote:   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


*Pam Dooner*

On 13 December 2017 at 11:36, Dave H  wrote:

> Pam,
>
> I haven't had any of the issues you are talking about - running 2.6.18 on
> 10.13.2 at the moment on both an iMac and a Macbook pro.  My scheduled
> transactions are all editable and scheduling correctly.  Are you sure
> you're running 2.6.18 and not 2.6.17 which is the version that has issues I
> believe ?
>
> Cheers Dave H.
>
> On 13 December 2017 at 19:56, Pam Dooner  wrote:
>
>> The latest version opens but there are issues. Such as scheduled
>> transactions not being editable or scheduled. Trying just causes crash and
>> having to force quit. I’m going to try to edit the gnucash file on an older
>> windows pc then open it in high sierra to see if that helps.
>> Watch this space!
>>
>> Le mer. 13 déc. 2017 à 10:14, Dave H  a écrit :
>>
>>> There is an issue when you are not using the latest version of gnucash on
>>> High Sierra.  If you aren't using 2.6.18 download and install 2.6.18 and
>>> your issue should go away.
>>>
>>> Cheers Dave H.
>>>
>>> On 13 December 2017 at 08:47, James Armstrong 
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > Without thinking I,ve just updated my MacBook Pro with the latest
>>> version
>>> > of macOS High Sierra version 10.13.1.
>>> >
>>> > Gnucash will not start!
>>> >
>>> > A pop up message states:  Gnucash cannot be opened because of a
>>> problem.
>>> > Check with the developer to make sure Gnucash works with this version
>>> of
>>> > macOS.
>>> >
>>> > Is this the case?
>>> >
>>> > Any help you could offer would be much appreciated.
>>> >
>>> > Thank you.
>>> >
>>> > Jim
>>> >
>>> >
>>> > James Armstrong
>>> > LonghornJim®
>>> > 07905 103568
>>> > j...@longhornjim.com
>>> >
>>> >
>>> >
>>> >
>>> > ___
>>> > gnucash-user mailing list
>>> > gnucash-user@gnucash.org
>>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> > -
>>> > 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
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> -
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>>
>> --
>> Sent from Pam’s iPhone
>>
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Pam Dooner]

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


*Pam Dooner*

On 13 December 2017 at 11:36, Dave H  wrote:

> Pam,
>
> I haven't had any of the issues you are talking about - running 2.6.18 on
> 10.13.2 at the moment on both an iMac and a Macbook pro.  My scheduled
> transactions are all editable and scheduling correctly.  Are you sure
> you're running 2.6.18 and not 2.6.17 which is the version that has issues I
> believe ?
>
> Cheers Dave H.
>
> On 13 December 2017 at 19:56, Pam Dooner  wrote:
>
>> The latest version opens but there are issues. Such as scheduled
>> transactions not being editable or scheduled. Trying just causes crash and
>> having to force quit. I’m going to try to edit the gnucash file on an older
>> windows pc then open it in high sierra to see if that helps.
>> Watch this space!
>>
>> Le mer. 13 déc. 2017 à 10:14, Dave H  a écrit :
>>
>>> There is an issue when you are not using the latest version of gnucash on
>>> High Sierra.  If you aren't using 2.6.18 download and install 2.6.18 and
>>> your issue should go away.
>>>
>>> Cheers Dave H.
>>>
>>> On 13 December 2017 at 08:47, James Armstrong 
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > Without thinking I,ve just updated my MacBook Pro with the latest
>>> version
>>> > of macOS High Sierra version 10.13.1.
>>> >
>>> > Gnucash will not start!
>>> >
>>> > A pop up message states:   Gnucash cannot be opened because of a
>>> problem.
>>> > Check with the developer to make sure Gnucash works with this version
>>> of
>>> > macOS.
>>> >
>>> > Is this the case?
>>> >
>>> > Any help you could offer would be much appreciated.
>>> >
>>> > Thank you.
>>> >
>>> > Jim
>>> >
>>> >
>>> > James Armstrong
>>> > LonghornJim®
>>> > 07905 103568
>>> > j...@longhornjim.com
>>> >
>>> >
>>> >
>>> >
>>> > ___
>>> > gnucash-user mailing list
>>> > gnucash-user@gnucash.org
>>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> > -
>>> > 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
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> -
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>>
>> --
>> Sent from Pam’s iPhone
>>
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Dave H]

Pam,

I haven't had any of the issues you are talking about - running 2.6.18 on
10.13.2 at the moment on both an iMac and a Macbook pro.  My scheduled
transactions are all editable and scheduling correctly.  Are you sure
you're running 2.6.18 and not 2.6.17 which is the version that has issues I
believe ?

Cheers Dave H.

On 13 December 2017 at 19:56, Pam Dooner  wrote:

> The latest version opens but there are issues. Such as scheduled
> transactions not being editable or scheduled. Trying just causes crash and
> having to force quit. I’m going to try to edit the gnucash file on an older
> windows pc then open it in high sierra to see if that helps.
> Watch this space!
>
> Le mer. 13 déc. 2017 à 10:14, Dave H  a écrit :
>
>> There is an issue when you are not using the latest version of gnucash on
>> High Sierra.  If you aren't using 2.6.18 download and install 2.6.18 and
>> your issue should go away.
>>
>> Cheers Dave H.
>>
>> On 13 December 2017 at 08:47, James Armstrong 
>> wrote:
>>
>> > Hi,
>> >
>> > Without thinking I,ve just updated my MacBook Pro with the latest
>> version
>> > of macOS High Sierra version 10.13.1.
>> >
>> > Gnucash will not start!
>> >
>> > A pop up message states:   Gnucash cannot be opened because of a
>> problem.
>> > Check with the developer to make sure Gnucash works with this version of
>> > macOS.
>> >
>> > Is this the case?
>> >
>> > Any help you could offer would be much appreciated.
>> >
>> > Thank you.
>> >
>> > Jim
>> >
>> >
>> > James Armstrong
>> > LonghornJim®
>> > 07905 103568
>> > j...@longhornjim.com
>> >
>> >
>> >
>> >
>> > ___
>> > gnucash-user mailing list
>> > gnucash-user@gnucash.org
>> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> > -
>> > 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
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>
> --
> Sent from Pam’s iPhone
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Pam Dooner]

The latest version opens but there are issues. Such as scheduled
transactions not being editable or scheduled. Trying just causes crash and
having to force quit. I’m going to try to edit the gnucash file on an older
windows pc then open it in high sierra to see if that helps.
Watch this space!

Le mer. 13 déc. 2017 à 10:14, Dave H  a écrit :

> There is an issue when you are not using the latest version of gnucash on
> High Sierra.  If you aren't using 2.6.18 download and install 2.6.18 and
> your issue should go away.
>
> Cheers Dave H.
>
> On 13 December 2017 at 08:47, James Armstrong  wrote:
>
> > Hi,
> >
> > Without thinking I,ve just updated my MacBook Pro with the latest version
> > of macOS High Sierra version 10.13.1.
> >
> > Gnucash will not start!
> >
> > A pop up message states:   Gnucash cannot be opened because of a problem.
> > Check with the developer to make sure Gnucash works with this version of
> > macOS.
> >
> > Is this the case?
> >
> > Any help you could offer would be much appreciated.
> >
> > Thank you.
> >
> > Jim
> >
> >
> > James Armstrong
> > LonghornJim®
> > 07905 103568
> > j...@longhornjim.com
> >
> >
> >
> >
> > ___
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -
> > 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
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-- 
Sent from Pam’s iPhone
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Gnucash & macOS High Sierra.

[Dave H]

There is an issue when you are not using the latest version of gnucash on
High Sierra.  If you aren't using 2.6.18 download and install 2.6.18 and
your issue should go away.

Cheers Dave H.

On 13 December 2017 at 08:47, James Armstrong  wrote:

> Hi,
>
> Without thinking I,ve just updated my MacBook Pro with the latest version
> of macOS High Sierra version 10.13.1.
>
> Gnucash will not start!
>
> A pop up message states:   Gnucash cannot be opened because of a problem.
> Check with the developer to make sure Gnucash works with this version of
> macOS.
>
> Is this the case?
>
> Any help you could offer would be much appreciated.
>
> Thank you.
>
> Jim
>
>
> James Armstrong
> LonghornJim®
> 07905 103568
> j...@longhornjim.com
>
>
>
>
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> 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
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Gnucash & macOS High Sierra.

[James Armstrong]

Hi,

Without thinking I,ve just updated my MacBook Pro with the latest version of 
macOS High Sierra version 10.13.1.

Gnucash will not start! 

A pop up message states:   Gnucash cannot be opened because of a problem. Check 
with the developer to make sure Gnucash works with this version of macOS.

Is this the case?

Any help you could offer would be much appreciated.

Thank you.

Jim 


James Armstrong 
LonghornJim®
07905 103568
j...@longhornjim.com




___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.