Posted on: 05/23/02 07:52pm
By: Euan
...but almost there. Just installed Geeklog at g-comm.net[*1] .
I have to make this a multi-lingual site - main languages will be Japanese and English, secondary will be Korean and Chinese plus other European languages. The Classic and ClearBlue skins work with Japanese, but none of the others I have do so at the moment - can anyone give me some pointers on what files to change to enable this? I already tried fiddling with the charset= in the header file, but no luck.
Thanks for any help!
Euan
Posted on: 05/24/02 01:14am
By: Dirk
In Geeklog 1.3.5, there is still a lot of hard-coded English text. Some of the themes have the "Get Published" etc. texts hard-coded, too. Compare the header.thtml
files with the themes where it works and you will see the usage of variables (in curly brackets) for those texts.
The next version of Geeklog will resolve these issues (I hope). I have moved all the hard-coded texts I could find within the Geeklog code to the language files. See also this story[*2] I submitted some time ago.
bye, Dirk
P.S. If you are creating new translations, be sure to subscribe to our new geeklog-translations[*3] mailing list! All the important announcements regarding translations and localisation of Geeklog are posted there.
Posted on: 05/24/02 01:48am
By: Euan
Posted on: 05/24/02 02:31am
By: Euan
Posted on: 05/24/02 06:39am
By: Dirk
I wasn't talking about Geeklog 2, but simply about the next Geeklog release which will go by the version number 1.3.6. It should come out in the not-too-distant future ...
As for language packs: There already is a fairly (but not quite) up-to-date Japanese language file (and someone is still working on it). No Korean or Chinese, though.
Check out CVS[*5] for the available languages.
bye, Dirk
Posted on: 05/24/02 10:48pm
By: Euan
Posted on: 05/25/02 01:35am
By: Dirk
You are running Geeklog 1.3.5, right? That version should work (and does for me). Just make sure that you send the correct character encoding with it.
Or you might want to try the version from CVS[*6] which has been updated a bit ...
bye, Dirk
Posted on: 05/25/02 08:44am
By: Euan
Posted on: 05/25/02 11:36am
By: Dirk
Oh, I see. For some reason, the site was still using an older version that was missing some commas (hence the parse errors). I've uploaded the version from CVS now and it seems to work (well, at least it doesn't give any errors - I can't read Kanji ...).
bye, Dirk
Posted on: 05/26/02 06:22am
By: Euan
Posted on: 07/22/02 04:08pm
By: Anonymous (Anonymous)