BOKF VODRFB AVF WAB LXF TOBJFU CFIEBLDFVL....ZITL GXEBQF HL LA FVQHVFFBHVQ VODRFB. - ZEDFT WKFDHVQ
Answer to yesterday's quote:
If we rely upon a legal principle to defend your position of the boundary and that principle has created a problem, not resolved it, then perhaps we need to reconsider which legal principle we should apply in order to determine the true intent of the landowners. -JBStahl
Hint below for today's CryptoQuote below
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
K=L
RULE NUMBER ONE FOR THE SURVEY DEPARTMENT
JPST CHARGE IT TO ENGINEERING NUMBER
JAMES FLEMING
LHADET- TADFLXHVQ HT EDHTT
Robert Hill, post: 356712, member: 378 wrote: RULE NUMBER ONE FOR THE SURVEY DEPARTMENT
JPST CHARGE IT TO ENGINEERING NUMBER
JAMES FLEMINGLHADET- TADFLXHVQ HT EDHTT
Thanks Robert. that should have been ZOTL (I couldn't paste it for some reason and had to retype it. I thought I checked it well)
MFVL EMBU, HVCFFC!
DDSM:beer:
Awry indeed!
I create these in upper-lower case; and in MSWord, I take the text and change it to "all-caps". But when I copy/paste the "all-caps" message to the board, it appears online in upper/lower case (I'm guessing the ascii-code is still upper/lower case and something happens in Word that doesn't eliminate the ascii code for the lower-case). I ended up typing it onsite with caps-lock on and had a typo. It's hard to type in Code. (and by the way, my name is LXADET) 😉
I'll create them in all-caps in the future and hopefully won't have to retype them in. A typo can obfuscate things further up when you trying to decypher.
