Geeklog Forums

Hi,

I installed v1.4.1 by encoding utf-8,
but I can not select any utf-8 language file in 'My Account'.
/usersettings.php?mode=edit

I uploaded only utf-8 language files, not euc language files.

---

Geeklog Japan https://www.geeklog.jp

What exactly is the problem, i.e. what isn't working?

Geeklog 1.4.1 is hiding the "UTF-8" from the user when the site is using UTF-8 as the default character set. So if you only uploaded the UTF-8 files, the languages you see in My Account are all UTF-8.

bye, Dirk

Thank you, Dirk.
I changed default_charset iso-8859-1 to UTF-8 in config.php,
it works good.

---

Geeklog Japan https://www.geeklog.jp

this is really frustrating!

i had geeklog 1.4, then upgraded to 1.41.

previously, everything was grand.

now i have my settings like this: (character for character)

$_CONF['language'] = 'english_utf-8';
$_CONF['default_charset'] = 'utf-8'; <-in my 1.4 config this said 'iso-8859-1'
$_CONF['locale'] = 'en_GB';

but the only way i can get my page to display right is by going into the non-utf-8 language file and forcing the charset to 'utf-8'

why isnt it automatically doing it?? am i misspelling something??

If you want to run the site on UTF-8, you should remove all non-UTF-8 language files.

bye, Dirk

oh. really?

did i miss a step in the instructions or something? i swear i thought i followed it word for word.

anyway. ok! thanks. didnt realize i had to remove those other ones.

btw. unbelievable speed on your reply. you give better support than most corporations....

to follow up. what i thought would work, did not in fact work.

i deleted all those other files. it didnt fix anything.

i changed

$_CONF['language'] = 'english_utf-8';
$_CONF['default_charset'] = 'utf-8';

to

$_CONF['language'] = 'english_utf-8';
$_CONF['default_charset'] = 'iso-8859-1';

then everything worked ok, but all of the languages disappeared in the drop down menu.

any idea? should i post my entire config?

it seems there is a bug?

i renamed two language files

english_utf-8
japanese_utf-8

to

english
japanese

and those two showed in the menu, and they work fine upon selecting them.

i guess the fix is to either rename all of the UTF-8 language files or to take the originals and rewrite it to say $LANG_CHARSET = 'utf-8';

i wonder if i am the only one with this problem???

ugh. but now the plugins show "??????????" upon selecting japanese :banghead:

ill have to just screw around and see what i can do >.<

Don't change the names of the language files - there are reasons why they have that name ...

You said you were upgrading to 1.4.1 and switching to UTF-8 at the same time. In that case, some of your users would still have a language cookie pointing to the old (non-UTF-8) language files.

That's why I advised you to remove the non-UTF-8 language files. Geeklog will fall back to the default language file (the one you set in config.php) when it can't find a language file. So this way, all your users will be forced to switch to UTF-8 now.

Don't try to fix something that isn't broken :wink:

bye, Dirk

i noticed on another thread, someone had to convert thier actual database.

i looked in my database using PHPadmin, and noticed that there are many things "collated" as latin1_general_ci

would that be giving me my troubles?

i found that if you have used UTF8 when UTF8 was not fully supported by MYSQL, then it will simply encode it in latin1, which is causing all of our problems.

i think i found that you can convert it, using MYSQL using this function. but i know nothing about it. perhaps you devs can pick up on it?

source: page 17 of
http://72.14.253.104/search?q=cache:fNygVLj71RUJ:www.oreilly.de/catalog/mysqlckbk2/chapter/ch05.pdf+COLLATION+%27latin1_general_ci%27+is+not+valid+for+CHARACTER+SET+%27utf8%27&hl=en&ct=clnk&cd=13&gl=us&client=firefox-a


The new collation must be legal for the character set of the string. For example, you
can use the
utf8_general_ci
collation with
utf8
strings, but not with
latin1
strings:
mysql> SELECT _latin1 'abc' COLLATE utf8_bin;
ERROR 1253 (42000): COLLATION 'utf8_bin' is not valid for
CHARACTER SET 'latin1'
To convert both the character set and collation of a string, use
CONVERT(  )
to change the
character set, and apply the
COLLATE
operator to the result:
mysql> SET @s1 = 'my string';
mysql> SET @s2 = CONVERT(@s1 USING utf8) COLLATE utf8_spanish_ci;
mysql> SELECT CHARSET(@s1), COLLATION(@s1), CHARSET(@s2), COLLATION(@s2);
+--------------+-------------------+--------------+-----------------+
| CHARSET(@s1) | COLLATION(@s1) | CHARSET(@s2) | COLLATION(@s2) |
+--------------+-------------------+--------------+-----------------+
| latin1 | latin1_swedish_ci | utf8 | utf8_spanish_ci |
+--------------+-------------------+--------------+-----------------+

ok, i couldn't fix it.

no matter how hard i try to convert my previous database from the latin1-encoded-utf8 to the true utf-8 encoded format, it just wont do it.

i have my settings correct, and the site works. new posts and such work fine on the old db. a new install also works fine. but i cant get the old data to convert.

i figure ill just live with it.

good luck to all