I don't know what kind of database software is used here on FAA, but most database software goes completely nuts when it sees punctuation marks because punctuation marks mean something different to a computer than they do to a human. I expect that's why we can't use them here.
As a programmer I can tell you that while technically true it is certainly easily overcome with a little creative programming. It is done everyday.. I think it is just not on the priority list of the programming staff here.
I have worked around this somewhat by using a capitol "I" as a divider. I used to use a small "l" (ell) but Sean switched the header so all words begin with a capitol and my "l" became "L" and I had to go back and change all my titles that I had done this to. I don't know why he did this because standard titles don't start every word with a capitol-words like "the" and I don't think it would affect the google search. Jim Vansant
My workaround is to use the 'real' title -- with proper punctuation, case, etc. -- as the first line of my description. That way, there's at least a chance of having the correct title seen and (hopefully) appreciated.
@Mary -- Interesting! I've never been able to make that happen. Though dashes/hyphens and apostrophes work okay.
That's odd, Wendy. I have two titles (that I can think of off the top of my head) that have had question marks in them for over a year. I know they didn't work when I first joined in 2010. I also have apostrophes in some, but commas and dashes don't work. Nor do accent marks. In fact, accent marks don't even work in keywords, which I would like because the foreign names of places, etc. are spelled wrong in my descriptions without the accent marks.