Text files generated by this module generally fail to load in Windows applications because of the \n Unix line break instead of expected Windows \r\n
I found no way to enforce these breaks: the \r part is always removed from the file.

How can this be addressed apart of a subsequent, manual processing of the files...

Thanks for help.

CommentFileSizeAuthor
#3 views_data_export-allow-windows-line-1942794-3.patch3.18 KBsteven jones

Comments

steven jones’s picture

steven jones commented
Version: 6.x-3.x-dev » 7.x-3.x-dev
Component: Miscellaneous » Code
Category: support » bug
Issue tags: +Needs tests

The line breaks really are "\r\n". I wonder if something is stripping the line breaks.
Sounds like a candidate for some tests.

steven jones’s picture

steven jones commented
Title: How to force windows line breaks in TXT / CSV files » Allow windows line breaks in TXT files
Category: bug » feature

We should allow a way to configure what line breaks are used in TXT files I think.

steven jones’s picture

steven jones commented
Status: Active » Needs review
StatusFileSize
new views_data_export-allow-windows-line-1942794-3.patch3.18 KB

Initial work on adding some tests for windows line breaks.

The last submitted patch, views_data_export-allow-windows-line-1942794-3.patch, failed testing.

steven jones’s picture

steven jones commented
Issue summary: View changes
Status: Needs work » Closed (won't fix)

Sorry for the lack of attention to your issue, please accept my apologies.

Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.

As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on #3492246: Close down Drupal 7 issues.

If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)