"C++" shows up as just "C" in book titles

see, for example:

http://www.librarything.com/work/1454513/book/53366726

Unfortunately LT doesn't always handle non-alphabetical characters correctly. But of course they might also be combined manually by somebody who is unaware there is a difference.

p.s.: Clearly this is a book about both though - sorry, I misunderstood you. It could be as simple as some import source having it wrong.

For your own copy of a book, the ++ disappears if you edit it in the catalog list, but remains if you edit it in the book details page.

It's a matter of escaping characters - it's been fixed and come unfixed at least three times that I'm aware of (over the 3+ years I've been on LT). As qebo said, if you only edit it on the Edit page it should stick, beware of editing in the catalog (for this particular bit of text).

Thank you for the workaround. There are different places you can edit a book--would you please be more specific as to how to reach the place where I can fix it? In other words, please dumb it down for me. :-) Again, thanks.

Your Books tab, List button -- this displays the catalog list. Double click the title in the Title column to edit, type a +, click Save. The + disappears.

In the catalog list, in the right hand column with various icons, click the pencil icon (says "edit book" when cursor is over it) -- this displays the book details page in editable form. Edit the text in the Title box, type a +, click Save. The + remains.

Thanks. This bug also shows up when you use the import tool, by the way (http://www.librarything.com/import)

So...it's on the list of bugs to be fixed, right? :-)

I came across another place where this is a problem. Under "Your Books" in the search box, entering c++ fails; the '++' disappears from the search box when you hit the button, and the page returns:

Search: c x

No books found in this collection.

8> Yeah - and I can't find a workaround for that. Quoting doesn't help, nor does escaping the pluses (searching c\+\+). Hmmm - nope, HTML codes don't do it, either. Sheesh! Getting worse...

ETA - fix escape characters