Re: [Phpwiki-talk] [dutch] translation update

[Jeff D. <da...@da...>]

>Well, I would like a new stable version instead. :) Can't we just
>feature freeze soon or are there many halfimplemented things in the
>main branch that need improvements?

The answer is "b) there are many halfimplemented things".  Mostly the
new database backend (which will allow multiple archived versions
of each page, and hopefully tie in to the quest for user authentication
abilities.)  I'm supposed to be working on that.  I'll see if I can =

produce something soon.  (Probably a couple of weeks.)


That said, the "alpha" branch does seem to be becoming popular.
Even if more big changes are anticipated, perhaps it's time for
a 1.3.1 release?  (Again with the understanding that those who
want real stability should stick with the 1.2.x branch.)


And: is it time for 1.2.1?  There have been a bunch of bug fixes since 1.=
2.
OTOH, things maybe worth waiting for (before 1.2.1) (?):
 * Marco has promised a few typo fixes for his Italian translations.
 * Should we fix the case-(in)sensitivity in page name bug(s) in the
   stable branch, or just leave it?  (SF bug # 233898).



>If you are on a PHP_SAFE_MODE system, do PhpWiki work like it's
>supposed to? I guess you can't mess much with environment variables at
>all.

Yes, now that you (and Jan) mention it, that is a problem.
Oh well.  Maybe things are best left as they (now are).
(With perhaps a little cleanup regarding LC_CTIME.)

>Yes. Have a test script that you can run to check if everything works
>ok.

Yes.  Adding some general regression and/or unit tests might be a good th=
ing
to think about (for everything, not just the setlocale() issues).  A lot
of work though....

Jeff