This hack will work with news, forum, wf-sections, tinycontent or any module that uses the textsanitizer.
After searching the boards and posting a couple questions that never were answered, I had a go at this myself and well…necessity is the mother of invention….I discovered the module.textsanitizer.php file and messed with it till I got it to work. I am not a coder, so I am sure that someone can improve on this. (More on that later)
First things first:
This hack assumes that you are using the multi-lingual hack that can be downloaded here from ModsCentral.
To install it on Xoops2.x, follow the instructions I posted here.
That will get your XOOPS to be multilingual.

Now to make your content multilingual:
1. Open the module.textsanitizer.php file in the class folder. Around line 145 is the function “&xoopsCodeDecode” After the line
Quote:
and before the line
Quote:
Place this code:
Quote:
Of course you will change the language ('english','japanese') to reflect the languages that you are targeting. The name in the brackets has to match the name of your language pack that you downloaded (or created). You could add more if you are targeting more than 2 languages.

To use this:
When you add your article just enclose the section you want shown in a particular language in brackets with that language name. This is very similar to adding a url or code to an article. For example: Quote:

If you are just targeting European languages, you may not have to worry about this, but if you are targeting multi-byte languages like Japanese you may have to manually change the character encoding of your English global.php file to match your japanese one.

That’s it! Basically very simple – If you are having problems with the layout, you probably are putting spaces between the codes.
I hope this helps!
Chad

Excellent hack! Great work!

Herko

Chado,

that looks really interesting, thanks for sharing it. Do you have a site where we can see this? i would like to see it working...

Thanks

I don't know if it's Chado website but this site :
http://peekaboo.s8.xrea.com:8080/
is using it, you can switch between english and japanese by clicking on the flags.

WismeriL

Quote:
I forgot to mention this, but while working on this hack, I tried to make it in such a way that it would automatically adapt to any language without having to go in and change the textsantizer code every time for each language - but I wasn't able to do it. So someone who knows php much better might be able to do it and make this hack something that could be used as is for anyone.....

So, instead of looking for each language (i.e. [english] or [japanese]), would it be possible to do something similar to the font or color code ([ font = Impact]) and have just one code that traps for different language - say something like [lang = english] and then have textsanitizer look at the language and if it is the current language then show the text, else don't show it. Does this make sense??

If someone could do this, it might be a much more useful hack for everyone.

Thanks,
Chad

Chad:

When I include the hack in module.textsanitizer.php, the admin side gives me this error message:

"Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING, expecting ')' in /home/mesadepr/public_html/class/module.textsanitizer.php on line 286"

Obviously, as soon as I remove the hack everything works as usual.

Any thoughts on what is causing this?

PS: I noticed also that on line 149 there's this (I've added a space to separate the word "code" from the bracket):

$patterns[] = "/\[ code](.*)\[\/ code\]/esU";

and not this:

$patterns[] = "/[ code](.*)[/ code]/esU";

Perhaps you've used a different version of the file...

Quote:

I have this problem before... When posting on the forums at xoops.org (or any XOOPS site), some characters in a [ code ] block are changed/removed/show up differently than entered. Generally it affects backslashes and maybe quotes, especially a problem for regexps. i.e. So what you see above is probably not what Chado actually has in the file...

Thanks, it works perfectly on that site AFAIK. Seems useful for a future project I want to do, still I dont fully get how it works on the admin side (guess you add text in both languages) but I will look at it more once I'm using it...

So, perhaps now the logical step would be to ask Chad if he's willing to share the code in a different format, for example a zip file sent by mail...

Chad?

In case you want this in a hurry...

In your above post, where you pointed out the difference between the line in your file and line in the post, you can basically see what changes you need:

i.e. add a backslash before '[', ']' and '/' in the regular expressions.