# 大于和小于的意外格式

**URL:** <https://meta.discourse.org/t/unexpected-formatting-of-greater-than-and-less-than/44479>\
**Category:** Product Support\
**Created:** [2016 年5 月 19 日 07:21 UTC](https://meta.discourse.org/t/unexpected-formatting-of-greater-than-and-less-than/44479 "2016-05-19T07:21:51Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

作者： ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
发布日期： [2016 年5 月 19 日 18:48 UTC](https://meta.discourse.org/t/unexpected-formatting-of-greater-than-and-less-than/44479/6 "2016-05-19T18:48:12Z")

</div>

> [@GaurangTandon](#):
>
> But shouldn’t these HTML tags be interpreted only when they are written like \<b\> and not when \<b?

Similarly, only when `<a>` and not when `<a ` ?

Parsing characters can be done, and indeed already is.

But there is a wide range between “don’t parse anything” and “parse everything that could possibly be there”.

for a contrived example

```plaintext
if(count<a){
 if((amount=="all")&&(time>24)){

```

you wouldn’t want to get a link like `<a){ if((amount=="all")&&(time>`

In other words, regular expressions and conditional testing _could_ be used, but having enough code in place to deal with everything would be extreme.

What is most commonly done is what is done here. a compromise. Be it bbCode, Handlebars, HTML MarkDown, i.e.

As long as the text is entered in a certain format it will be parsed.

When something is not in a certain format when it should be, and when it shouldn’t be but is, that’s when there’s a problem.

---

_[View the full topic](https://meta.discourse.org/t/unexpected-formatting-of-greater-than-and-less-than/44479)._