Forums
Feed Informer Support

1. bojack
   Member

   Hello again:

   I am digesting a feed and displaying only the title of each item. Alas, the source of the feed insists on putting language at the end of every single title that's exactly the same. I'd love to get rid of all that repetitive language. Is there any way to do it?

   Say the titles of several items read as follows:

   Yankees win pennant [Baseball News]
   Mets swoon down stretch [Baseball News]
   Joe Torre caught dogfighting [Baseball News]

   Is there a way to get rid of the [Baseball News] at the end of each title? They will be exactly the same for the title of every item, and at the end.

   Thanks for your help -- I am loving this service.

   Posted 16 years ago #

2. admin
   Key Master

   Yes. We have a tag to do substitutions. It should go somewhat like this:

   <gsub from="[Baseball News]" to="">%TITLE%</gsub>

   Try it out. I didn't double check I wrote that right. If it fails, try something simpler like:

   <gsub from="News" to="">%TITLE%</gsub>

   And work your way up.. :) I'm not sure if the angled brackets might cause issues or not..

   Posted 16 years ago #

3. bojack
   Member

   Turns out, they're not angled brackets around the words -- my mistake. They're regular parentheses, ( and ) . gsub gets rid of the words (hurray!), but not the parentheses. Maybe if I use the html code names of the parentheses?

   Posted 16 years ago #

4. admin
   Key Master

   As long as it matches exactly how they're represented, you /should/ be okay. So view source on the raw HTML digest, see how the ( and ) are notated, then use that.

   Posted 16 years ago #

5. bojack
   Member

   The raw HTML shows them as simple parentheses, but gsub won't take them out.

   I've worked around this by using gsub and the description field, which has the words but not the parentheses. Works well.

   Posted 16 years ago #

6. admin
   Key Master

   I think this is something to do with parentheses being reserved characters. I'll have a deeper look when I next go into the code :)

   Posted 16 years ago #

RSS feed for this topic

Reply

You must log in to post.