Opened 16 years ago
Last modified 5 months ago
#7813 new defect (bug)
export function does not preserve encoding
Reported by: | tott | Owned by: | tott |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | minor | Version: | 2.7 |
Component: | Export | Keywords: | needs-testing has-patch |
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 (11)
#3
follow-up:
↓ 9
@
16 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
@
15 years ago
- Milestone changed from Future Release to 2.9
- Severity changed from normal to minor
#9
in reply to:
↑ 3
@
10 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?
Note: See
TracTickets for help on using
tickets.
possible patch for encoding problem. needs testing