Hi,
I have installed CPG 132 and choosen Brazilian Portuguese on the admin config. Everything is in portuguese now, but there is some kind of problem with the characters. Characters with accents like ã á are not being displayed correctly.
What sould be done to fix it?
Thanks
Actually I have one more problem now. I was trying to change the character encoding option to see if portuguese worked fine, but then the config was set back to English, and now for more that I try to change it, it looks like stuck on English. I change to Portuguese again, save it, it says that it was saved, but continues showing the option English selected. I tried changing to other languages and it's just not changing.
Why is that?
Thanks
Link, please.
One explanation: the brazilian portuguese language file in utf-8 encoding is broken (http://forum.coppermine-gallery.net/index.php?topic=4623.140#msg54582). I'll fix this within a week.
== Olivier
QuoteOne explanation: the brazilian portuguese language file in utf-8 encoding is broken. I'll fix this within a week.
But could it be so broken that now I can't change to any language?
Basically I first changed to brazilian portuguese, not sure if utf-8 or not, there are 2 options. The change was made but the characters were weird. So I tried chaning the character encode option. After doing that, was when it went back to english and now I can't change to any language AT ALL.
Will it require a new installation of the CPG to fix it?
Thanks
Clear your cookies, then you should be able to change language again.
I can't clear all my cookies, so I am looking for the specific one and can't find it. I am looking for anything cpg132, cpg, any text file modified yesterday, etc... and can't find it.
Should I change the cookie name on my config file?
Thanks
Here is the corrected version of the brazilian portuguese utf-8 language file.
Quote from: skuba on December 01, 2004, 07:48:24 PM
Should I change the cookie name on my config file?
That would do it.
For future the cookie will be one that looks like yourname@yoursite
Niiiiiiiice!
It works now. Thanks a lot!