The discussion revolves around a “Body is invalid” error message appearing on short posts despite the minimum post length setting being adjusted. Stelmsind investigates the issue and finds the problem in the TextSentinel code, which disallows all uppercase content in English. sam suggests submitting a pull request (PR) to add a site setting to override this. Stelmsind agrees to submit a PR. However, codinghorror reveals that a setting called “allow uppercase posts” already exists. layerssss points out that this issue affects non-alphabetical languages, but sam notes that customized settings for non-English locales are now shipped to address this issue.
Hey,
On short posts I’m still getting:
Body is invalid; try to be a little more descriptive
But I have set all of the following configuration:
min post length: 1
min first post length: 1
body min entropy: 1
min topic title length: 1
title min entropy: 1
Ah, so the problem is here, in TextSentinel:
def seems_quiet?
# We don't allow all upper case content in english
not((@text =~ /[A-Z]+/) && !(@text =~ /[^[:ascii:]]/) && (@text == @text.upcase))
end
There isn’t any option to override this at present time.
feel free to submit a PR for a site setting.
Sure. Hopefully I’ll have the time in the next week. It’ll be my first ever PR! 
GREAT I AM LOOKING FORWARD TO THE ADDITION OF THIS SETTING!
Haha. I think I might add an extra knob so that you can allow all capitals
if it’s only one word
NEAT!
The setting exists and is called allow uppercase posts for anyone that needs it.
NOW I CAN SEE WEATHER REPORTS LIKE THEY ARE MEANT TO BE.
(Assuming that “teletype” is how they are meant to be.)
This is having fatal effects on non-alphabetical languages like “PHP 是最好的语言”
Note, these days we ship we customised settings for non English locales which take care of this issue.