• Michael R (unregistered)

    FieldType: Text FieldName: T5ZA1 FieldNameAlt: T5ZA1 FieldFlags: 25165824 FieldJustification: Left FieldMinLength: 5 FieldMaxLength: 5 FieldDefault: Frist

  • (nodebb)

    The Boulder is conflicted over the use of a bitmask (25165824 = 0x1800000) in a PDF. Are we still in the era of saving bytes? Please reassure The Boulder that it was converted to separate columns when writing to the database . . .

  • (nodebb)

    I'd like to see one of those forms actually... Because if you look at, say, tax forms where I live, all the fields are numbered. And for this kind of stuff, skipping "O" particularly makes sense, as it eliminates the risk of users confusing it for zero.

  • (nodebb)

    Oh and I see an opportunity to be the frist one to mention growing fucks in those fields.

  • (nodebb) in reply to Medinoc

    skipping "O" particularly makes sense

    True . . . but then it seems obvious that "I" should be skipped as well.

  • (nodebb) in reply to dpm

    The "flags" looks to come from the PDF spec. If I'm reading it right, the fields have the "Comb" (split into single-character boxes) and "DoNotScroll" (exactly what it says) flags set. Not really relevant information in this case, but it looks like Sally's code is just dumping the field definitions.

  • (nodebb)

    This is not a WTF. We don't no the background, but I'm sure there is some documentation out somewhere which explains exactly the meaning of each field.

    And it makes sense because each field is easily identifiable. For instance, if you want to marry your grandmother's stepsister, some documentation may tell you "fill out field C3 to C5", and there will be no discussion what exact fields these could be and where to find them.

Leave a comment on “The Barren Fields”

Log In or post as a guest

Replying to comment #693577:

Log Out

« Return to Article