Excellent. Encoding is a problem, though for strange characters. There is a way
to clue a text editor into the fact that it is looking at unicode. Mine had
problems. XMLSpy did better, but still the characters came out wrong. See below
for more on this encoding issue, which is really a different bug, it just affect
accuracy of output.
http://vegbank.org/vegbank/DisplayPlot.do?resultType=ASCIIEvironment&vegbankAccessionNumber=VB.832
needs to enclose values with a comma in quotes of some sort. This leads me to
believe that other special character escaping also needs to be employed. For
now, we may consider using the miscrosoft standard (sad, so sad) which is to
repeat a quote to escape it, and enclosed a string in quotes to make a comma not
represent a field break.
ie to show the field: This is "quite" a nice day, don't you think?
could be:
"This is ""quite"" a nice day, don't you think?" [or]
'This is "quite" a nice day, don''t you think?'
----encodings---
Unicode representation in obs=635
635,Pinus monophylla Torr. & Frè«®,0.5,H,37.5
correct, as seen in psql: Pinus monophylla Torr. & Frém.
(note the reversal of the slash on e ).
[side note that: 'Achnatherum speciosum (Trin. Rupr.) Barkworth' as seen on
web-view of this plot should be 'Achnatherum speciosum (Trin. & Rupr.)
Barkworth' - this is part of the larger encoding problems.]