On 6/18/2022 2:00 PM, Adrien Monteleone wrote:
I'm not arguing anything. I'm simply passing along what I've seen the devs talk about in prior threads.

Of course, if they have time out of their day coding GnuCash to chime in, I'm sure they can enlighten you more on the issues they have to consider in the code, and why that decision was made. As far as I'm aware, they aren't specifically 'anti-crypto'.

Perhaps if one of them (or an experienced user) has the time, they can put something in the FAQ on the subject. (it is a fairly frequent topic here on the list.)

Of course, if you took the time to search the list archives, you'll find those discussions and explanations.

I'll reply not a a developer but as somebody whose done LOTS of software design in my day.

a) If the developers did the job right, the ISO currency codes are not hard coded but in "app data" read in when the program starts << that means they can be changed without changing the code in any program, just data in a file.

b) NO, not a "lame excuse". Misunderstanding of what the ISO is/does. It sets STANDARDS. In other words, "for currency X use ABX" (or whatever). Dr. David, if there is no agreed standard for what the three letter currency code for "bitcoin" is, what should the developers use? Should they simply use ANY three characters not already in use for some currency that has an ISO currency code? There are > 17 thousand three character codes possible and only the order of a hundred or two in use. Whatever they pick the odds are worse then 10,000:1 it won't agree with the code chosen by any other team of software developers OR with what eventually become the standardized currency code for bitcoin if/when the ISO chooses one.

   Your beef should not be with the gnucash developers but with the ISO. You bitcoin users need to lobby THEM to choose a code for bitcoin. Actually, there are TWO standards you need them to choose. One one is the two character prefix to be used when a currency that is not the currency of a nation state (or union of states, like EU in EUR). Then the third character that means "bitcoin".

       Actually, there ARE several codes (competing codes) in use for Bitcoin. Any of those might end up as the eventual code except BTC (which violates ISO 4217 because BT is the code for an existing nation state). When I was suggesting that a two character code first, note that "CC" (for "cryptocurrency" will not do as "CC" already assigned as a "country code".

Michael D Novack


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

Reply via email to