G2 & VB3.5.4 Integrated - language problems
|
fudge55
Joined: 2006-07-31
Posts: 6 |
Posted: Mon, 2006-07-31 18:41
|
|||||
|
Ok, i've integrated the G2 and VB, everything works fine, except the international characters. If i call the g2 without the integration, international chars are working well. But if i use it through the embedding script, they fail. When i view the source i can see this: 1. Normal version Galéria 2. Embedded version GalĂŠria It seems that the core module outputs something else when i use the embedded version. I don't know why... Any solutions? Attaching 2 images to see the difference... Anyone can help?
|
||||||
Posts: 6818
Hello,
Gallery2 translation are UTF-8.
If your environment is not UTF-8 then the translations fail.
Jens
--
Last Gallery v1 Developer and v1 translation manager.
Posts: 6
Well, i tried to change the header in VB to UTF-8 and there were no changes.
What do you mean by 'enviroment'?
The strange thing that i can see the difference in the SOURCE, so G2 outputs the strings in different format when it's embedded.
Posts: 6818
This VB is your Environment.
Can you provide an URL to your embedded G2 ?
Jens
--
Last Gallery v1 Developer and v1 translation manager.
Posts: 6
Sure, it's
http://www.salsaforum.hu/salsa/gallery2.php
and
http://www.salsaforum.hu/salsa/gallery2/ is the regular version.
View the source and see the differences.
(you can use L: Tim P: g2 if you don't see the localized version)
Thanks
Posts: 6818
i see: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2" />
nothing about utf-8
Jens
--
Last Gallery v1 Developer and v1 translation manager.
Posts: 6
Ok, see it now, it's UTF-8, and the chars are still scrumbled...
Posts: 6
Well, i just see if i change this line in GalleryTranslator.class
bind_textdomain_codeset($domain, 'UTF-8');
to
bind_textdomain_codeset($domain, 'iso-8859-2');
then the fixed strings look good, and only ones that the user inputted has problems...
(because these are not going through the gallerytranslator.class i guess)
So i think this is not going to be the right way...except it you can tell me how to send every string through the bind_textdomain_codeset function...
Posts: 6
As i go deeper in the source code, it seems that the embedded version doesn't actually convert the special characters back to utf-8...
It's not an enviroment issue i think, because there's no difference now in my enviroment...
You can see this if you see the SOURCE of the two versions...
Posts: 6818
its still charset=iso-8859-2
Jens
--
Last Gallery v1 Developer and v1 translation manager.