Submitted by yngens on Sat, 11/19/2016 - 04:27
Today I've got the following message from Authentic Theme:
Detected that you are using en.UTF-8 character set and not utf-8, which is strongly recommended. Strange  character might appear in text-editor mode and/or other encoding issues are going to happen. Change language in Virtualmin Configuration to en.UTF-8 and make sure, that your browser also detected it correctly.
Note the recommendation to set "utf-8" in the first sentence goes against the recommendation for "en.UTF-8" in the second sentence. Please make up your mind between the two and set the correct message.
Status:
Closed (fixed)
Comments
Hi,
Obviously it's not intended and should only appear if you don't have utf8 set.
What is your current charset?
Submitted by JamieCameron on Sat, 11/19/2016 - 14:05 Comment #3
A recommendation to use the
en.UTF-8
language instead of justen
wouldn't be unreasonable. In fact, recent Webmin installs useeu.UTF-8
by default.Submitted by yngens on Sat, 11/19/2016 - 16:15 Comment #4
You guys seem to miss the subject matter. Read carefully the first and then the second sentence of the message given and then you will understand : the first one suggest one thing, the second one - completely another thing.
Submitted by dlynes on Sat, 11/26/2016 - 09:01 Pro Licensee Comment #5
@yngens is saying that authentic theme is saying that he's using UTF-8, but then suggesting that he's not and he should be. (i.e. utf-8 vs en.UTF-8)
Hi,
I have made stricter checkups. This message will only show up when you don't use
uft*
charset for any of the languages.Thanks for reporting.
It will be enhanced in 18.30.
Submitted by yngens on Thu, 12/01/2016 - 19:27 Comment #8
Well, I believe my point is totally missed. Ilya, just translate two sentences into Russian and you will see it.
Ты пойми, что первое предложение строго рекомендует utf-8, а второе - наоборот en.UTF-8.
Compare
utf-8, which is strongly recommended
with
Change language in Virtualminr Configuration to en.UTF-8
Submitted by yngens on Thu, 12/01/2016 - 19:28 Comment #9
Have to open this again as the point is missed again.
Hi,
:)
I have understood to what you were saying after the first glance. I have written this.
What should never be happening is that you have:
Detected that you are using "en.UTF-8"...
, it always should be non-utf string, like:Detected that you are using "en"...
.I have no idea how did this happen on your side that you're having this message to appear. Strings were converted to lowercase() before comparison prosidure.
Can you tell me what are the settings in:
I will try to reproduce it. However, I tweaked code a bit already but still I don't see how it happened on your side. This message shouldn't have appeared at the first place.
What browser are you using?
I think it's better to change the sentence to just saying:
Detected that you are using non-unicode charset...
..but still, what you should have had is
en
in the first part and noten.UTF8
The message will be changed to the clearer one.
I think it should be better.
I expect it not to be displayed for you anymore in 18.30+
New message example: http://rostovtsev.ru/pub/src/authentic/18.30b/langiage_warning_message_u...