Thank you for your post.
I have confirmed this with my own testing, and I see that this has previously been reported to our Development and Testing departments. At this time, there is no additional information available.
For anyone who runs into this apparently rare problem, you can run the following from the command line:
perl -i -pe 's/\015/\012/g' yourfile.txt
Will convert the Mac line endings to Unix.
Yep, and it's *still* broken in version 10... So - 4 major releases now (7-10) - any chance of this one getting fixed yet? Pretty, pretty, pretty please? Even if it only exports them to the DOS line endings would work!
This issue seriously needs bumping. FMP 11 and line endings are still Mac whatever the file format. This must be fixed!
is there a way to convert Mac line endings to Windows or DOS through XSLT?
I'm trying to create a .csv file to import into UPS Worldship and while I can open the Filemaker-generated .csv in Excell and resave it as a Windows .csv, it would be much better to automate the whole process.
Whew, here in 2016, and FileMaker v15, a full 8 years after this was reported, and yet FileMaker on OS X is still spitting out CR-only text files, which is way, way legacy even in Apple's view.
CR-only format breaks all kinds of stuff and devs have to jump through all kinds of hoops to correct it because FMI still hasn't corrected this ridiculous default.
Exporting should be CR+LF by default, perhaps with an option to set it to CR-only or LF-only if you want to provide that for weird situation where you need those formats.
C'mon guys....this kind of stuff mucks with the cross-platform claims of FileMaker and makes our lives miserable.
I have escalated this issue to Development and Testing for discussion. When I receive any feedback, I will let you know.
Mac OS X continues to use the CR (ASCII-13) for line breaks in a text file, while Unix uses LF (ASCII-10). Windows uses both CR and LF.
Thanks for escalating.
Your statement about default line-endings is incorrect, however. The Macintosh platofrm last used CR (ASCII 13) for line breaks in text files back in 2001 with the last version of Mac OS 9.
OS X has always used LF (ASCII 10) as the native line breaks, just like the underlying unix that drives it. Save a plaintext file in TextEdit and then open it in TextWrangler or BBEdit to see the LF-only line breaks.
However, that's really immaterial to this discussion. FileMaker is designed and marketed as a cross-platform product, and its output must similarly be cross-platform. The platform-specific and hard-coded line-ending behavior of the Export File script step and other similar functions isn't appropriate to a cross-platform product, and it triggers the need for all kinds of obnoxious workarounds and extra coding to be able to generate text files that will work everywhere (i.e. CR+LF).
If there must be one one hard-coded line-ending behavior, it should be CR+LF in all platform versions of FileMaker, as that's pretty much universal. In the extremely rare circumstance where CR-only or LF-only text files would actually be required, then the current batch of obnoxious workarounds could be employed.
There are several Ideas posted to this forum for revising the Import and Export to allow greater control of the delimiters and encoding. This would be one of those delimiters requested!! For end-of-line, we should have a choice of CR, LF or CRLF (of any other character that might be used in data exchange with another system). The platform making the exchange should NOT be a factor, as Windows or Mac or iOS users can be creating documents read by another, or reading documents created by another.
This should be the #1 request for the next version. Pretty please?
beverly and JohnDCCIU:
Your suggestions for CR+LF and choice of delimiter has been attached to the original report.