Hi there,

We are in the process of translating XOOPS to Greek language (will be finished soon). At the moment we have a huge problem with document encoding. For Greek language we use the "Windows-1253" encoding. All the mails that are sent from the site are not compliant with that encoding and are not readable. Also the file /backend.php produces a format where the Greek fonts are not readable.

Is there a fix? Can someone help? This is urgent...

Thank you very much, that was quick... :)

After editing a user profile three dots are appended at the Signature and Extra Info fields. If the same profile gets edited again, three more dots get appended, and so on...

Help anyone?

Well, i decided to come back to you because i saw you have a lot of questions about security and risks for htmlarea.

Follow my thoughts... You just need a decent editor for your site visitors and your editors. You can't expect your site visitors and even your editors to be able to write html - this is where every nuke like portal fails and it ends up to be webmaster-centric. I decided to go with XOOPS and it's been months now since the release of XOOPS 2.0.3 I'm still trying to find free time and complete the integration of htmlarea.

Security risks? Not at all. I just want to replace the (difficult to use by novices) bbcode editor. So, i only enabled bold, italics, underlines, left-center-right aligns and two or three more things. It's even more secure because noone can write even a single html command. The editor is responsible to convert the text to html. THAT simple...

Soon i will be ready to give you a preview of the htmlareea integration. Believe me... It's so beautiful and works so nice that all developers will start thinking the integration of an advanced editor inside the core. I really hope so because i already know that it is already impossible to upgrade my XOOPS engine to a newer version. The changes are so many that it's almost impossible...

Well... i think i must comment here because i spent a lot of my time on this project and we are at a good point at the moment. We managed to integrate htmlarea for the whole site but there are things to do now that completely recreate Xoops. Let's see some problems:

1. Smilies don't work as expected so you have to integrate them in the htmlarea code (by using custom buttons) and remove any smilie references from Xoops

2. Integrated image manager of XOOPS is not working anymore (not an actual image manager - more of an imae handler for a small number of images. No search option)

3. All bbcode should be removed because it is now replaced with htmlarea

4. htmlarea appears in places tou don't want to (for example the at user's profile, at the textarea to add a signature) and you need to restrict html from those pages. Maybe a custom textarea there will do the job...

5. At some points, users and editors may select to "Disable HTML" which is womething you don't want to. You have to edit each page and remove thos references

6. you propably don't need any bbcode references too, so the pages should be edited again to remove those references.

....

There are a lot more small things that all of them take up your time for such a project. Unfortunately i cannot post any code, because as you can propably understand the changes are at the whole XOOPS site and not on single files...

Maybe at the end of the projects, we could try and release some XOOPS htmlarea patch that someone could run and promote XOOPS to WUSIWYG editing...

I wishyou good luck...

P.S. has anyone managed to create a searchable image manager that is able to work with htmlarea or could easily be adopted? Thanks...

Quote:

How is your Greek translation going? Are you at any good point to share it with us?

Thanks MithikoS...