Re: [WebDNA] Retrieving a PDF from an email
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101457
interpreted = N
texte = Thanks for your thoughts guys. What I have been trying to do is use WebDNA to collect mail and then enter the data into a database. To do this part I have been using the Shared POP widget that comes with all WebDNA installs. I then grab the required info out of the body of the email and populate an order database This has worked perfectly for me for all but one instance where the client is sending their order as an attached pdf, their order system can not be changed to a text email (they won't change, stubborn) so I have tried to extract the pdf and then using a nice little app that I found extracts the text from the pdf and then I can do my funky thing in the same way as a regular text email. Problem is that I can not convert the pdf from its BASE64 encryption using WebDNA as it seems to choke on (as suggested by Craig) a null character. I have not tried to do this with any other attachment type ie .jpg, .doc etc. Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 19/11/2008, at 4:45 AM, Govinda wrote: > I wrote an encryption tool once in visual basic using XOR, and that > resulting case of the null char bit me too. > Now my training on encryption amounts to like 3 pages of a book > written in 1998, but whatever it is worth, and IF this is the issue, > Donovan/Chris what I did was just tell my algorithm to leave the > char alone rather than let it XOR on that encryption/decrypt > iteration if it happened to be the same char as the one we were > about to use from the encrypt/decrypt seed (which would thus XORs > into the null char). Now if i understand right, what we are talking > about here is trying to decode something encoded by other software, > so I immediately profess ignorance since I have never even used > WebDNA's Base64 tool let alone what the creator of the pdfs do(es). > > Anyway like Steve, I was not actually working through (even in my > head) what Stuart is doing, just my experience led me to think like > this, so sorry if this is just noise. > > -G > > On Nov 18, 2008, at 9:15 AM, Kenneth Grome wrote: > >>> Maybe it's got nothing whatsoever to >>> do with the topic ... >> >> I think it has everything to do with the topic, and I'll bet >> that's exactly what's going on here. >> >> PDF's are binary files so they probably have one or more >> null characters in them, and if they do this explains why >> WebDNA chokes on them. >> >> Thanks Steve! >> >> Sincerely, >> Ken Grome >> >> >> >> >> >> >>> Don't know if it's relevant to your situation as I >>> haven't really been paying attention but, I had problems >>> trying to do an XOR thing a while back and I always found >>> that WebDNA choked whenever it came up against a null >>> character. Neither the decrypt or encode things seemed to >>> be able to get past them. May be that's the problem, I >>> never did get a workaround.. >>> >>> Cheers >>> PS Maybe it's got nothing whatsoever to do with the >>> topic, if so apologies for wasting this precious >>> bandwidth!! >>> > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/
Associated Messages, from the most recent to the oldest:
Thanks for your thoughts guys. What I have been trying to do is use WebDNA to collect mail and then enter the data into a database. To do this part I have been using the Shared POP widget that comes with all WebDNA installs. I then grab the required info out of the body of the email and populate an order database This has worked perfectly for me for all but one instance where the client is sending their order as an attached pdf, their order system can not be changed to a text email (they won't change, stubborn) so I have tried to extract the pdf and then using a nice little app that I found extracts the text from the pdf and then I can do my funky thing in the same way as a regular text email. Problem is that I can not convert the pdf from its BASE64 encryption using WebDNA as it seems to choke on (as suggested by Craig) a null character. I have not tried to do this with any other attachment type ie .jpg, .doc etc. Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 19/11/2008, at 4:45 AM, Govinda wrote: > I wrote an encryption tool once in visual basic using XOR, and that > resulting case of the null char bit me too. > Now my training on encryption amounts to like 3 pages of a book > written in 1998, but whatever it is worth, and IF this is the issue, > Donovan/Chris what I did was just tell my algorithm to leave the > char alone rather than let it XOR on that encryption/decrypt > iteration if it happened to be the same char as the one we were > about to use from the encrypt/decrypt seed (which would thus XORs > into the null char). Now if i understand right, what we are talking > about here is trying to decode something encoded by other software, > so I immediately profess ignorance since I have never even used > WebDNA's Base64 tool let alone what the creator of the pdfs do(es). > > Anyway like Steve, I was not actually working through (even in my > head) what Stuart is doing, just my experience led me to think like > this, so sorry if this is just noise. > > -G > > On Nov 18, 2008, at 9:15 AM, Kenneth Grome wrote: > >>> Maybe it's got nothing whatsoever to >>> do with the topic ... >> >> I think it has everything to do with the topic, and I'll bet >> that's exactly what's going on here. >> >> PDF's are binary files so they probably have one or more >> null characters in them, and if they do this explains why >> WebDNA chokes on them. >> >> Thanks Steve! >> >> Sincerely, >> Ken Grome >> >> >> >> >> >> >>> Don't know if it's relevant to your situation as I >>> haven't really been paying attention but, I had problems >>> trying to do an XOR thing a while back and I always found >>> that WebDNA choked whenever it came up against a null >>> character. Neither the decrypt or encode things seemed to >>> be able to get past them. May be that's the problem, I >>> never did get a workaround.. >>> >>> Cheers >>> PS Maybe it's got nothing whatsoever to do with the >>> topic, if so apologies for wasting this precious >>> bandwidth!! >>> > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/
Stuart Tremain
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[delete] problem (1997)
WebCatalog2 Feature Feedback (1996)
Table sorting by selected category then others (2004)
chicken / egg::purchase / setheader (2002)
RAM variables (1997)
Am I going senile? (Price recalc based on quantity) (1997)
return missing item (was:WebCat Sales) (1997)
Search syntax question (1998)
Websited Development (1999)
Multiple prices (1997)
Thanks and Big News!!! (1997)
WebCat2 - Getting to the browser's username/password data (1997)
Associative lookup style? + bit more (1997)
Date Range Issue (2006)
Problems appending to database (1997)
[WebDNA] Authorize working connection... (2019)
WebCatalog 2.0 b 15 mac (1997)
using listfiles to build a database? (2000)
Problem with formatting dates stored in db (2003)
Serving images from databases (1998)