Fix typos.
This commit is contained in:
parent
c773b1b2ce
commit
3ac0e706ad
|
@ -387,9 +387,9 @@ Backwards Compatibility
|
||||||
|
|
||||||
The semantics of unicode.encode with errors="replace" has changed:
|
The semantics of unicode.encode with errors="replace" has changed:
|
||||||
The old version always stored a ? character in the output string
|
The old version always stored a ? character in the output string
|
||||||
even if no character was mapped to ? in the mapping. With the
|
even if no character was mapped to ? in the mapping. With the
|
||||||
proposed patch, the replacement string from the callback callback
|
proposed patch, the replacement string from the callback will
|
||||||
will again be looked up in the mapping dictionary. But as all
|
again be looked up in the mapping dictionary. But as all
|
||||||
supported encodings are ASCII based, and thus map ? to ?, this
|
supported encodings are ASCII based, and thus map ? to ?, this
|
||||||
should not be a problem in practice.
|
should not be a problem in practice.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue