J
|
Jane 3/14/2007 |
Vasilis,
and replace it with this one: Charset = "utf-8"
and replace it with this one: session.codepage=65001 |
S
|
srlsir author 3/14/2007 |
Jane, |
J
|
Jane 3/14/2007 |
What version of ASPRunnerPro do you use? |
S
|
srlsir author 3/14/2007 |
ASP RUNNER 4.0 (BUILD 97) |
J
|
Jane 3/14/2007 |
You need to edit include/commonfunctions.asp file in this case. |
S
|
srlsir author 3/14/2007 |
My problem doesn't solve. When I open the edit page, I can view text ok (in all language). But when I'm trying to write some new text and click the save button, then I can't see either Greek or Turkish text correctly. The only text that is correct is the English text. |
![]() |
Sergey Kornilov admin 3/14/2007 |
I would suggest to upgrade to ASPRunnerPro 4.1, rebuild the project and apply Jane's fix. |
S
|
srlsir author 3/15/2007 |
Dear Jane or Sergey, |
A
|
agmoraojr 3/17/2007 |
hello there to everybody, |
M
|
mazyad 3/21/2007 |
I also have the same problem with Arabic Characters presentation. Arabic text retrieved from the database is presented well, however, the text generated by Smarty is Scambled characters. I hope this is investigated because in the past (Version 4.0) we define the code page as follow <%@Language=Vbscript Codepage=1256%> and every thing is smooth thereafter. In version 4.1 build 225 this is not working and changing the charset/session.codepage/Session.LCID .. etc in every possible way did not fix the problem. |
M
|
mazyad 4/3/2007 |
First I'm grateful for the level of support we continue to obtain. The Smarty Attachement I received from support@xlinesoft.com solved the Arabic language problem as long as I use Arabic only (not mix with english/hebrew for multilingual site). I indeed appreciate the propmt replay and accurate solution for now. |