Here it comes, the root of our problem. There are dozens of “common” formats out there like HTML, Markdown, BBCode, Textile, XML, TeX, Wiki Markup, etc. People also tend to bring their own extensions to such markups when implementing their systems, making the problem even bigger. After all, we’re developers… introducing new standards fires the natural “why not?” approach.

Who cares?! What’s the problem with it?

Not taking into consideration the limitations imposed by some markup languages, the most important problem with this is interoperability.

The fact is that content produced by end-users of our systems can be used in different contexts, for many different purposes. For example:

• In a web page, which nowadays must be responsive and adapt to different devices.
• In a native application.
• In e-mails, either as content or notifications.
• In printed material.
• In server-side search systems.

Added to the above, we must also take into consideration that data produced in one application can be used by another one. Finally, machines, like search engines, may “read” the text. They must be able to understand it and to retrieve the additional value that rich-text provides.

Summing up, deciding for the right data format is a non-trivial and critical task.

Rich-Text Editors (RTEs)

Yolo. This is the end.

‍