# 带有全大写和图像的正文

**URL:** <https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646>\
**Category:** Feature\
**Created:** [2018年十一月24日 02:25 UTC](https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646 "2018-11-24T02:25:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![marianord](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marianord/32/90502_2.png) [@marianord](https://meta.discourse.org/u/marianord)\
**Post date:** [2018年十一月24日 02:25 UTC](https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646/1 "2018-11-24T02:25:55Z")

</div>

I’ve seeing and issue where posts with all caps text and images, doesn’t trigger any issue with the `uppercase` check.

Here is the setting unchecked (as expected)

![image](https://global.discourse-cdn.com/meta/original/3X/1/d/1d9692fe4f6b155a45f29a036dba01a5dc37f454.png)

And here’s the post:

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/9/f9e3b846abce90a6aa27aa665f76997be7c15a1d.jpeg)

The link if you want to see it live is: [Puntas de tripoides y copas - Club Corsa CCV](https://clubcorsavenezuela.com/t/puntas-de-tripoides-y-copas/13705)

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2018年十一月26日 00:32 UTC](https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646/2 "2018-11-26T00:32:13Z")

</div>

Tricky, this is related to the image in the post, it causes a bypass.

We can not really have a partially working site setting though 🙂

@codinghorror how much do you want this fixed ?

The problem is that we need to do this particular test on `Raw -> Cooked -> converted back to text without images`. This adds definite cost into the pipeline.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2018年十一月26日 00:50 UTC](https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646/3 "2018-11-26T00:50:44Z")

</div>

I don’t feel this rare case is worth doing a lot of extra engineering work for. There are lots of ways to bypass. Putting `&nbsp;` in your post would work too, for example.

---

<div class="post-metadata">

**Author:** ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)\
**Post date:** [2018年十一月26日 01:05 UTC](https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646/4 "2018-11-26T01:05:37Z")

</div>

Just an idea: maybe another way of dealing with with this would be to make the setting trigger at 90 percent uppercase or so?

---

<div class="post-metadata">

**Author:** ![marianord](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marianord/32/90502_2.png) [@marianord](https://meta.discourse.org/u/marianord)\
**Post date:** [2018年十一月26日 03:39 UTC](https://meta.discourse.org/t/post-body-with-full-uppercase-and-images/102646/5 "2018-11-26T03:39:00Z")

</div>

I really like this idea.

I was thinking maybe in a regex, to avoid taking into account [\*]( \* ) something like that. So the most common use cases, without trying to really bypass the limitation like emojis, links, images, are excluded from the parsing.