Re: slrn 1.0 [2007-08-25] ?

Peter J Ross <[email protected]>
Newsgroups gmane.network.slrn.user
Message-ID <[email protected]>
On Monday 02 July 2007 19:48, Martin Trautmann wrote:
> On 2. Jul 2007, at 0:37, Sven Guckes wrote:
> > the froscon will take  place on 2007-08-25 -
> > four years after the release of slrn 0.9.8.0.
> > do you think we can get slrn 1.0 ready for it?
> > and where exactly is that roadmap hiding, anyway?
>
> This would be great.
>
> Have there been sufficient tests how it does compile for the current
> release? (e.g. UTF-8 support on linux and MacOSX?)

I've found no problems with UTF-8 on Linux, but support for undeclared or 
incorrectly declared legacy character sets is poor. Any thread in which OE, 
Thunderbird, Agent and Google users participate is a mess on the screen - 
quite apart from the nonsense such people write ;-)

There are also problems with iconv, which are, likewise, the fault of other 
newsreaders using non-standard charset declarations.

There's a canlock issue as reported here by Robert Grimm and also discussed in 
NSR. There are probably other canlock issues, but they can probably be blamed 
on canlock. :-)

I'm hoping that Thomas Wiegner's patch will solve some of these  problems, but 
I haven't had time to try it yet.

The documentation needs some minor tweaks, and that's something I'm willing to 
volunteer to help with. And I can proof-read the website.

What other problems are there, if any? And which, if any, of these problems 
are release-critical?

Anyway, 1.0.0.0 doesn't have to be perfect; perfection will be achieved in 
1.0.1.15 or something!

-- 
PJR :-)

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.