[Sigia-l] Tag separators in text fields - standardise please

Paola Kathuria paola at limov.com
Thu Jul 31 10:22:50 EDT 2008


Ziya Oz wrote:
> Now, technology and the intertubes could conceivably make some sense of this
> mess

Here're a few comments from on a post a few years ago
http://www.37signals.com/svn/archives2/tag_formats_cant_we_all_just_get_along.php

brad / 05 Dec 05
> I would vote for the quotes, because that’s how you search
 > for specific phrases in Google and I reflexively put quotes
 > around key phrases in other programs/search engines just as
 > a force of habit.

Jan / 05 Dec 05
> I guess you could just do both. If the user uses quotes, then
 > use the flickr style to parse it. If the user uses commas,
 > then use 43things style to parse the string.

Zzypt / 05 Dec 05
> Smart parsing is the answer. I want quotes to work when I use
 > them; so that I can include commas and spaces. Then commas should
 > separate tags and if there are no commas then use spaces.
 >
 > Ever used a credit card validation that expected dashes or
 > spaces to separate numbers into groups of four, then the next
 > site requires no separation? I wrote a credit card validation
 > routine once that got a higher sales rate when I accepted
 > spaces, dashes or even no spaces. I checked the validation
 > error file regularly and if there were new separation styles
 > being tried, then I added those. When money is at stake you want
 > to accept all users idea of a credit card number.

I hereby change my futile request to allow for both.


 > Paula


Paola



More information about the Sigia-l mailing list