Search options

Thanks, got it working (albeit a little slow). The reason was exactly this - exit was called before my footer was wrapping up the node tree.

Sure it is not. However, instead of declaring that 'punBB is not multibyte-safe' you can make a code fork (not a big one, I mind you).

What I thouhgt is that, essentially, you write in the readme - 'you need it to work multibyte - presto, substitute file X with file Y and you are all set, you need extension Z and extension K for this to work'). People who gonna need this (for example Asian PHP installs) usually have the extension builtin and usually they are familiar with the issue.

PostgreSQL for instance (as well as MySQL of recent versions) both have calls to determine the current client charset and change it. Th only problem I encountered as of yet is with this indexing feature (which is apparently related to the regexps, and it seems that mbstring is not overloading the PCRE extension).

I will send you the code - just make a diff with the one of yours (mine will surely work slowly because I never could grasp regexps).

BTW. a good candidate for a UTF-8 solution is this very forum - just look at these fancy ????? in my post in the russian section :-)

I tried it with all good-mannered browsers I have (Firefox and Safari). Got this practice of developing for good user agents before anything even gets to IE.

There may (!) be a problem with the fact that the error screen I get is sent as ISO charset, but the POST data should still be accurate.

I have to find out what is going on with the words before they get to the database (instead of your regex I tried to substitute a generic database quoting routine from ADODB, same result, so I guess the characters get mangled even before they get to be quoted for the database), because everything else just works fine - postin g(if your post contains one long word), userlists etc.

How can I trace variables that go through this script, I tried putting print_r there but your script evidently suppresses all output.

Probably this is just a case of some array_ function of PHP being not multibyte-safe.

If you can afford it you can use PostgreSQL.

Then you can map your users table into a view looking like the punbb_users table. Then you can define rules for INSERT and UPDATE on punbb_users and your systems will be transparently integrated. An hour of careful work is needed though.

For encryption look for function punbb_hash in punBB sources, there you can change the encryption mechanism used for passwords and cookies to something of your taste, even substitute a call to your own hashing routine.

If you want to stay with MySQL and your table you are set for some serious hacking on the punBB source (I am not sure that MySQL supports rules and triggers, although it definitely supports views in the latest version).