Project

General

Profile

Actions

Bug #41793

closed

Use UTF-8 by default in Flexforms and Backend

Added by Benni Mack over 11 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2012-10-09
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.0
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Was: FlexFormTools array to XML does not use UTF-8 by default

When using FlexFormTools, and no $LANG->charSet is set, then the XML header is written with an empty character set. This happens if you use this function in your own extension and not in the backend e.g., but also when instantiating the storages (this is where I noticed it).

Thus, we introduce a fallback to UTF-8. This is the same way, GeneralUtility (t3lib_div) - array2xml_cs does it.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #56841: Remove deprecated initCharset from DocumentTemplateClosed2014-03-12

Actions
Actions #1

Updated by Benni Mack over 11 years ago

  • Status changed from New to Accepted
  • Assignee set to Benni Mack
Actions #2

Updated by Gerrit Code Review over 11 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15446

Actions #3

Updated by Benni Mack over 11 years ago

  • Subject changed from FlexFormTools array to XML does not use UTF-8 by default to Use UTF-8 by default in Flexforms and Backend
Actions #4

Updated by Gerrit Code Review over 11 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15446

Actions #5

Updated by Gerrit Code Review over 11 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15446

Actions #6

Updated by Benni Mack over 11 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #7

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF