Hi guys,
I am not trying to spam the list. It is just that I keep running into a bunch of issues these days.
I am export an mse model of CodeFoo (actually the same exception is raised for a few other models). The exporter crashes when it tries to write out a comment which contains some unicode characters. The comment is in
Character>>initCyrillicSmallCapital
The raised exception is "This character is not supported by this class of string". I think the solution would be to open the mse file stream as utf-8 encoded. I wonder if the importer would still work then.
The other option is to simply not print the unicode comments.
Cheers, Mircea.
perfect!
Hi guys,
I am not trying to spam the list. It is just that I keep running into a bunch of issues these days.
I am export an mse model of CodeFoo (actually the same exception is raised for a few other models). The exporter crashes when it tries to write out a comment which contains some unicode characters. The comment is in
Character>>initCyrillicSmallCapital
The raised exception is "This character is not supported by this class of string". I think the solution would be to open the mse file stream as utf-8 encoded. I wonder if the importer would still work then.
No idea Did you try?
The other option is to simply not print the unicode comments.
Cheers, Mircea.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The raised exception is "This character is not supported by this class of string". I think the solution would be to open the mse file stream as utf-8 encoded. I wonder if the importer would still work then.
No idea Did you try?
I changed the MooseModel>>exportMSEToFile such that it writes an utf-8 stream. Tested exporting and importing CodeFoo and works without problems so I commited the change to MooseDevelopment.
Mircea.
cool and mircea don't refrain you from posting. We are communicating.
I can tell you that there is a difference between our emails and "get a bigger penis"
Stef
On May 26, 2009, at 12:50 AM, Mircea Lungu wrote:
The raised exception is "This character is not supported by this class of string". I think the solution would be to open the mse file stream as utf-8 encoded. I wonder if the importer would still work then.
No idea Did you try?
I changed the MooseModel>>exportMSEToFile such that it writes an utf-8 stream. Tested exporting and importing CodeFoo and works without problems so I commited the change to MooseDevelopment.
Mircea.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Mircea Lungu -
stéphane ducasse -
Stéphane Ducasse