Rich Text support in Hyperkitty
Hi All,
I have been recently working on adding rich text support through markdown in Hyperkitty so that emails can be made easier to read. The core design idea in my mind when working on this was building something that doesn't bother writers of plain text emails too much, but allows people to write emails in markdown.
The supported syntax is limited Markdown, for example:
Hyperkitty's Markdown Syntax
- List items are supported
- Even nested ones
- Headers with
#aren't supported, mostly due to their widespread use as comments in code shared on mailing lists. - You can **emphasize** text and _itcalize_ them too
- Block code and
inline codeworks. - URLs work like they usually do.
- Images _do work_, but are disabled by default because of their potential for tracking users. They need to be enabled by administrators through a configuration flag.
def sample():
return "yay"
While text intentionally written for Markdown rending looks pretty good, plain text sometimes isn't as good. I have applied my branch1 on both the Mailman installations for these two lists (mail.python.org & lists.mailman3.org).
Any feedback or bug reports on weird looking stuff is welcome here or directly on my PR
-- thanks, Abhilash Raj (maxking)
Headers with # aren't supported, mostly due to their widespread use as comments in code shared on mailing lists. I do not understand this, if you write a code snippet, it will not recognize the
#a markdown syntax. So there should be no problem.
The supported syntax is limited Markdown Why not full markdown? I have given my response to the problem above. What other reasons are there? Am I missing something here?
On Sat, Jun 22, 2019, at 12:26 AM, Aaryan Bhagat wrote:
Headers with # aren't supported, mostly due to their widespread use as comments in code shared on mailing lists. I do not understand this, if you write a code snippet, it will not recognize the
#a markdown syntax. So there should be no problem.
The problem is that people don't know that they are writing code segments.
import hello # This is a comment which would become H1 def hello_world(): print(hello.world)
The above code segment is what I hope to not break.
Code intentionally written for Markdown won't break, that is right. But over emails, people aren't writing markdown, they are writing plain text.
The idea is to opportunistically render plain text emails as Markdown without making it look weird.
The supported syntax is limited Markdown Why not full markdown? I have given my response to the problem above. What other reasons are there? Am I missing something here?
Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-leave@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3
Security Policy: https://wiki.list.org/x/QIA9
-- thanks, Abhilash Raj (maxking)
participants (2)
-
Aaryan Bhagat -
Abhilash Raj