Olivia Attwood and Bradley Dack's split was 'caused by his infidelity as he quietly rekindles romance with ex-girlfriend' - after estranged wife is seen kissing Pete Wicks
How Sadiq Khan-backed 'Barcelona-on-Thames' housing estate will swell by 20,000 homes...despite fears over school places and GP appointments
THIS is where the old clothes you give to charity or carefully put in 'recycling bins' REALLY end up... (Squint hard enough and you may see your M&S bra in this fetid mound)
Half our house is owned in a trust by my husband's children from his first marriage: How do we unwind it?
Valero oil refinery in Port Arthur explodes into flames triggering massive boom as smoke billows through Texas air
Inside the abandoned Pontins holiday park where squawking seagulls have replaced thousands of tourists
Trump envoy 'travels to Pakistan hoping for talks with Iran' as feared missile barrage across Gulf fails to materialise: Hopes rise of diplomatic end to war - but Tehran says suggestion of a deal is 'fake news'
Prices for these 10 modern-classic supercars have gone into orbit in the past three months
Cyberattack on a Car Breathalyzer Firm Leaves Drivers Stuck
Read more of this story at Slashdot.
Viral video claims 'loophole' allows drivers to avoid Stansted drop off charges
Meningitis I thought was food poisoning almost killed me twice
Trump's team eye Iran's parliament speaker as a US-backed leader - despite his repeated threats to America and criticisms of the President
CodeSOD: The Barren Fields
Today, it's not exactly the code that was bad. For some time, a government agency had been collecting information from users using fillable PDF forms. The user would submit the form, and then a data entry clerk would copy the text from the form into a database. This, of course, raised the question: why was someone manually riding the copy/paste button?
Sally was tasked with automating this. The data is already in a digital format, so it should be easy to use a PDF library to parse out the entered data and insert it into the database. And it almost was.
Sally shares with us, not code, but the output of her program which scanned the fields, looking for their names:
FieldType: Text FieldName: T5ZA1 FieldNameAlt: T5ZA1 FieldFlags: 25165824 FieldJustification: Left FieldMaxLength: 3 --- FieldType: Text FieldName: T5ZA2 FieldNameAlt: T5ZA2 FieldFlags: 25165824 FieldJustification: Left FieldMaxLength: 2 --- FieldType: Text FieldName: T5ZA3 FieldNameAlt: T5ZA3 FieldFlags: 25165824 FieldJustification: Left FieldMaxLength: 4I could go on, Sally certainly shared many more examples, but you can get the gist. The names were all cryptic five character blobs. They all start with T5Z, and followed by "letternumber": A3, B9, C2, etc. It has the vibe of being autogenerated; someone just never considered that they might want clear names for the fields, and just let their editor autonumber them, but that has one counterpoint to it: the letter "O" is never used. T5ZN9 is followed by T5ZP1.
Sally was left scratching her head. Of course, she was going to have to write some sort of lookup that would convert the PDF's field names into database field names, but she expected that the PDF would provide at least some sort of guidance on that front.
I really enjoy that the alt-text for every field is also the field name, which is a clear accessibility "win".