[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: website translation infrastructure
From: |
Graham Percival |
Subject: |
Re: website translation infrastructure |
Date: |
Wed, 31 Mar 2010 19:58:16 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Wed, Mar 31, 2010 at 08:48:45PM +0200, John Mandereau wrote:
> Il giorno mer, 31/03/2010 alle 19.31 +0100, Graham Percival ha scritto:
> > On Wed, Mar 31, 2010 at 02:19:32PM +0200, John Mandereau wrote:
> > > You mean scripts/build. Yay, yet another place for translating
> > > strings :-P
> >
> > Not my problem.
>
> You mean you don't care about maintainability for these scripts,
Correct.
> which may survive a build system switch?
I doubt that. Before (or during) a build system switch, pretty
much everything I did about the website in the past few months
should be scrapped.
http://code.google.com/p/lilypond/issues/detail?id=1004
> > I have no desires for or against that. However, if you more stuff
> > into python/ then you'll need to update website.make to declare
> > PYTHONHOME.
>
> I was thinking of PYTHONPATH, I'll choose most appropriate.
Err, yeah, whatever. I don't know what I'm talking about.
> > Don't the partly-translated texinfo files contain English at the
> > beginning?
>
> No, I trim out every bit of copied English docs I notice in the
> translations (I don't do it systematically, though), but for offline
> target the output files that are "empty" (i.e. marked as "UNTRANSLATED")
> in translations are replaced by copies of the output files in English.
> This functionality should be copied from www_post:postprocess_html to
> web_post if not already done.
Umm, yeah. You could either do that, or just stop trimming the
English text from the website translations. I think the latter is
less work.
> > If so, it's no problem: community.de.html (for
> > example) would contain only English text, but that's not a
> > problem. No, the extra bandwidth in uploading idential
> > community.en.html and community.de.html is /not/ an issue.
>
> Agreed (modulo the file copying problem), so unless I discover problems
> with this I will conserve the disabling of the auto-language selection
> for pages other than the home page (which the current system amounts
> to). It is an issue for the manuals, though.
The manuals are not created by website.make or website_post.py, so
nothing has changed there.
Cheers,
- Graham
- Re: website translation infrastructure, (continued)
Re: website translation infrastructure, John Mandereau, 2010/03/31
- Re: website translation infrastructure, Graham Percival, 2010/03/31
- Re: website translation infrastructure, John Mandereau, 2010/03/31
- Re: website translation infrastructure, Graham Percival, 2010/03/31
- Re: website translation infrastructure, John Mandereau, 2010/03/31
- Re: website translation infrastructure, Graham Percival, 2010/03/31
- Re: website translation infrastructure, John Mandereau, 2010/03/31
- Re: website translation infrastructure,
Graham Percival <=
website translation infrastructure, Graham Percival, 2010/03/30