Author |
Topic  |
MarcelG
Retired Support Moderator
    
Netherlands
2625 Posts |
Posted - 09 August 2006 : 01:40:03
|
Rui, oxle is now reverted back to as it was yesterday ;
<META HTTP-EQUIV="Content-Type" content="text/html; charset=iso-8859-1"> The characters I tried to support were some Turkish characters. Switching to Windows-1254 as characterset therefor solved my problem, at least, now the site supported the Turkish characterset. I also checked. However, that characterset does not suffice for my needs, as I want to support a wider characterset.
Regarding your PS ; the characters were inputted via a Turkish keyboard by 2 of my members who're on holiday there. They needed the normal i, but as the Turkish keyboards have the dotless i by default, they unintentionally got that one. And thát one got converted to #305;. |
portfolio - linkshrinker - oxle - twitter |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
MarcelG
Retired Support Moderator
    
Netherlands
2625 Posts |
Posted - 09 August 2006 : 06:29:31
|
Okay, I guess I have to read up on 'codepage values'. I've got no clue on what it is, so I guess it's time to Google  |
portfolio - linkshrinker - oxle - twitter |
 |
|
MarcelG
Retired Support Moderator
    
Netherlands
2625 Posts |
Posted - 09 August 2006 : 07:12:18
|
Wow!!!! This is brilliant!!! I've just added these two lines to config.asp, and changed the HTML characterset to UTF-8.
Response.CodePage = 65001
Response.CharSet = "utf-8"
Presto! The result is amazing! Mixed arabic, turkish russian and latin in a single topic!  |
portfolio - linkshrinker - oxle - twitter |
Edited by - MarcelG on 09 August 2006 07:23:19 |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
MarcelG
Retired Support Moderator
    
Netherlands
2625 Posts |
Posted - 09 August 2006 : 07:27:26
|
quote: Originally posted by ruirib
I told you . You will need to save your .asp files in utf-8 format too.
err...what do you mean with that ? Can I no longer just click the 'save' button in Crimson Editor before uploading the file via FTP ? |
portfolio - linkshrinker - oxle - twitter |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 09 August 2006 : 07:53:07
|
No weird characters in your pages HTML (not speaking of Db stored contents)? If not, then you're ok.
Anyway, all it takes is to choose UTF-8 as the saved format for the pages. If you use only "regular" chars, the need to use utf-8 will not be noticeable. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
MarcelG
Retired Support Moderator
    
Netherlands
2625 Posts |
Posted - 09 August 2006 : 09:12:02
|
Nope, no weird characters in my code.  Thanks for your help!!! This really makes my site more internationally appealing! |
portfolio - linkshrinker - oxle - twitter |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
gpspassion
Junior Member
 
260 Posts |
Posted - 12 January 2008 : 13:10:47
|
Just what I was looking for, so all it takes is adding these two lines to config.asp
Response.CodePage = 65001 Response.CharSet = "utf-8"
Where do you change changed the HTML characterset to UTF-8 though ? |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
TSAloha
Junior Member
 
USA
151 Posts |
Posted - 12 January 2008 : 14:20:52
|
Depending on what you are doing with Snitz forums unicoded. Changing Codepage and Charset in config.asp enables the base forums to handle unicode charsets - 6501 is for server codepage support and utf-8 is client side encoding support.
If you are creating a base Snitz forums with unicode to handle multilingual contents - whatever languages - but with Western European languages (a la ISO Latin 1 group), you really don't have to touch each file. Forum user interface will remain in English-US, but you can create Categories/Forums (Admin) in whatever languages you prefer, and posting can be in any languages, which will be rendered in whatever locale language input you use - multilingual content delivery.
What Rui mentions above is more for non-Western European languages or languages with special chars/symbols that would need to be properly rendered, especially in case of Asian languages.
There are some basic notes on this issue in the documentation forum of the test unicode forum (V3406 unicode forums internationalized with 4 languages): MUAF-Multilingual Unicode ASP Forums |
Edited by - TSAloha on 12 January 2008 15:52:18 |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
sadra
Starting Member
Iran
30 Posts |
Posted - 12 January 2008 : 23:45:28
|
quote: Originally posted by ruirib
Taku is a real specialist in Unicode based forums, probably the most experienced person on the issue here, right now, so better heed his advice.
hi,
on this forum, JUST: Add below code on top of "inc_header.asp"
Session.Codepage = 65001 Response.Charset = "utf-8"
and after <head> tag add: <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> JUST
See the Example: http://www.basamid-ngo.com/ this site based on forum snitz code
Good Luck |
[red]how soon is too late[/red] |
Edited by - sadra on 12 January 2008 23:49:04 |
 |
|
TSAloha
Junior Member
 
USA
151 Posts |
Posted - 13 January 2008 : 11:46:28
|
Yes, that accomplishes utf-8 support for forum contents handling. But you have to also define the same for inc_header_short.asp which is included in pop_preview etc. Also, meta tag definition is not really necessary if a default content type is defined in config.asp.
A best current example of unicoded site is oxle.com by MarcelG, I can think of.
After a lot of trial and error for a simplest and easy approach for unicode support with a base version I came to is to set: Session.Codepage = 65001 Response.Charset = "utf-8" in config.asp right under the copyright statement, where a default codepage/charset is defined for all pages.
Also, inc_header and inc_header_short has html content type variable defined, which by default will fetch the variable value from the one defined in config.asp.
There are some differences in handling enabling a base version to support unicode and a localized based version to handle unicode support.
Anyway, some of the basic considerations in enabling unicode support for various Snitz Forum versions are discused in the documentation mentioned above, or Unicode Support for Snitz Forums 2000 Localization/Translation if these are any help for considering various approaches.
BTW,Ruithat's quite a credit given to me, but not really, I have to say. Still learning. |
Edited by - TSAloha on 13 January 2008 12:08:00 |
 |
|
Topic  |
|