[fixed] 2.2.x Private Messages

[Logician]

FYI about the conversion of 2.2.x to 3.x:

Either the conversion script or the new vb3 code is not friendly with Non-English chars. Non-english chars. in my old private messages have been ruined when you upgraded vbulletin.com to vb3. I was able to view them without any problems in vb.2.2.x. (Not char. encoding problem btw.) This would be a bad sign for upgrading of non-english boards as you might guess so I thought you would want to check it out.

Ps. moved from here (http://www.vbulletin.com/forum/showpost.php?postid=374822&postcount=129)

[Floris]

Originally posted by Logician
FYI about the conversion of 2.2.x to 3.x:

Either the conversion script or the new vb3 code is not friendly with Non-English chars. Non-english chars. in my old private messages have been ruined when you upgraded vbulletin.com to vb3. I was able to view them without any problems in vb.2.2.x. (Not char. encoding problem btw.) This would be a bad sign for upgrading of non-english boards as you might guess so I thought you would want to check it out.

Ps. moved from here (http://www.vbulletin.com/forum/showpost.php?postid=374822&postcount=129)

Hopefully a temporary glitch in the Matrix :)

I recently have upgraded my categories with an International one, so I would love to see those conversations being displayed properly. But I think it will be possible to fix this. (at least I am keeping my eye on these kind of threads)

[Chen]

You can see this here too:
http://www.vbulletin.com/forum/showthread.php?threadid=34497&mode=linear&perpage= 40&pagenumber=1

[Paul]

Originally posted by Logician
FYI about the conversion of 2.2.x to 3.x:

Either the conversion script or the new vb3 code is not friendly with Non-English chars. Non-english chars. in my old private messages have been ruined when you upgraded vbulletin.com to vb3. I was able to view them without any problems in vb.2.2.x. (Not char. encoding problem btw.) This would be a bad sign for upgrading of non-english boards as you might guess so I thought you would want to check it out.

Ps. moved from here (http://www.vbulletin.com/forum/showpost.php?postid=374822&postcount=129)

This is a problem (most likely) with the character set being defined in vB3. vB2 (despite HTML coding standards) does not include a character set meta tag.

At the top of vBulletin3 pages, you'll see:


<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />

This causes your browser to render the text on the page using the ASCII character set only, which does not include support for certain special characters.

This should probably be <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> instead, which would provide support for most western languages.

Of course, this will break any Eastern language installations of vBulletin. In the final version of vB3, this should probably be a option in the Admin CP (perhaps in the form of a replacement variable for {contenttype} like {htmldoctype} in vB2).

I just "whined" about this in the vB2 Troubleshooting forums the other day while mentioning a problem with other non-standard HTML usage in vB2. ;)
http://www.vbulletin.com/forum/showthread.php?threadid=59198



For example, the default headers that ship with vBulletin do not specify a character set--doing so without modifying the product setup or administration interface would be impractical for users who use vBulletin in non-Western settings as specifying a western character type would cause their sites to parse incorrectly for their users.

Best wishes,
Paul

Edit: I should add that I'm just guessing here--this may be a problem with the conversion script. If someone sends me a zipped copy of vB3, I'll be happy to check it out ;)

[Paul]

Well, I needed an excuse to play with attachments on vB3.. so... :)

Attached is the Infopop thread that Chen provided a link to as viewed with vB3 using the us-ascii charset...

[Paul]

With iso-8859-1...

[Streicher]

Why not using <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />. I think this will be the best choice.

[Andy Z]

Originally posted by LoveShack
With iso-8859-1... In Mozilla wiht US-ASCII, the undefined character marking that it shows, aslo appears in all Sticky titles:
"Important: "<- A wierd character appears right there. It disappears if the encoding is changed.

[Andy Z]

Originally posted by Streicher
Why not using <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />. I think this will be the best choice. UTF-8 does not solve the problem of the TM symbol or the Sticky issue I posted above.

BTW, isn't UTF-8 basically just ASCII? I'm not sure if I saw something about this or not.

[Paul]

Originally posted by Streicher
Why not using <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />. I think this will be the best choice.

The best choice is an admin cp user-definable option. To make it work like it did with vB2, use iso-8859-1.

[Floris]

Originally posted by LoveShack
The best choice is an admin cp user-definable option. To make it work like it did with vB2, use iso-8859-1. You can .. in vb2 too :) Just add it to the header

[Paul]

Originally posted by xiphoid
You can .. in vb2 too :) Just add it to the header Well, of course. ;) I mean in the same way {htmldoctype} is defined by default as a replacement.

[Scott MacVicar]

you can edit the content type in the style settings.