Opened 5 years ago

Last modified 4 years ago

#7813 new defect (bug)

export function does not preserve encoding

Reported by: tott Owned by: tott
Priority: normal Milestone: Future Release
Component: Export Version: 2.7
Severity: minor Keywords: export, encoding, i18n, needs-patch needs-testing
Cc: lloydbudd

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)

export.diff​ (782 bytes) - added by tott 5 years ago.
possible patch for encoding problem. needs testing

Download all attachments as: .zip

Change History (8)

tott — 5 years ago

possible patch for encoding problem. needs testing

comment:1   lloydbudd — 5 years ago

  • Cc lloydbudd added
  • Milestone set to 2.7
  • Version set to 2.7

comment:2   lloydbudd — 5 years ago

  • Keywords has-patch added

comment:3   westi — 5 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.

comment:4   Denis-de-Bernardy — 4 years ago

  • Milestone changed from 2.8 to Future Release

comment:5   Denis-de-Bernardy — 4 years ago

  • Component changed from i18n to Export

comment:6   Denis-de-Bernardy — 4 years ago

  • Milestone changed from Future Release to 2.9
  • Severity changed from normal to minor

comment:7   ryan — 4 years ago

  • Milestone changed from 2.9 to Future Release
Note: See TracTickets for help on using tickets.