Opened 17 years ago
Last modified 7 months ago
#7813 new defect (bug)
export function does not preserve encoding
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Future Release | Priority: | normal |
| Severity: | minor | Version: | 2.7 |
| Component: | Export | Keywords: | 2nd-opinion close |
| Focuses: | Cc: |
Description
when exporting strings are always converted to utf-8 while header and encoding is set to encoding used in blog.
this causes trouble when importing later.
Attachments (1)
Change History (12)
#3
follow-up:
↓ 9
@
17 years ago
- Keywords needs-patch needs-testing added; has-patch removed
- Milestone changed from 2.7 to 2.8
Moving to 2.8 for now.
Needs a new patch and some testing before commit:
We can't rely on mb_ functions existing so we need a fallback for that.
#6
@
17 years ago
- Milestone changed from Future Release to 2.9
- Severity changed from normal to minor
#9
in reply to:
↑ 3
@
11 years ago
Replying to westi:
We can't rely on mb_ functions existing so we need a fallback for that.
Several years on, and the only real fallback is to see if the function_exists before calling it. Still, that would hopefully catch a fair proportion of affected cases, wouldn't it?
#11
@
7 months ago
- Keywords 2nd-opinion close added; needs-testing has-patch removed
This report has to be further discussed. I know that has been stalling for more than one decade, and it looks more like "close me and don't open the grave, please".
Patch is obviously not applying, although, it's pretty easy to fix. The big question here is: *should we fix it?
Recently, working for providing support outside UTF-8 has been commented against #62172, and I agree, specially because we are now in 2025.
For me, this is a wontfix clear close candidate.
possible patch for encoding problem. needs testing