Timeline for Problem with NumberForm when exporting
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 21, 2014 at 10:15 | comment | added | Chris Degnen |
@Hubble07 - Export will evaluate NumberForm but in only the top level terms of a two-dimensional grid of data. That is, unless OutputForm is used, which somehow forces evaluation. Quite interesting.
|
|
Sep 21, 2014 at 8:51 | comment | added | Hubble07 | @ChrisDegnen But FullForm[t1] also shows NumberForm unevaluated and yet Export works in that case. | |
Sep 20, 2014 at 18:48 | comment | added | Chris Degnen |
@kguler - Yes, copy & paste evaluates the NumberForm statements. FullForm[t2] shows NumberForm unevaluated. So Export does not evaluate like copy & paste.
|
|
Sep 20, 2014 at 18:05 | comment | added | kglr |
Chris, if you copy/paste the output of t2 (OP's version) into the second argument of Export it works ok.
|
|
Sep 20, 2014 at 17:23 | comment | added | Chris Degnen |
The export format, which appears to be "Data" , seems to expect only a two-dimensional grid of data. So the nested items in the sublists are not being evaluated like the top level items during the Export process.
|
|
Sep 20, 2014 at 16:57 | comment | added | Hubble07 | This is fine but whats wrong with an extra bracket from the point of view of Export. I mean why Export fails to write the result given by t2. | |
Sep 20, 2014 at 16:48 | history | answered | Chris Degnen | CC BY-SA 3.0 |