Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: re: chunky errors


From   Christopher Baum <[email protected]>
To   <[email protected]>
Subject   st: re: chunky errors
Date   Sun, 21 Nov 2010 11:17:58 -0500

<.
Dmitri said

Peeking at the first 2 lines of raw_price_data.csv

  1003,2008-03-23,0,Disc,NULL,7.99,7.87678139240359,8.35,8.56885514506366,10.7974394069005,NULL,10.2566666666667,6.99,6.99,7.99,7.77333333333333,10.36
> 5,NULL,NULL,5.99,5.99,5.99,NULL,


I suspect this file may have been saved as Unicode (e.g., UTF-8) and that the non-printing characters represent a BOM (Byte Order Mark). There is no reason for a .csv file to be saved as Unicode unless there is content that does not appear in the full 256-character ASCII set (8-bit ASCII). If a file contained something like, e.g., accented characters from Polish or Turkish, or text in Cyrillic, it could end up as UTF-8.

Kit



Research Papers in Economics (RePEc)
http://repec.org




*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index