Well, actually, CSV *DOES* stand for Comma Separated Variables. If anybody uses 
a different character to separate the variables, e.g. semi-colon, then the data 
file is not CSV, it is something else. Using CSV to refer to any data file that 
uses a specific character to separate the variables (except Comma, of course) 
is on a par with referring to all vacuum cleaners as Hoovers, all analogue 
multimeters as Avo's, etc.
Cheers All,
Clarence

________________________________
From: [email protected] 
<[email protected]> on behalf of 
[email protected] 
<[email protected]>
Sent: 30 July 2019 19:00
To: [email protected] <[email protected]>
Subject: chirp_users Digest, Vol 127, Issue 14

Send chirp_users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://intrepid.danplanet.com/mailman/listinfo/chirp_users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of chirp_users digest..."


Today's Topics:

   1. Re: jetstream jt270m on win10 (Reza Rahgozar)
   2. Re: CHIRP won't recognize .csv file (Dave B)
   3. Re: CHIRP won't recognize .csv file (Reza Rahgozar)
   4. Re: CHIRP won't recognize .csv file (Nigel A. Gunn  G8IFF/W8IFF)


----------------------------------------------------------------------

Message: 1
Date: Tue, 30 Jul 2019 12:06:55 +0430
From: Reza Rahgozar <[email protected]>
Subject: Re: [chirp_users] jetstream jt270m on win10
To: Discussion of CHIRP <[email protected]>
Message-ID:
        <CAFoRs4e5DMb9UQMLp2_3ZpvLZJgkX3JhSTgn80v=3eycjwy...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Use px728 programing software in PC for any Walky talky from to day I did
write this app until u do use and pray for me.enjoy

On Fri, Jul 12, 2019, 07:26 Jim Unroe <[email protected]> wrote:

> On Thu, Jul 11, 2019 at 9:07 PM Glenn At Home <[email protected]>
> wrote:
> >
> > Hi Patricia,
> > Perhaps it's the terminology you are using.
> > Download is from Chirp to the radio, and Upload is to Chirp.
> > You will first download to the radio, set up the database, and upload to
> the radio.
> >
> > HTH.
> > Glenn
>
> Glenn,
>
> I think you meant to say it right but it wound up being reversed.
>
> An easy way to remember is to look at it as if the radio is sitting on
> top of the computer. Data going from the radio towards the computer
> would be down (download). Data going from the computer towards the
> radio would be up (upload).
>
> Radio
>   ? (on the Radio tab choose "Download From Radio   Alt+D")
> Computer
>
> Radio
>   ? (on the Radio tab choose "Upload To Radio   Alt+U")
> Computer
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> [email protected]
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Orbit at [email protected]
> To unsubscribe, send an email to
> [email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190730/5372d23e/attachment-0001.html

------------------------------

Message: 2
Date: Tue, 30 Jul 2019 09:10:09 +0100
From: Dave B <[email protected]>
Subject: Re: [chirp_users] CHIRP won't recognize .csv file
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Re:-

.CSV dowsn't mean that the correct fields are included or in the correct
order, or that the field headers are there, or that the fields are
seperated by commas and not some other character.

~ ~ ~

Er... CSV stands for "Comma Separated Variable". So, the data fields
/will/be separated by a comma ','

However, the nature of the field contents, and the order they are in,
are not part of the CSV format, that IS application specific.

Line ends can be whatever the native system expects/can handle, but
again, that can cause things to fall over too.

CHIRP (and many other similar CSV aware data munchers) are a bit fragile
in this respect, but to harden CHIRP against unexpected stuff, would be
a major undertaking.

Some locale's too, use the comma as a decimal separator, so that can
mess things up if you create such a file outside of CHIRP. 73 Dave G0WBX.

--
Created on and sent from a Unix like PC running and using free and open source 
software:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190730/c76c17b8/attachment-0001.html

------------------------------

Message: 3
Date: Tue, 30 Jul 2019 14:12:20 +0430
From: Reza Rahgozar <[email protected]>
Subject: Re: [chirp_users] CHIRP won't recognize .csv file
To: Dave B <[email protected]>,   Discussion of CHIRP
        <[email protected]>
Message-ID:
        <cafors4dsp5q188zfdnunp7ywv3onybhuqgqzb2xknkx197w...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Use UHF antenna for vhf or HD devices.is very better but u should
disconnect and remove battry from device when u want use from powered radio
because battry it's may crash motherboard so u can use with out battry and
sharper.just with a better anten

On Tue, Jul 30, 2019, 12:40 Dave B via chirp_users <
[email protected]> wrote:

> Re:-
>
> .CSV dowsn't mean that the correct fields are included or in the correct
> order, or that the field headers are there, or that the fields are
> seperated by commas and not some other character.
>
> ~ ~ ~
>
> Er... CSV stands for "Comma Separated Variable". So, the data fields
> *will* be separated by a comma ','
>
> However, the nature of the field contents, and the order they are in, are
> not part of the CSV format, that IS application specific.
>
> Line ends can be whatever the native system expects/can handle, but again,
> that can cause things to fall over too.
>
> CHIRP (and many other similar CSV aware data munchers) are a bit fragile
> in this respect, but to harden CHIRP against unexpected stuff, would be a
> major undertaking.
>
> Some locale's too, use the comma as a decimal separator, so that can mess
> things up if you create such a file outside of CHIRP. 73 Dave G0WBX.
>
> --
> Created on and sent from a Unix like PC running and using free and open 
> source software:
>
>
> _______________________________________________
> chirp_users mailing list
> [email protected]
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Orbit at [email protected]
> To unsubscribe, send an email to
> [email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190730/228fb30f/attachment-0001.html

------------------------------

Message: 4
Date: Tue, 30 Jul 2019 08:27:23 -0400 (EDT)
From: "Nigel A. Gunn  G8IFF/W8IFF" <[email protected]>
Subject: Re: [chirp_users] CHIRP won't recognize .csv file
To: Dave B <[email protected]>,  Discussion of CHIRP
        <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Not necessarily. In both Libre Office and Excel you can specify what the 
delimit character is going to be. Doesn't have to be a comma at all. 
Spreadsheet will still be saves as a .CSV.



> On 30 July 2019 at 04:10 Dave B via chirp_users 
> <[email protected]> wrote:
>
>
>     ~ ~ ~
>
>     Er... CSV stands for "Comma Separated Variable". So, the data fields will 
> be separated by a comma ','
>

Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 
5032
Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail [email protected] www 
http://www.ngunn.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20190730/a3344a76/attachment-0001.html

------------------------------

_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
To unsubscribe, send an email to [email protected]

End of chirp_users Digest, Vol 127, Issue 14
********************************************
_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to [email protected] at [email protected]
To unsubscribe, send an email to [email protected]

Reply via email to