On Wed, 29 Mar 100, T.E.Dickey wrote:
> > Btw. the various *.po files now available are all based on a very
> > early lynx.pot (from one of the first 2.8.3dev.Ns, more or less
> > the same as 2.8.2, it seems), although they claim to be 2.8.3.
>
> I've noticed that...
>
> > They'll be out of date when 2.8.3 comes out. Should we encourage
> > translators to update their translations now? How?
>
> It would be nice if they could update when we start pre-release, since
> (it would be nice to assume the code will be fairly stable). I see only
> one bug report against dev.23 (the htmlized cfg file install).
There is one more bug wrt prettysrc and charset handling (not checked
dev23, but it's present in dev16 and seems no fixes for it were posted). If
charset of page was specified in the HTTP header, and that charset is not assumed
document charset, then switching to psrc and back will rerender document with
assumed charset rather than the one specified by http header. This loss of
charset information makes documents in russian completely unreadable. Sorry
for reporting this so late - I hoped to fix this problem myself (but if anyone
knows solution right now - please do this). As I understand - the something in
LYMainLoop.c should be tweaked (and I predict the patch will change only one
line in LYMainLoop.c).
Seems the following could be considered a bug: lynx treats SIGWINCH only if
run in xterm or under X Window (as I understand) - but shouldn't it do this
in console too (this could happen if user invoked SVGATextMode in linux to
change screen size)?
> > Klaus
>
> --
> Thomas E. Dickey
> [EMAIL PROTECTED]
> http://www.clark.net/pub/dickey
>
Best regards,
-Vlad
