On 9/30/20 4:51 AM, ToddAndMargo via gnucash-user wrote:
Hi Geoff,
The current game plane is to
1) learn how to import a CSV into GnuCash
2) take my data that I was going to place in the clipboard
and instead write it to a standard CSV file and location
the GnuCash can easily and consistently see
Since I will be the one handling the dat, I should be able to
handle the pitfalls of CSV.
One of my customers had me write a filter between two
program the used a CSV to transfer data between the two
of them. Things go a little interesting when the
importing program thought the quote mark they were
using for inches was the field terminator. It was
a bug in the receiving program as the field terminator
is a quote and then a comma. The end of line is a quote
and a return. My solution was to find where they were
using a quote sign for inches and replace it with "in".
I do use single quotes to denote cable feet and I may
have a few double quotes in my part descriptions that
I have to deal with. It all depends on how well done
GnuCash's import function is written. I will find out.
-T
On 2020-09-30 06:40, Adrien Monteleone wrote:
> Sounds like a good case for using UTF8, prime and double-prime, either
> originally when typing, or in substitution while processing. That would
> also be typographically correct.
>
> Regards,
> Adrien
>
Here is a CSV exported from Libre Office Calc that
will blow a parcers mind, especially the second line
Inches,Feet
3”,0.25 ‘
"6”, strap","0.5’, strap"
Believe it or not, Calc actually reads it back correctly
_______________________________________________
gnucash-user mailing list
[email protected]
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.
