iso-8895-1 error

177 views
Skip to first unread message

Neybar

unread,
Jul 31, 2009, 12:23:36 PM7/31/09
to Bots Open Source EDI Translator
I'm not positive when this error started, but yesterday I updated my
bots install to 1.5.4. I used the updatebots_to1_5_4.zip file.

Now in some of my routes I'm getting this error:

File "/home/ci/bots/lib/python2.5/site-packages/bots-1.5.3-py2.5.egg/
bots/inmessage.py", line 29, in edifromfile ediobject.initfromfile
(ta_info) File "/home/ci/bots/lib/python2.5/site-packages/bots-1.5.3-
py2.5.egg/bots/inmessage.py", line 53, in initfromfile
self._readcontent_edifile() File "/home/ci/bots/lib/python2.5/site-
packages/bots-1.5.3-py2.5.egg/bots/inmessage.py", line 263, in
_readcontent_edifile self.rawinput = botslib.botsreaddata
(filename=self.ta_info['filename'],charset=self.ta_info
['charset'],errors=self.ta_info['checkcharsetin']) File "/home/ci/bots/
lib/python2.5/site-packages/bots-1.5.3-py2.5.egg/bots/botslib.py",
line 607, in botsreaddata f = botsopen(filename,'r',charset,errors)
File "/home/ci/bots/lib/python2.5/site-packages/bots-1.5.3-py2.5.egg/
bots/botslib.py", line 602, in botsopen return codecs.open
(filename,mode,charset,errors) File "/usr/lib/python2.5/codecs.py",
line 820, in open info = lookup(encoding) LookupError: unknown
encoding: iso-8895-1

I jumped into my python debugger just for kicks and
>>import codecs
>>codecs.lookup('iso-8895-1')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
LookupError: unknown encoding: iso-8895-1

I tried this on a few machines, none of which worked. I poked around
in my db, to see if anything is setting the charset to iso-8895-1, but
I can't find it.

Any idea why this would be happening now?

-James

Neybar

unread,
Jul 31, 2009, 12:28:05 PM7/31/09
to Bots Open Source EDI Translator
I answered my own question. I kept digging a little deeper and found
in one of my grammar files:
syntax = {
'charset' : 'iso-8895-1',
}

I changed that to latin1 and it seems to be working OK now.

Did something change from bots 1.5.3 to 1.5.4 that would invalidate
the iso-8895-1 charset?

Thanks,
James

hjeb...@gmail.com

unread,
Jul 31, 2009, 12:40:23 PM7/31/09
to bots...@googlegroups.com
hi James,

must be a typo.
it really is   iso-8859-1
iso-8895 is: Shaped insulating refractory products -- Determination of cold crushing strength

you wouldn't want to use that as a charset ;-)

kind regards,
henk-jan

hjeb...@gmail.com

unread,
Jul 31, 2009, 12:46:01 PM7/31/09
to bots...@googlegroups.com
mmmh, I see why this happened.
bots 1.5.3 used the charset of the in-channel to read the file.
this was not how it was meant to be...the charset of the message has to be used (and is used in 1.5.4).


kind regards,
henk-jan

Neybar wrote:

Neybar

unread,
Jul 31, 2009, 12:53:45 PM7/31/09
to Bots Open Source EDI Translator
OK, So I've had this error for a while then and it just now popped up
with 1.5.4

And I'm notorious for transposing letters/numbers so I'm sure that I
meant iso-8859-1

-James

On Jul 31, 10:46 am, "hjebb...@gmail.com" <hjebb...@gmail.com> wrote:
> mmmh, I see why this happened.
> bots 1.5.3 used the charset of the in-channel to read the file.
> this was not how it was meant to be...the charset of the message has to be used (and is used in 1.5.4).
> kind regards,
> henk-jan
> Neybar wrote:I answered my own question. I kept digging a little deeper and found in one of my grammar files: syntax = { 'charset' : 'iso-8895-1', } I changed that to latin1 and it seems to be working OK now. Did something change from bots 1.5.3 to 1.5.4 that would invalidate the iso-8895-1 charset? Thanks, James On Jul 31, 10:23 am, Neybar<ney...@gmail.com>wrote:I'm not positive when this error started, but yesterday I updated my bots install to 1.5.4.  I used the updatebots_to1_5_4.zip file. Now in some of my routes I'm getting this error: File "/home/ci/bots/lib/python2.5/site-packages/bots-1.5.3-py2.5.egg/ bots/inmessage.py", line 29, in edifromfile ediobject.initfromfile (ta_info) File "/home/ci/bots/lib/python2.5/site-packages/bots-1.5.3- py2.5.egg/bots/inmessage.py", line 53, in initfromfile self._readcontent_edifile() File "/home/ci/bots/lib/python2.5/site- packages/bots-1.5.3-py2.5.egg/bots/inmessage.py", line 263, in _readcontent_edifile self.rawinput = botslib.botsreaddata (filename=self.ta_info['filename'],charset=self.ta_info ['charset'],errors=self.ta_info['checkcharsetin']) File "/home/ci/bots/ lib/python2.5/site-packages/bots-1.5.3-py2.5.egg/bots/botslib.py", line 607, in botsreaddata f = botsopen(filename,'r',charset,errors) File "/home/ci/bots/lib/python2.5/site-packages/bots-1.5.3-py2.5.egg/ bots/botslib.py", line 602, in botsopen return codecs.open (filename,mode,charset,errors) File "/usr/lib/python2.5/codecs.py", line 820, in open info = lookup(encoding) LookupError: unknown encoding: iso-8895-1 I jumped into my python debugger just for kicks and>>import codecscodecs.lookup('iso-8895-1')Traceback (most recent call last):   File "<stdin>", line 1, in <module> LookupError: unknown encoding: iso-8895-1 I tried this on a few machines, none of which worked.  I poked around in my db, to see if anything is setting the charset to iso-8895-1, but I can't find it. Any idea why this would be happening now? -James
Reply all
Reply to author
Forward
0 new messages