On 19 Jul 2014, at 8:44pm, Keith Medcalf wrote:
> Simon Slavin wrote
>
>> So you used to see files with names like
>> SENSOR6.CSD . In SIXBIT, of course.
>
>> [snip]
>
> Fortunately the EBCDIC codes for IFS IGS IRS IUS are the same as the ASCI FS
> GS RS US respectively. Depends on the spe
Keith Medcalf expressed precisely :
Mostly the problems experienced by people is that they make some home-
brew CSV importer that does not realise how to correctly read
output from a standards-based exporter such as Excel, and then try to
change things like separation or quoting methods to "fix"
Of course, one advantage of using ASCII control separators is that they are
by definition valid Unicode control separators.
On Sat, Jul 19, 2014 at 1:44 PM, Keith Medcalf wrote:
> >ASCII 30 is Record Separator. Use this where you might expect a newline.
> >ASCII 31 is Unit Separator.Use th
>ASCII 30 is Record Separator. Use this where you might expect a newline.
>ASCII 31 is Unit Separator.Use this where you might expect a comma.
>Files which used these codes (together with 28 and 29) used to be called
>'Control Separated Data' files. So you used to see files with names like
>
On 19 Jul 2014 at 19:06, Jonathan Leslie wrote:
> h'mmm never new about ascii 28-31 either. I don't know why these things are
> kept a secret.
They aren't, you've obviously never bothered to look at the ASCII table, which,
oddly enough, can be found here:
http://www.asciitable.com
Person
h'mmm never new about ascii 28-31 either. I don't know why these things are
kept a secret. Alas though, it not being printable is a major headache, even
if its "procedural" to make it visible. Its just annoying. you put the
record out on ethernet and want to wireshark it, or have a log du
On 19 Jul 2014, at 4:42pm, James K. Lowden wrote:
> Jonathan Leslie wrote:
>
>> What I do is I never use a CSV file as a "Comma separated Values"
>> file but rather as a "Character separated Values" file, but rather
>> use a Character, º (0186), a legal character but not one on the
>> keyboar
On Fri, 18 Jul 2014 07:53:57 -0700
Jonathan Leslie wrote:
> What I do is I never use a CSV file as a "Comma separated Values"
> file but rather as a "Character separated Values" file, but rather
> use a Character, º (0186), a legal character but not one on the
> keyboard, as the separator charac
8 matches
Mail list logo
