Kalle Olavi Niemitalo <[EMAIL PROTECTED]> wrote Sat, Mar 01, 2008: > I propose we change most newlines to spaces in the option.desc strings: > > [snip example] > > Of course, newlines that delimit paragraphs or list items would > be left in.
I know that witekfl tried to push for this change and even did some work on this. > This change would require rewriting the translations in po/ > though, so I don't know whether it is appropriate for 0.12.GIT. Did you investigate whether we can simply replace the newlines with spaces in the po files and things will work? > Currently, 0.12.GIT and 0.11.4rc0.GIT are very compatible with > respect to po files, and this in principle allows 0.11.* to > benefit from po/perl/msgaccel-check in 0.12.GIT. I am not expecting a lot of new 0.11.* releases, so I don't think the po compatibility argument should hold back this thing from entering 0.12. The bigger question to me is what will happen with 0.12 and beyond? As you and other developers have noticed I am not much active anymore, and when I am, it mostly amounts to a few documentation and website updates. Lacking a real maintainer, does it make sense to have anything other than a "current" branch? In my opinion and in my perhaps more current role as merely a release manager, it seems like a simpler solution. We can have some monthly or quarterly "elinks-%Y.%m" release, possibly with a "-quirky" or "-dev" tag attached to warn. This way upgrade pain is amortized better, users are happy, and developers full of hope! I think this development model fits better the slower development pace ELinks is in, besides I have always felt that the development branch has been pretty stable. -- Jonas Fonseca _______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
