Re: web translation oddities

[Graham Percival]

On Sun, Apr 04, 2010 at 05:20:08PM +0200, Jan Nieuwenhuizen wrote:
> 
> > It's "fine", but not "perfect" -- enable the "nl" translation,
> > then look at community->old news.  The HTML output contains a
> > bunch of @ref{Changes} and the like.
> 
> just like -- see below -- news.itexi, also community.itexi
> has no dutch translation.  These refs are also from the
> original english version -- same argument: should we mandate
> copies/ skeletons here?
> 
> if so, iwbn if make skeleton-update worked

I'm guessing that skeleton-update copies stuff around?  Like
/etc/skel/ ?

> > So I see three options:
> > 1)  ignore it.  Let the log have ~500 extra lines (which makes it
> > much harder to track down any real problems that might occur later
> > on), let the output have a literal @ref{...}, etc.
> 
> right, I've been doing this and it produces a working website.
> I think all/most real node errors are caucht anyway by a regular
> make all-doc

I guess so.  I'm still worried about burying the console in
(mostly) pointless warning messages, thereby obscuring the *real*
error messages.

This is especially bad when people start adding @manualFoo-nl
links in there.  Most translators aren't going to get that stuff
right, so being able to tell them "if you see any warnings in
`make website', then go back and fix the mistake in whatever you
last changed" would really help.

I mean, you'd like the nl page for Manuals->Learning to link to
the nl version of the Learning manual, right?  And display the nl
translation of "Learning" ?  etc?

> > 2)  insist that the Documentation/??/web/ contain all the files in
> > the English version.  We don't insist that they all be translated;
> > just that they have the copies there, and that they update the
> > @ref{}s to be internally consistent.
> 
> see iwbn above...also, won't this requirement cascade (because of refs)
> right down into *all* documentation?

No, because "make website" only build the website.  I don't know
how the main build system does this, but evidently it works.

... then again, given the amount of "node warnings" when doing
"make doc", maybe it _isn't_ working at the moment.

> > 3)  fix lilypond-texi2html.init.  Not me.
> 
> ...when it's in python maybe.

So we wait for John to rescue the translations?  *shrug* I won't
argue with that.

Cheers,
- Graham