5 ms·
> US (Unit Separator), RS (Record Separator), GS (Group Separator), and FS (File Separator) are the only 4 remaining of the 8 information separators (ISi) (or d
by JKCalhoun 5y ago
> US (Unit Separator), RS (Record Separator), GS (Group Separator), and FS (File Separator) are the only 4 remaining of the 8 information separators (ISi) (or data delimiters) that I put in in 1961 September.
And I'm thinking — why not one separator and the byte that follows indicates Unit/Record/Group/File/etc.?
Amazing though that we know the moment and the person (and the reason) that specific ASCII characters were added.
Were we defining ASCII for the first time now, I suspect the BELL control code would be gone — perhaps replaced by the smiley-face?
- KerrAvon 5y agoJust a guess, but modern readers often forget how precious memory was at that time — an extra byte per record would potentially have been a costly amount of extra storage.
- gerdesj 5y ago"why not one separator and the byte that follows" That's an extra byte ... a whole extra byte! 20 odd years later my ZX80 had 1KB of RAM and a portion of even that was unavailable for the end user. My C-64 had a whopping err 50ish? KB usable RAM. My 80286 1MB. etc. This laptop has 32GB.
- chrismcb 5y agoSure, but they only had 127 characters to play with
- gerdesj 5y ago"I suspect the BELL control code would be gone" I remember my mum getting her first electronic typewriter. It went bing at the end of the line to warn you, just like the old manual jobbies. I guess that was BEL in action. Later models had a buffer that you typed into and then it would spew text onto the paper when it knew what to do with your text to avoid splitting words or whatever lowly skills it had with typesetting.
- colanderman 5y agoI've always been curious, whether any popular systems made good use of US/RS/GS/FS. E.g. I'm surprised never to have seen any support for CSV files using US/RS instead of TAB/(CR)LF or comma/(CR)LF. Or any support in Unix to use RS instead of LF or NUL to delineate records.
- wglb 5y agoI've written something that uses RS. The mind boggles at how much trouble (including security issues) if the inventors of CSV understood all of ASCII.
- function_seven 5y agoA few years ago I was consuming a SOAP webservice from a Remedy ticket handling system. While developing my end of it, I saw all sorts of weird 3-character clusters in some notes fields. I don't remember what they were exactly, but something like � (I just did that in CyberChef, I don't think that's what it really was at the time. It was only 3 glyphs I'm sure.) I started digging into it, a eventually worked out that some system at the start of the chain was using the ASCII US and RS characters to separate the notes! Each note would have the format of timestamp␟username␟note␞timestamp␟username␟note and so on. Then, through some chain of black boxes I never got to see, those ASCII values were converted into the visual ones I used above (U+241E and U+241F), then those were misinterpreted into Latin1 or some other non-Unicode encoding. What came out the other end were the jumbled messes I saw. I ended up just searching and splitting on those messy characters to recover the structured format of the notes. (They were all dumped into a single field in the SOAP record. I hate SOAP enough as it is, but was amazed how our systems managed to ruin it even more :)
- thaumasiotes 5y ago> I've always been curious, whether any popular systems made good use of US/RS/GS/FS. That can't be done; the concept of a "record separator" character already assumes that there is a value that can't occur within the data. If you play along with that, you're not making good use of anything. You're better off using commas and being forced to constantly confront the fact that tons of data contains commas than using a byte value that hides the problem slightly better than commas do.
- saurik 5y agoFWIW, the two smiley faces in DOS were where "start of heading" and "start of text" are in ASCII.