|
Carbon dioxide posted:But nope, to remove ambiguity with clock times, ISO8601 has a completely different format for durations, which looks like 2H30M5S. That's fine and all but turns out the java time parsing library cannot deal with durations written as 2:30 and requires the 2H30 format. So I had to write my own parser for that. code:
|
# ? May 24, 2020 22:37 |
|
|
# ? May 23, 2024 16:18 |
|
I mean yes that's basically what I did. I never said it was hard. Just annoying.
|
# ? May 25, 2020 07:01 |
|
https://twitter.com/tansokudesuga/status/1264905078911066114 Translation: We asked 100 people "Did you watch 72 Hour Television*?" Didn't watch it: 90 people Watched it: 10 people *some dumb 72 hour telethon
|
# ? May 26, 2020 09:24 |
|
Mr. Fix It posted:https://twitter.com/tansokudesuga/status/1264905078911066114 10%? Whoa, that's nearly half!
|
# ? May 26, 2020 11:02 |
|
Someone took "the last 10% is half the work" too literally.
|
# ? May 26, 2020 11:39 |
|
You miss 10% of the pie charts you don't take.
|
# ? May 26, 2020 14:58 |
|
Unperson_47 posted:Now, also switch our time system over to beats and you're onto something. Swatch Internet Time! I remember the few months that cnn.com actually included .beats on their site.
|
# ? May 27, 2020 21:00 |
|
And beats are actually French Revolutionary Time minutes renamed so it's maybe the right time* for it * pun accepted but not intended
|
# ? May 27, 2020 21:12 |
|
My company has a large continental European office and a large US office. Don't ask me about how annoying it is that the decimal point is a decimal comma over there instead.
|
# ? May 27, 2020 23:58 |
|
Munin posted:My company has a large continental European office and a large US office. Don't ask me about how annoying it is that the decimal point is a decimal comma over there instead. How the hell do CSV files work over there? Does everyone just use bar delimited? Escape characters everywhere?
|
# ? May 28, 2020 20:40 |
|
Sardonik posted:How the hell do CSV files work over there? Does everyone just use bar delimited? Escape characters everywhere? Semicolons as the value separators.
|
# ? May 28, 2020 21:09 |
|
Sardonik posted:How the hell do CSV files work over there? Does everyone just use bar delimited? Escape characters everywhere? surrounding in quotes is the usual way. For example: "column, 1 has a comma in it", column 2 does not, "column 3, does also"
|
# ? May 28, 2020 21:30 |
|
Platystemon posted:Emphasis mine: This is pages back but it's driving me nuts and I can't find anything on google.What's with the dead cat near the bottom of the painting?
|
# ? May 28, 2020 22:02 |
|
Here is one interpretation.quote:The brothers have been disembowelled (in fact, there is talk of cannibalism in contemporary accounts of the killings), which suggests ritual slaughter or even some kind of black mass. This impression is reinforced by the dead cat seen bottom centre, cats (and especially their butchering) being closely associated with witchcraft and other acts of devil worship.
|
# ? May 29, 2020 00:08 |
|
Sardonik posted:How the hell do CSV files work over there? Does everyone just use bar delimited? Escape characters everywhere? CSVs are the devil's work as well.
|
# ? May 29, 2020 00:20 |
|
CSV files are fine. Ok, my CSV files are fine. If no one else touches them. And then I import them into a database. And delete them.
|
# ? May 29, 2020 00:40 |
|
CSVs are great because you can import then directly into excel and do some real data analysis.
|
# ? May 29, 2020 01:45 |
|
LeastActionHero posted:CSVs are great because you can import then directly into excel and do some real data analysis. https://i.imgur.com/dHbZeDM.gifv
|
# ? May 29, 2020 02:06 |
|
Munin posted:My company has a large continental European office and a large US office. Don't ask me about how annoying it is that the decimal point is a decimal comma over there instead. Yeah I'm in a country where that is the case as well and it's annoying as gently caress. Especially when some two-bit web developer doesn't account for the comma as decimal separator in a text input and there's no helpful error message telling the user that the poo poo's hosed.
|
# ? May 29, 2020 02:16 |
|
CSVs are fine for certain types of data. Data that contains commas does not fall into that category.
|
# ? May 29, 2020 03:10 |
|
Just use the record and unit separator control characters.
|
# ? May 29, 2020 05:18 |
|
Hail Satan.
|
# ? May 29, 2020 06:07 |
|
Tab separated values are superior in almost every way.
|
# ? May 29, 2020 06:47 |
|
I wanna know the WORST way to store data in plaintext.
|
# ? May 29, 2020 06:49 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. undelimited
|
# ? May 29, 2020 06:51 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. If you assume that you'll want a computer to do math to it at some point, the worst way is natural language.
|
# ? May 29, 2020 06:56 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. csv, but typed into a word doc
|
# ? May 29, 2020 07:06 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. Whatever the Voynich manuscribe did
|
# ? May 29, 2020 07:07 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. Handwritten cursive note scanned as a low-res JPG.
|
# ? May 29, 2020 07:11 |
|
AreWeDrunkYet posted:Handwritten cursive note scanned as a low-res JPG. And converted back to plain text using one of those image to ASCII art converters.
|
# ? May 29, 2020 07:21 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. Real life thing I have dealt with: Fixed width format with a documentation file that goes "parse chars 1 to 5 as the ID, parse chars 6 to 11 as the date, we have no idea what chars 12 to 35 do so ignore them, 36 - 45 is the description" and so on. Tbf I heard the application that generates this stuff is a legacy 1980s thing.
|
# ? May 29, 2020 07:22 |
|
Platystemon posted:Whatever the Voynich manuscribe did Voynichese is the only true way of storing data
|
# ? May 29, 2020 07:23 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. You'll get many answers but the true answer is proprietary fixed width files. ANYTHING delimited is preferable. E: Carbon dioxide posted:Real life thing I have dealt with: This person gets it. Also EDI was made by Satan.
|
# ? May 29, 2020 07:24 |
|
Parsing the FAA’s wind forecasts: Wind direction and speed get a four‐digit block. The first two are magnetic azimuth, in tens of degrees. The latter two are speed in knots. Wind ten degrees west of south at ninety‐nine knots would be 1999. But wait! What if the wind speed crosses a hundred knots? I’m glad you asked. In that case, you subtract a hundred from the wind speed and add fifty to wind direction. Let’s say the wind direction is still the same, and now it’s a hundred and sixty‐nine knots. Now it’s denoted with 6969. Wind data can also be encountered six‐digit groups. Surely this must be giving three digits to each component, right? Wrong. The wind digits are unchanged. Temperature just got appended to it. 696969 is wind ten degrees west of south, blowing a hundred and sixty‐nine knots, with ambient air temperature of sixty‐nine degrees Celsius. Sixty‐nine degrees Celsius is an unreasonably high temperature. You’d never see it in a real forecast. Except you might, because negative sixty‐nine degrees can be seen at altitude. That raises the question “how are negative and positive temperatures differentiated?” Oh. That’s easy. Negative temperatures have a minus sign in front of them. So that 696969 should really be 6969-69. …except when it isn’t, because the preface to the forecast informed you that all temperatures above FL240 were below zero so they would be omitting all the signs. What a sensible system. If there were any positive temperatures, they have plus signs, as seen below in the chart for Colorado and nearby states.
|
# ? May 29, 2020 07:27 |
|
Platystemon posted:Parsing the FAA’s wind forecasts: Holy smokes. Unperson_47 has a new favorite as of 07:30 on May 29, 2020 |
# ? May 29, 2020 07:28 |
|
Platystemon posted:Parsing the FAA’s wind forecasts: Ha ha ha ha ha ha
|
# ? May 29, 2020 07:41 |
|
MARC21, my fellows: http://www.loc.gov/marc/specifications/specrecstruc.html The only thing I've ever run across that actually *does* use the ASCII FS, US, RS, GS characters. In the catalog system I occasionally have to tinker with, MARC records are stored in a database. In multiple rows if necessary, because the field length is 990 characters. Why 990? gently caress you, that's why. Just use the sequence numbers and cat the results together like a normal person.
|
# ? May 29, 2020 07:57 |
|
Carbon dioxide posted:Real life thing I have dealt with: oh yeah, i used to work at a payments company, we had to deal with those all the time. your credit card charges have to pass through a lotta big iron.
|
# ? May 29, 2020 08:37 |
|
CSVs in Continental Europe are divided by semicolons.
|
# ? May 29, 2020 08:39 |
|
|
# ? May 23, 2024 16:18 |
|
Unperson_47 posted:I wanna know the WORST way to store data in plaintext. In traditional Chinese characters. Written into a word doc and no punctuation
|
# ? May 29, 2020 08:42 |