On Monday, May 9, 2011 we will be implementing UTF-8 encoding across all of the forums.
What this means for our users:
All posts written in UTF-8 will be able to be read regardless of the language selection made at the bottom of each forum page - for example, if you have selected the Greek UTF-8 encoding, you’ll be able to read messages encoded in UTF-8 across the Russian, French, and other native language forums.
Any post written before May 9 will not be re-encoded as UTF-8. This means to view those posts, you will need to switch the encoding to the appropriate code page. In other words, we are not converting the old message content to be UTF-8 as that would require the forums be offline for much longer.
During the switch over, the web interface to the forums will be offline; the NNTP interface will still be available to those users who wish to use it. When the web interface comes back online, those messages will be synchronized as usual through our gateway.
For our English-speaking audience, the changes you’ll see will be minimal. This change mostly affects the non-English forums and is being implemented so users can switch languages in the interface and not encounter encoding issues in newly posted messages when dong so.
thank you, sounds like a giant step forward in openSUSE joining the world_wide web!!
–
CAVEAT: http://is.gd/bpoMD
[openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8 via NNTP]
Q: What do you get if you divide the circumference of a jack-o-lantern
by its diameter?
A: Pumpkin Pi!
And thinking that this is of minor interest to the English speaking part of the forums is not true. People posting in English often have e.g. Bengali or Arabic, Cyrillic, or … characters in their filenames, etc. and thus posting problems with those computer listings are mess until now.
On 2011-04-26 22:06, hendersj wrote:
> - Any post written before May 9 will not be re-encoded as UTF-8.
> This means to view those posts, you will need to switch the encoding
> to the appropriate code page. In other words, we are not converting
> the old message content to be UTF-8 as that would require the forums
> be offline for much longer.
Perhaps that can be done later in background?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 04/29/2011 09:36 AM, vazhavandan wrote:
>
>> if you name your browser and version maybe someone will know.
> Read my signature
>
>
ah…sorry…didn’t get down that far…but, sorry again, i can’t help
as i’ve never used seamonkey (nothing against it, just never used it)…
for opera i think this might work:
Menu Settings > Preferences > General (tab) > Language (section) >
Details (button), (spin) from whatever is there now (mine is iso-8859-1)
to utf-8 > Ok > Ok, done
i guess seamonkey would be as easy…just different labels and path…
On 04/29/2011 02:06 PM, hcvv wrote:
>
> Nope, the encoding is send by the server, either in the HTTP protocol or
> in the (X)HTML itself (or both). The browser has only to obey.
hmmmmm…ok…i thought it would make for a faster render, since the
browser setting is just tell the browser machinery what to expect…if
it is getting utf8 from the server (like when forums.opensuse changes)
then it is just ready to receive and nothing has to be detected and
render engine changed to accommodate the stream–woosh! but, if
iso-something is set and expected and utf8 is presented, then . . .
but, i could be wrong, i’m not a browser guru…heck, i’m not any kind
of guru…just a generalist, not a specialist on anything…except
breathing and few other essential ‘dependencies’
>
> Normaly there is no need to change the encoding in the browser
> settings, except when the information send by the server is missing or
> wrong.
oh, we know that it is impossible for the opensuse.org servers to send
anything missing or wrong, right?
oh, we know that it is impossible for the opensuse.org servers to send
anything missing or wrong, right?
I delibiratly said it this way because I am pretty sure that the forums software does it wrong all the time. It says it sends ISO-8859-1, but in fact it sends UTF-8 encoded UNICODE. Happily most of the time most browser seem to detect this and display the correct characters.
My idea is that after the change it will say that it sends UTF-8 when sending UTF-8 (at least that is my big hope).
I also hope very much that such anomalies as you can see on the home page on these forums will be repaired. Choose language English (or Dutch or several other for that matter) and look at the Greek part of that page. The headiing is prefect, but the rest is … (broken is an understatment imho). Unitil now I was to lazy to analyze that page to find iout what bytes are what and what they should represent and why they are interpreted as tehy are. But again I hope that this will be cured after the change.
In short, let us wait and see. And can not beworse as it is now IMHO.
But the question: do have to change anything in my browser configuration, I can answer with NO, because when you are surfing the net ,all sorts of pages coming in from all sorts of web-sites have all sorts of encoding and you as user never worry about it.
On 04/29/2011 03:36 PM, hcvv wrote:
>
> But the question: do have to change anything in my browser
> configuration, I can answer with NO, because when you are surfing the
> net ,all sorts of pages coming in from all sorts of web-sites have all
> sorts of encoding and you as user never worry about it.
On Wed, 27 Apr 2011 19:38:06 +0000, Carlos E. R. wrote:
> On 2011-04-26 22:06, hendersj wrote:
>> - Any post written before May 9 will not be re-encoded as UTF-8.
>> This means to view those posts, you will need to switch the encoding
>> to the appropriate code page. In other words, we are not converting
>> the old message content to be UTF-8 as that would require the forums
>> be offline for much longer.
>
> Perhaps that can be done later in background?
It’s not on the roadmap per se, but I suppose it’s a possibility. Though
we generally seem to find that people post before searching, so the
tradeoff may not be significant enough.
(Sorry for the delayed response, I was on the road yesterday).
