[MPlayer-translations] r20940 - in trunk/DOCS/xml: html-common.xsl pl/Makefile pl/html-chunk.xsl pl/html-common.xsl pl/html-single.xsl ru/Makefile ru/html-chunk.xsl ru/html-common.xsl ru/html-single.xsl

[Diego Biurrun]

On Wed, Nov 15, 2006 at 02:39:25PM +0100, Torinthiel wrote:
> On Wed, Nov 15, 2006 at 12:49:04PM +0100, Diego Biurrun wrote:
> > 
> > On Wed, Nov 15, 2006 at 12:38:22PM +0100, Torinthiel wrote:
> > > On Wed, Nov 15, 2006 at 11:37:42AM +0100, diego wrote:
> > > > Output UTF-8 instead of legacy encodings by default.
> > > 
> > > I can't say I'm in favor of that change.
> > 
> > That objection is coming rather late ...
> 
> This one maybe. But not this one:
> 20061031081017.GA6264 at kraken.home.aster.pl (dated Tue, 31 Oct 2006 09:10:17
> in thread "Re: [MPlayer-translations] r20530 ...")
> 
> And as it's in reply to your mail and you've replied as well, you can't
> pretend to have missed it ;)

I didn't mean to just ignore your objection.  But this was two weeks ago
and we discussed the UTF-8 subject in the meantime.  All the other
objections and problems were solved.  That's why I asked explicitly for
the output encoding again.  Somehow I expected you to speak up again if
you still had issues...

> > > Utf-8 may be good, but still iso-8859-2 is more standard amongst
> > > Polish webpages. As I've already said in previous thread about utf-8.
> > 
> > That's beside the point.  The point is whether it causes users problems
> > or not, i.e. whether modern browsers have trouble coping with UTF-8.
> 
> Haven't found any, that's true. I still don't like it, but don't have
> any logical reasons to support my view[1].
> 
> But during testing I've found that IE 6 somehow complains that it has
> "restricted the file from showing active content that could access your
> computer". Even stranger, it only happens if I try to browse local copy,
> browsing mphq is ok. Any ideas?

The cron job to regenerate the docs did not yet run.  Plus, it will take
a while for the mirrors to sync, so make sure to test against www1.

> [1] Apart from the fact that I've objected it two weeks ago and I'm
> maintainer of this translation.

I really think it's the right thing to do in the long run.  You could of
course restore the Polish xsl files and override the encoding, but if it
works, which it seems to do, I believe we should stick to UTF-8 now.

Diego