I add this issue from Richard here:

I'd like to report a small bug that I noticed: The N3 pages are served with a slightly sub-optimal Content-type header. For example:

$ curl -I http://linkedgeodata.org/page/node264695865.n3 HTTP/1.1 200 OK Date: Wed, 27 Apr 2011 18:21:34 GMT Transfer-encoding: chunked Content-type: text/rdf+n3

The media type for N3 is:

text/n3;charset=utf-8.

See [1] for reference and an explanation why the charset parameter is necessary. (Otherwise, the file will not display correctly in web browsers.)

[1] http://www.w3.org/TeamSubmission/n3/#mimetype