Message117586
| Author | vstinner |
|---|---|
| Recipients | amaury.forgeotdarc, ezio.melotti, lemburg, vstinner |
| Date | 2010-09-29.09:14:23 |
| SpamBayes Score | 1.274156e-05 |
| Marked as misclassified | No |
| Message-id | <201009291114.17306.victor.stinner@haypocalc.com> |
| In-reply-to | <1285744287.59.0.722291764266.issue9979@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> But shouldn't PyUnicode_AsWideCharString() merge surrogate pairs when it > can? The implementation doesn't do this. I don't want to do two different things at the same time. My plan is: - create PyUnicode_AsWideCharString() - use PyUnicode_AsWideCharString() everywhere - patch unicode_aswidechar() (used by PyUnicode_AsWideChar() and PyUnicode_AsWideCharString()) to convert surrogates when needed So, you agree with the API (and the documentation)? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-09-29 09:14:25 | vstinner | set | recipients: + vstinner, lemburg, amaury.forgeotdarc, ezio.melotti |
| 2010-09-29 09:14:24 | vstinner | link | issue9979 messages |
| 2010-09-29 09:14:23 | vstinner | create | |