[Octave-bug-tracker] [bug #46771] symbolic/sympy oct-package fails

[anonymous]

Follow-up Comment #13, bug #46771 (project octave):

The decoding was fixed by adding following lines to the end of decoding_table
in file cp1252.py:

    'u23a1'   #  0x5B -> LEFT SQUARE BRACKET
    'u23a2'   #  0x7C -> VERTICAL LINE
    'u23a3'   #  0x5B -> LEFT SQUARE BRACKET
    'u23a4'   #  0x5D -> RIGHT SQUARE BRACKET
    'u23a5'   #  0x7C -> VERTICAL LINE
    'u23a6'   #  0x5D -> RIGHT SQUARE BRACKET
    'u22c5'   #  0x2A -> ASTERISK

However, all encoding errors, for example for

int(f,x)

.
'charmap' codec can't encode characters in position 196-197: character maps to
<undefined>
.

continued. And the encoding possibly should be unique (?) not including
several alternatives. I don't know if these fixes are correct (of course more
precise character to character matching is clearly necessary). There are
ASCII-characters xC4 and xC5 both defined in decoding_table (and thus in
encoding_table also, i suppose) but still error is that they are "undefined".
I tested that these xC4 and xC5 characters function expectedly in octave and
in python without any errors.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46771>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/