In version 1.50, coming in the next couple of days, Fargo will do a lite render of RSS descriptions.
What "lite" means
It passes the text through the global glossary.
It passes the text through your cmsPrefs.opml glossary, if you have one.
It passes the text through the Markdown processor.
What's unprocessed
This will help the text in the feed look good in whatever RSS apps your readers are using. But it will still leave macros unprocessed, and it won't use any local glossaries. And the pagetable elements, if you reference them, will be unevaluated.
These things are difficult, but not impossible. However there are lots of other things that are higher priority.
Also, you have to watch out for glossary items that depend on the runtime environment of Fargo-generated pages. Anything that depends on Font Awesome being present, or Bootstrap Toolkit, won't work. I do that in my smiley characters.
But the cheesecake glossary entry should render fine.
Sunday or Monday
I want to spend some time using the new version myself (I'm using it now) before making it part of the main release. This is tricky stuff and I want to be sure I got it right.
The only change in Fargo 1.49 was that Font Awesome 3 has been replaced with version 4.
This was not a small change, unfortunately, even though the goal was to make it appear as if it was a small change. Please watch for breakage.
While I was working in this area I made it so that the left and right arrow keys move between panels in the Icon Chooser dialog (accessible from the Outliner menu in Fargo).
I also updated the GitHub project.
Editorial
Font Awesome is still very awesome.
But I wish they wouldn't rock the boat so much.
We've baked in support for this excellent toolkit deeply in Fargo. Such deeply integrated things are not easily replaced, especially when lots of small seemingly unnecessary changes are made.