Bug #37465
Configuring a different encoding for CSV export doesn't work
| Status: | Resolved | Start date: | 2012-05-24 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
I tried to make the CSV export of the BE module a bit more Excel friendly, so I set the TSConfig options tx_formhandler_mod1.config.csv.delimiter and .encoding. While setting an alternative delimiter works fine, the exported file is always encoded as utf-8, regardless of the TSConfig setting.
When digging into the code, it seems to me this feature is not fully implemented at the moment? The desired output encoding is set in Tx_Formhandler_Generator_CSV.php, but there doesn't actually seem to happen a charset conversion.
The attached patch adds the desired behavior and fixes a copy-paste error when setting the default value of "encoding". Please let me know if I somwhow missed something and setting a custom ouput charset works different than I expected.
Associated revisions
Configuring a different encoding for CSV export doesn't work (fixes #37465)
Configuring a different encoding for CSV export doesn't work (fixes #37465)
History
Updated by Reinhard Führicht 12 months ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r62894.