- Feature Requests & Improvements
-
Questions
+9
Under review
How to escape @ symbol?
I'm making a second story entry (tutorial) and I faced a problem when liking to required sources.
The links in question contain @ symbol and stylizing breaks at it, whenever I try to neatly put the link behind a descriptive word [name](link) or just having the bare link.
The only solution I found was to put spaces on both sides of the symbol and ask people to copypaste the whole link and remove spaces but that's stupid.
What exactly happens:
Actual link: https://www.flickr.com/photos/34323424@N00/864254125/
How it comes out: https://www.flickr.com/photos/34323424[@N00](/N00)/864254125/
Duplicates
1
Customer support service by UserEcho
This sounds like a bug with the Markdown parser. That's non-standard behavior for the markup language.
That said, I know this isn't Flickr Support, but Flickr typically recommends using the share URL for linking to photos, not the URL you see in your browser's omnibar. You can find it in the Share dialog, by clicking the Share icon next to the Fave star. In this case, the share URL would be https://flic.kr/p/2jnwDc .
That should actually solve the problem until the bug is fixed.
Should probably be fixed anyway, I would imagine that will also break emails.
And thanks, I had no clue flickr had such a feature - I don't actually use the site other than randomly coming across it this time when I was searching CC-BY content to use in the said tutorial. Was also the first time I saw an url have the @ symbol, but I figured it's possible for them to have that :o
Until they hopefully allow proper formatting (BB Code and/or HTML) you should be able to escape markdown with a backslash. So \@ is supposed to render as just @.
This does appear as it should be a thing.
I'll investigate it a little, soon.
Please read my related proposal and explanation of the problems with Markdown here: http://support.furrynetwork.com/topics/650-/
At this point, links appear as plane text unless formatted for Markdown purposes. I've tested this with the link in the example, and it appeared fine. It's a bit annoying to have to copy/paste, but it works.
We're also working on bringing in a WYSIWYG editor; this should make links work better.