lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: web translation oddities


From: Jan Nieuwenhuizen
Subject: Re: web translation oddities
Date: Sat, 03 Apr 2010 12:53:19 +0200

Op zaterdag 03-04-2010 om 11:15 uur [tijdzone +0100], schreef Graham
Percival:

> Umm, dude?  You can't spot these for yourself?

No.

> ** Unknown command address@hidden</code>' (left as is)
>    (four times)
> ** Unknown command address@hidden</code>' (left as is)
>    (four times again... hmm, maybe this one isn't a translation
> problem?  oh, and it goes 4 times yet again)

Not a nl-specific problem?

> *** Undefined node `Manuals' in @ref (in
> /home/janneke/vc/lelie-web/Documentation//web/community.itexi l.
> 419 in @divEnd)
> 
> *** Undefined node `Changes' in @ref (in
> /home/janneke/vc/lelie-web/Documentation//web/news.itexi l. 122)
> *** Undefined node `Old downloads' in @ref (in
> /home/janneke/vc/lelie-web/Documentation//web/news.itexi l. 194 in
> @newsEnd)
>    (these messages are repeated, other than the line numbers, 407
> times!)

Not a nl-specific problem?  We /do/ have nodes
called Changes and Manuals, but they're translated.

These english node names are referenced from  community.itexi and
news.itexi, which are not (yet) part of the dutch translation, which
should not be a problem; our automatic language selection takes
care of "translating" Manuals to "Handleidingen" when accessed
from the english community.itexi or news.itexi?

> Completely incorrect.  Francisco has been translating stuff.  I've
> been tweaking the translation infrastructure in response to his
> bug reports; it was only 3 days ago that I thought I was finished.

Okay...So it's been ready for 3 days and we didn't switch yet!

> I fixed another small bug last night.

Oh, I forgot the lilypond.org build, just found out about that
and fixing what I can.

> Colin Campbell is planning some suggestions for the Introduction
> chapter.

> I'm thinking about another Introduction vs. Community issue.

Both good, your call if this is RC for a switch or not...

> I've had credible reports that the website is broken in IE 7.0, or
> just with IE in compatibility mode, or IE without compatibility
> mode, or something.  Is that important?

    1 3294062 67.26% Netscape
    2 822303 16.79% Micro$oft Internet Exploder
   18 34266 0.70% Mozilla/4.0 (compatible; MSIE 8.0; 
   24 29011 0.59% Mozilla/4.0 (compatible; MSIE 8.0; 
   27 26795 0.55% Mozilla/4.0 (compatible; MSIE 8.0; 
   32 22014 0.45% Mozilla/4.0 (compatible; MSIE 8.0;
   44 17416 0.36% Mozilla/4.0 (compatible; MSIE 8.0;
...
   50 16318 0.33% Mozilla/4.0 (compatible; MSIE 7.0; 

so we'd be pissing off 1 in 300 people.

it would be nice to have a javascript on the front page saying
please upgrade to ie8 or firefox.

> Yes, there will come a time where we say "ok, good enough, let's
> go live".  Maybe even we'll just do it for 24 or 48 hours, get
> feedback, then put the old website back up while we fix other
> issues.  But that time is not now.

Okay.

Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyOfSource.com | AvatarĀ®  http://AvatarAcademy.nl  






reply via email to

[Prev in Thread] Current Thread [Next in Thread]