Project

General

Profile

Bug #883

Export to two flat ASCII tables with default attributes:test

Added by Michael Lee almost 20 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Normal
Category:
misc
Target version:
Start date:
11/13/2002
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
883

Description

ML tests


Related issues

Blocks VegBank - Bug #864: Two flat ASCII tables with default attributesResolved11/13/2002

History

#1 Updated by Michael Lee almost 19 years ago

ML needs to test this and if so, confirm&close this bug and 864

#2 Updated by Michael Lee almost 19 years ago

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.]

#3 Updated by P. Anderson over 18 years ago

The export formatting options should be configurable in each user's preferences
(eventually). For now, I wrapped string fields in "double quotes" and am
escaping any double quote found in the field value with another double quote...

If users want the MS format, escape " as ""
If users want what we call the Standard way, use \" (later)
By default we'll use the MS way, and that's all we support now.

NOTE that single quotes are NOT escaped since [I presume] a field wrapped
entirely in "double quotes" needn't escape its 'single quotes'. Let me know if
this is incorrect and I'll fix it.

#4 Updated by Michael Lee over 17 years ago

changed from components that are to be deleted to "misc" so that bugs don't get
deleted with component. Sorry for all the email.

#5 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 883

Also available in: Atom PDF