Hi Lukas,
Thank you very much for your interest in this problem. I have attached
two sample documents, both are .doc files generated by Open Office 2.4.
I generated the error by simply copying and pasting the contents of the
documents into Pier's edit box. (I'm using Firefox on Ubuntu Linux.)
Sample_One does not work, while Sample_Two works just fine, and the only
thing I did in Sample_Two was delete the long dash between the words
"conclusion" and "whatever" and replace it with a period. So Magritte
is
not generating errors based on the encoding of the whole message, it's
responding to specific characters (which I assume it can't read.)
Thus my suggestion that the problem be solved by simply replacing those
characters with a question mark or a box, plus perhaps a message to the
user.
As to your suggestion that I add some code... I'd love to, but you could
put everything I know about Squeak in a thimble and have room left over.
(I plan to work on Squeak in my spare moments, but it will be many
months before I'm ready to contribute to a sophisticated project.) But
I'll happily submit additions to the documentation as appropriate, and
supply you with a continuing stream of bug reports as our development
goes forward.
Thanks,
Alex
Lukas Renggli wrote:
On Fri, May 15, 2009 at 11:00 PM, Alex Roston
<clover(a)pacbell.net> wrote:
According to our sysadmin, "we're using
the Wakom server adapter, plus the
most recent version of Magritte, Seaside, and Pier from Lukas, which we
updated may 14th."
Ok, I guess you are on Squeak/Pharo then.
The exact error message we're seeing read,
"Contents: Invalid input given."
I have included a screen shot, which I hope will not be rejected by the
mailing list program.
Ok, that doesn't look too bad. This is a validation check of Magritte.
You can easily change the error message by adding a method like this:
PRCase class>>descriptionDocumentYourPackage: aDescription
^ aDescription kindErrorMessage: 'There was a problem reading your
input because your word processor is not set to UTF-8.'
To be able to investigate the real cause of the problem I need some
more information. Could you send step by step introductions on how to
reproduce the problem. Maybe together with a Word document (I assume
this is the offender?) that I can copy from?
Cheers,
Lukas