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

Re: New security/audit pages not translatable

On Thu Nov 29, 2007 at 13:09:34 +0100, Frans Pop wrote:

> (Keeping you CC'ed as I'm not sure if you're subscribed...)

  I am.

> You don't seem to be replying to the translation issue for the main audit 
> advisories page. 

  I thought I was, or at least my failure to answer wasn't deliberate.
 I said that the files were there in CVS, and now you're suggesting they
 are not.

> For that translations of the wml file _are_ available and 
> have been updated, but the builds fail for some reason.

  The build failure is a seperate issue to translations, so I'll ignore it.
 (Mostly on the grounds that I'm not terribly familiar with WML.)

> >     ./audit/2003/index.wml
> >     ./audit/2004/index.wml
> >     ./audit/2005/index.wml
> >     ./audit/2006/index.wml
> >     ...
> >
> >    are the very source which should be translated!
> Yes. Basically, because these files are not in CVS, there is nothing that 
> can be translated and as they are generated automatically, there is not 
> much point either in having them in CVS or translating them.

  These index.wml files *are* in CVS.  Or at least appear to be so to me:

skx@klecker:~/webwml/english/security/audit/2007$ cvs log index.wml 
RCS file: /cvs/webwml/webwml/english/security/audit/2007/index.wml,v
Working file: index.wml
head: 1.3
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 3;     selected revisions: 3
revision 1.3
date: 2007-11-02 21:54:36 +0000;  author: skx;  state: Exp;  lines: +1 -1
  Updated link to the advisories page, so it is correct.

  I guess you're suggesting that the *output* files are not in CVS?
 But they shouldn't be.  THey shouldn't have anything to be translated
 in them (though right now there are about three small strings that
 are there).

> The current build process is not optimal anyway. We now have auto-generated 
> WML files that, because they are present on www-master will show up as "to 
> be translated" on translation status pages [1]. This is contradictory: 
> pages should either be auto-generated, or in CVS and translatable.

  This process came about via the following thread:


  [Where I asked for advice because IW anted to generate pages
 from data files.  The current solution is a result of that thread
 and help from Rhonda.]

  If you wish to change the way this works, to make it more translatable
 you're very welcome to do so.

> IMO you should either directly generate HTML (using gettext for translatable 
> parts), or have stub WML pages with the fixed content (title and such) and 
> include the variable content in that.

  The latter is what I thought we were doing.  The stub pages are 200N/index.wml, which include the variable content inside it.

> There are probably different solutions possible for this, but I'm not 
> familiar enough with writing WML from scratch to suggest which is best.

  Me either.

  (I half suspect we're talking past each other here, and we're neither
 of us familiar enough with WML to make a really useful change, but if
 I'm being confusing, unclear, or just not helpful please feel free to
 tell me so.  It isn't deliberate.)


Reply to: