The "Input is Invalid" Error

>> I'm involved in a project which uses the Pier wiki.
>>    
>
> If you talk about encodings you should mention the platform you are
> using, the version of the platform, the server adaptor, the version of
> Seaside, the version of Magritte and Pier.
>
> Encoding problems show up from time to time, but usually they can be
> solved by fixing the configuration you use.
>  

>  
>> If one pastes something from a non-UTF-8
>> compatible world processor, it is rejected with an error message reading,
>> "Input is Invalid."
>>    
>
> What kind of error message? A Magritte error within the page, a
> Seaside error within a separate page, or even a debugger within the
> image?
>  

> 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."
>
> 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.
>
> Thanks,
>
> Alex
>
>
> Lukas Renggli wrote:
>>> I'm involved in a project which uses the Pier wiki.
>>>
>>
>> If you talk about encodings you should mention the platform you are
>> using, the version of the platform, the server adaptor, the version  
>> of
>> Seaside, the version of Magritte and Pier.
>>
>> Encoding problems show up from time to time, but usually they can be
>> solved by fixing the configuration you use.
>>
>>
>>> If one pastes something from a non-UTF-8
>>> compatible world processor, it is rejected with an error message  
>>> reading,
>>> "Input is Invalid."
>>>
>>
>> What kind of error message? A Magritte error within the page, a
>> Seaside error within a separate page, or even a debugger within the
>> image?
>>
>> Cheers,
>> Lukas
>>
>>
>
> <Error_Message.png>_______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> But on which version?
> Because this is more tricky than that :)
>
> On May 15, 2009, at 11:00 PM, Alex Roston 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."
>>
>> 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.
>>
>> Thanks,
>>
>> Alex
>>
>>
>> Lukas Renggli wrote:
>>>> I'm involved in a project which uses the Pier wiki.
>>>>
>>>
>>> If you talk about encodings you should mention the platform you are
>>> using, the version of the platform, the server adaptor, the  
>>> version of
>>> Seaside, the version of Magritte and Pier.
>>>
>>> Encoding problems show up from time to time, but usually they can be
>>> solved by fixing the configuration you use.
>>>
>>>
>>>> If one pastes something from a non-UTF-8
>>>> compatible world processor, it is rejected with an error message  
>>>> reading,
>>>> "Input is Invalid."
>>>>
>>>
>>> What kind of error message? A Magritte error within the page, a
>>> Seaside error within a separate page, or even a debugger within the
>>> image?
>>>
>>> Cheers,
>>> Lukas
>>>
>>>
>>
>> <Error_Message.png>_______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Hi,
>
> The message is due to the Magritte validation checks of the form.
>
> Cheers,
> Doru
>
> On 16 May 2009, at 08:45, stéphane ducasse wrote:
>
>> But on which version?
>> Because this is more tricky than that :)
>>
>> On May 15, 2009, at 11:00 PM, Alex Roston 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."
>>>
>>> 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.
>>>
>>> Thanks,
>>>
>>> Alex
>>>
>>>
>>> Lukas Renggli wrote:
>>>>> I'm involved in a project which uses the Pier wiki.
>>>>>
>>>>
>>>> If you talk about encodings you should mention the platform you are
>>>> using, the version of the platform, the server adaptor, the version of
>>>> Seaside, the version of Magritte and Pier.
>>>>
>>>> Encoding problems show up from time to time, but usually they can be
>>>> solved by fixing the configuration you use.
>>>>
>>>>
>>>>> If one pastes something from a non-UTF-8
>>>>> compatible world processor, it is rejected with an error message
>>>>> reading,
>>>>> "Input is Invalid."
>>>>>
>>>>
>>>> What kind of error message? A Magritte error within the page, a
>>>> Seaside error within a separate page, or even a debugger within the
>>>> image?
>>>>
>>>> Cheers,
>>>> Lukas
>>>>
>>>>
>>>
>>> <Error_Message.png>_______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>
> --
> www.tudorgirba.com
>
> "If you interrupt the barber while he is cutting your hair, you will
> end up with a messy haircut."
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

> On Fri, May 15, 2009 at 11:00 PM, Alex Roston <[hidden email]> 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
>
>  

> On Fri, May 15, 2009 at 11:00 PM, Alex Roston <[hidden email]> 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
>
>  

> Hi Lukas,
>
> Thank you very much for your interest in this problem. I have sent  
> two sample documents to your regular email address as they are too  
> big for the mailing list. 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 <[hidden email]>  
>> 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
>>
>>
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Hi Lukas,
>
> Thank you very much for your interest in this problem. I have sent two
> sample documents to your regular email address as they are too big for the
> mailing list. 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 <[hidden email]> 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
>>
>>
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

> Thanks for sending the sample documents.
>
> I tried to reproduce with all of the following 36 possible combinations:
>
> - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux
> - WAKom / WAKomEncoded
> - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux
> - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux
>
> I cannot reproduce the problem.
>
> Maybe you can try to temporarily replace
> MAContainerComponent>>validate to see if there is something strange
> going on with exceptions ...
>
> MAContainerComponent>>validate
> self withContainersDo: [ :each | each doValidate ].
> ^ errors isEmpty
>
> Cheers,
> Lukas
>
> On Sat, May 16, 2009 at 6:14 PM, Alex Roston <[hidden email]> wrote:
>  
>> Hi Lukas,
>>
>> Thank you very much for your interest in this problem. I have sent two
>> sample documents to your regular email address as they are too big for the
>> mailing list. 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 <[hidden email]> 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
>>>
>>>
>>>      
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>>    
>
>
>
>  

> Thanks for sending the sample documents.
>
> I tried to reproduce with all of the following 36 possible  
> combinations:
>
> - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux
> - WAKom / WAKomEncoded
> - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux
> - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux
>
> I cannot reproduce the problem.
>
> Maybe you can try to temporarily replace
> MAContainerComponent>>validate to see if there is something strange
> going on with exceptions ...
>
> MAContainerComponent>>validate
> self withContainersDo: [ :each | each doValidate ].
> ^ errors isEmpty
>
> Cheers,
> Lukas
>
> On Sat, May 16, 2009 at 6:14 PM, Alex Roston <[hidden email]>  
> wrote:
>> Hi Lukas,
>>
>> Thank you very much for your interest in this problem. I have sent  
>> two
>> sample documents to your regular email address as they are too big  
>> for the
>> mailing list. 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 <[hidden email]>  
>>> 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
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>

> Thanks for sending the sample documents.
>
> I tried to reproduce with all of the following 36 possible combinations:
>
> - Pier 1.1.1 on Mac / latest Pier on Mac / Pier 1.1.1 on Linux
> - WAKom / WAKomEncoded
> - Safari 3 on Mac / IE 6 on Windows / FireFox 3 on Ubuntu Linux
> - Microsoft Word 2008 on Mac / Open Office 2.4 on Ubuntu Linux
>
> I cannot reproduce the problem.
>
> Maybe you can try to temporarily replace
> MAContainerComponent>>validate to see if there is something strange
> going on with exceptions ...
>
> MAContainerComponent>>validate
> self withContainersDo: [ :each | each doValidate ].
> ^ errors isEmpty
>
> Cheers,
> Lukas
>
> On Sat, May 16, 2009 at 6:14 PM, Alex Roston <[hidden email]> wrote:
>  
>> Hi Lukas,
>>
>> Thank you very much for your interest in this problem. I have sent two
>> sample documents to your regular email address as they are too big for the
>> mailing list. 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 <[hidden email]> 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
>>>
>>>
>>>      
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>>    
>
>
>
>