Exactly!  Since there are two periods in the version number, they cannot possibly be a decimal fraction indicator.  Each number (major version, minor version, & revision level) are separate whole numbers.

If one is using Windows 10, go to the "System" page & note the current Microsoft version: 10.16299.64.  Soon the revision level (typically every time an update forces a reboot) will be over 100, just like for earlier builds.  There is never a leading zero, because each number is a whole number, not a decimal fraction.

This is a standard industry way of denoting the major version, minor version, & revision level.


On 2017-11-21 18:56, George Riner wrote:
Interesting interpretation of what the period (or 'dot') symbol means as 
punctuation between the levels of revisions in the releases. It does not mean a 
decimal fraction part thereof. It is more representative of say an outline 
level, such as what Microsoft Word would produce if one had subheadings 
numbered 1 through 18 - the ones numbered 1 through 9 would not have a zero and 
I think most people would readily understand that 3 is less than 18.

2.6.18 means the 18th revision of the 6th version of release 2.

If the future versions of gnucash proceed up to "2.10", I don't think the 
developers should expected to go back and renumber 2.1 to 2.01; 2.2 to 2.02; etc.; Nor 
should they have been expected to start that numbering at the outset not knowing if they 
would even get to a 2.10 before getting to release 3.0

: George
-- -- --
Sent by Droid.

On November 21, 2017 5:59:54 PM PST, Alan Whiteman <a.c.white...@gmail.com> 
wrote:
I think the confusion is that .3 is generally accepted (here in the
U.S., anyway) as "0.30".

so .3 = .30

Perhaps the number method should be 2.6.03 instead of 2.6.3... For the
future, of course.

On 11/21/2017 11:14 AM, davel...@mac.com wrote:
Please keep replies on the list as it may help others.

Yes, 2.6.18 is newer. Each number between the periods is a separate
number and 18 is greater than 3.
In general, do not download the 2.7.x versions as those are beta
releases for the next version unless you are testing those with other
data (i.e., don't run a 2.7 with the only copy of your actual data
file).
Dave

On Nov 21, 2017, at 12:34 PM, Sean Perlmutter
<s...@seanperlmutter.com> wrote:
Hi Dave,

Just requested access to the list. But looking for an answer
quickly. Saw your reply re the issue below and thought I’d contact you
directly. Hope that’s ok.
I’ve got the same issue: Just updated to High Sierra, now GnuCash
won’t open. And I can’t find Gnucash.app/contents/Resources/lib.
I see your workaround is to just update to the newest version of
GnuCash. Which I’m happy to do. But something is odd.
I have version 2.6.3, installed March 2014. And the GnuCash homepage
shows the most recent version as 2.6.18. The version number is lower!
Am I missing something? Is that more recent than 2.6.3?
Thanks in advance for your help.
Sean



On Nov 16, 2017, at 10:36 AM, Peter Schoonmaker <petermschoonmaker
at gmail.com
wrote:
   Hello,

   I’ve used Gnucash for several years and I love it. But, I’m a
complete novice about the technical side of Gnucash and I need very
basic help. I understand that the following is a fix or work around my
recent problem:
   copy /usr/lib/libz.1.dylib to Gnucash.app/Contents/Resources/lib

   However, I don’t know what the above line means nor how to
implement it. In other words, how do I copy /usr/lib/libz.1.dylib to
Gnucash.app/Contents/Resources/lib?
   I’m embarrassed to admit my lack of knowledge, but I would need a
step by step description in order to fix this problem on my MacBook
Pro.
   I don’t even know the version of Gnucash that I’m running. I don’t
want to lose my data from the last few years. Is it safe to try to
reinstall Gnucash with the latest version?
   I’ve thought about moving my Gnucash data from my current computer
to another Mac that’s running an older operating system than High
Sierra, but I don’t even know how to begin to do that.
   Thanks, in advance, for any assistance you can give me. I’ve
copied this message to my regular email address so I won’t miss any
replies. Thanks again.
   Peter



That fix is only needed if you're running an old version. The easier
solution is to download the latest gnucash for Mac which no longer
requires that fix.
Copying it to another computer requires knowledge of where the data
file you are using is stored. If your only goal is to get gnucash
running again, just install the latest version on the High Sierra
computer. If you still want to move it to another computer, we'll need
to figure out where your data file is installed. I'm not at a computer
with gnucash installed right now so I can't check how to tell that.
HTH,
Dave


_______________________________________________
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-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.

Reply via email to