Thanks Shaxs,

sometimes he gets confused with the cchooices of posting data as php or html or XOOPS code. In that case he just gives me a call and I go and make a couple of changes to the code he updated.

The XOOPS multilanguage hack made it a snap to have both the japanese and English content ready at the push of a button.

I did have to teach him the basics of html and how the multilanguage tags worked, but other than that, it only took a couple ofdays for him to learns what he needed to know.

Jose

Hi Bassman,

How you been?

I built a site for a local church, Munakata Bethel Christian Center. XOOPS is so easy, now the Pastor does all the content updates himself.

Jose

I check into wjue's site once in a while and he announced last year that he was in private beta testing but no more than that.

I read a bit into how BSD licenses work and I don't see how that would stop development. Otherwise, I really don't know what's going on with the project.

I'll go check out xsurvey now tho'

Jose

exactly,

It was the folder permissions on the download of the schinese lang files for agendax and xf-sections.

Jose

I figured out most of the problem,

I didn't check the permissions of all the folders after I downloaded the different language packs for each module I was planning to install.

I found that some of them had the wrong permissions and after I fixed that, All was fine, no need even for a module update.

Jose

Just about anything you can find that is about wf-sections can apply to xf-sections. People here know wf-sections alot, and xf-sections is basically just a feature enriched clone of it.

Jose

some more info:

when I looked at the source code for the rendered page for this site, when I change the language interface the smarty variables in the theme that return language encoding ($xoops_langcode

Hi everybody,

it's been awhile.

I've been contracted to put together a new website for a japanese client that wants to make a web presence in mainland china.

I've been using the multilanguage hack successfully for several months on a couple of different sites now and thought that it would be no challenge to make it work for a chinese site as long as I had all the language files installed properly.

But it turns out that when I install all the language files for tchinese, schinese, japanese english and spanish, all of them work flawlessly with multilanguage except for the schinese. In every instance, whether working with official modules or third party stuff (like xf-sections), schinese always reverts to the english entries for the user interface, but content encoded to show up in schinese (I use the tags [sc][/sc]) always comes out fine. I've even tried copying bits of the GB2312 encoded text from the schinese language files and pasting them in between [sc][/sc] tags and they come up ok too. On the other hand I'm not sure if they come up REALLY properly or not, as I can read japanese but can't really read chinese.

More strange behaviour is that when schinese has been selected as the language in the pop-up menu, the administration interface shows the raw php entries for language such as "_AM_POSTNEWARTICLE". It does this in some parts of the user interface as well, such as the notifications boxes.

It's as if the system simply can't see the language files even tho' I can see them there, and having looked at their contents I can see that they're ok.

Like I said the tchinese and japanese interface comes up perfectly so I'm pretty sure that it's not a multibyte problem, after all selecting schinese simply makes the interface jump to English (with those missing bits that show only the php entries).

Anyone know what might be going on?

Jose

This behaviour was vexing me for the longest time too, unti I figured out that the big story block code is set to display somethng only if it has been added to the database in the last 24 hours.

After that time limit is up then no matter how often it is read, it won't be there anymore. I've been meaning to hack this behaviour for awhile but I haven't gotten around to starting to yet. If you need this solved in A BIG WAY, I'll be willing to look into it for you.

On the other hand if Catz is reading this maybe you should ask him... he's the man.

Jose

Your Apache installation isn't configured to accept "index.php" as a directory default page.

Look in your Apache documentation about changing the directory index in the config file.

Jose