Zum Inhalt springen

e-mail js popup error charset problem

Erstellt am 16. April 2007 · 5 Antworten · letzte Antwort am 18. April 2007

Tags: Frage, English

htp ·

Hi,

I'm not sure, that this is the place for this topic.

Because I'm from Bulgaria and I want to run typo3 in Bulgarian language ( cyrillic char letter ) I using UTF-8 encoding. So far, so good. The things that I enter in db ( like page titles etc ) are ok.

The problem is with this javascript error popup message ( from mail form plugin - validation ). In some way js mess with the form names, and when it pop up there are some not understanding letters.

Also, when I try to translate locallang.php for chc_forum extension, the problem is same - not understanding chars like javascript pop up error.

When I try to translate indexsearch extension ( locallang.xml ) the problem is different - this time only question marks ( ???? ).

I want to point, that I'm using utf- file encoding for files. I rename original file, create new empty file with UTF-8 encoding ( to be sure the problem is not utf ) and paste inside new file contents from renamed file. The problem remains.

I search in google for this, but I can't find solution or some comment. Because my typo3 is using utf-8 this problem is a quite strange ??

Any suggestions from you guys ?

Thanks, Georgi!

htp ·

Yes, I set this option. I also set to be sure utf-8 filesystem. If I didn't set
forceCharset = utf-8 when I can't put understanduble data for cyr letters.

The problem is when I messing up with php files, but not all php files.
Sometime result is question marks, sometime understanding letters.

I test and I test this and send to typo3 bugtracker, but still I don't have any answer.

I test with new installation and etc. I can't find a logic subject for this problem.

Is it possible inside of typo3 engine to have some additional encoding and engine can't equal values ?

Georgi.

just2b ·

Normally for the Backend it is enough to set forceCharset-Option.

For the FE you can also set config.metaCharset = utf-8 (config.renderCharset is set vith the forceCharset).

Concering the files: I think you have made everything in the correct way :/

sorry that I can't help more
georg

htp ·

Yes, I also set this option. I think over this problem from 3 days.

The last thing is to put typo3 on other system ( my work station is debian gnu linux )

but why some files are ok, and some are messed up ??

Very interesting problem. I will continue to think and search of this.

10x for the helo!

Georgi.

htp ·

There is solution all ready for localization problem in MAILFORM validation alert pop- up box.

This is the link for this:
http://bugs.typo3.org/view.php?id=3527

Solution (thanks to Kit from forum www.typo3.biz)

Patch for t3lib/jsfunc.validateform.js

function validateForm(theFormname,theFieldlist,goodMess,badMess,emailMess) {
var formObject = document[theFormname];
// patch start
theFieldlist = decodeURI(theFieldlist);
// end
if (!formObj............

Very, Very nice!!

Georgi!