Skip to content

Commit

Permalink
Update README to specify that output.txt needs to use UTF-8 encoding
Browse files Browse the repository at this point in the history
I'm running into a lot of problems with Fatheads using the wrong
encoding. The processing scripts look for UTF-8 and often don't work
if some other encoding is used.
  • Loading branch information
rpicard committed May 21, 2012
1 parent bac0ff5 commit 13037f9
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions README.md
Expand Up @@ -98,6 +98,8 @@ Keywords: jQuery

Please name the output file output.txt (tab delimited) but do not store the data file(s) in the repository (as noted above) unless it is under 1MB.

The output file needs to use UTF-8 encoding so we can process it. Please make sure you write your parse scripts accordingly or we'll probably run into some problems getting it integrated.

The output format from parse.xx depends on the type of content. In any case, it should be a tab delimited file, with one line per entry. Usually there is no need for newline characters, but if there is a need for some reason, escape them with a backslash like \\\n. If you wanta newline displayed, use <br>

The general output fields are as follows. Check out [https://duckduckgo.com/Perl](https://duckduckgo.com/Perl) for reference, which we will refer to in explaining the fields.
Expand Down

0 comments on commit 13037f9

Please sign in to comment.