Bug #754

LaTex parsing on email notifications

Added by scott voth over 10 years ago. Updated over 10 years ago.

Priority name:
Category name:
BuddyPress (misc)
Target version:
Start date:
Due date:
% Done:


Estimated time:


I don't know if this is possible to even control - but when reviewing LaTex support on the Commons, I noticed that when email notifications are sent out, LaTex code is not parsed. So if a member contributes to a group forum, and that contribution has LaTex, it looks good in the forum, but the email notification goes out with the [latex] tags.


#1 Updated by Matt Gold over 10 years ago

  • Status changed from New to Assigned

Great catch, Scott.

#2 Updated by Boone Gorges over 10 years ago

Does anyone have suggestions for how this should be fixed? LaTeX rendering works like this: the TeX markup is sent to's server, which then converts it into an image file and sends it back to us for displaying inline. Our notification emails are plaintext (as opposed to HTML) and thus do not support inline images. So there are a few options:

1) Produce HTML emails. This will take a large amount of development, and still leaves the question of how we handle the issue for users who opt out of HTML emails (because their client will not support them)
2) Remove the [latex] shortcode tags, but leave the markup, figuring that people subscribed to such emails will be able to read the markup at least fairly well (and if not, they can click through to the web version)
3) Remove the shortcodes and the markup altogether, optionally replacing with an inline message (or a message in the footer) that says something like "This message contains LaTeX, which is best viewed in a browser. Click here..."

Or some combination thereof?

#3 Updated by Matt Gold over 10 years ago

I like #3, except that I think it would be better to include the entire message but to have some sort of symbol where the LaTeX images should be. That way, people can still see what was written, and they can check out the math if they want by clicking on a link.

#4 Updated by Boone Gorges over 10 years ago

Ok. Your suggestion sounds exactly like my #3 (not sure I understand your "except"), though I was suggesting a text link instead of a "symbol" -what do you have in mind?

#5 Updated by Matt Gold over 10 years ago

Sorry -- I misread it -- somehow I thought you wanted to replace the entire message with a link to the online version. A text link sounds perfect.

#6 Updated by scott voth over 10 years ago

Sounds great to me also. Thanks!

#7 Updated by Boone Gorges over 10 years ago

  • Target version set to 1.3

OK, thanks.

#9 Updated by Matt Gold over 10 years ago

How did we say we wanted to deal with notifications that should be sent to users when a relevant ticket was resolved? Because we should inform that math group about this.

Also available in: Atom PDF