webgen users - May 2009 - Keeping track of outdated translations

As the new FSFE Fellowship pages are continuously updated with more 
information, often with small changes like adding a new mailing list, we were 
wondering what the best way would be to keep track of the outdated 
translations.

Would this be a sensible feature for webgen itself? Are there extensions that 
can do this? Is there some ruby magic that could help?

all the best,
/Stian

> As the new FSFE Fellowship pages are continuously updated with more 
> information, often with small changes like adding a new mailing list,
> we were wondering what the best way would be to keep track of the
> outdated translations.
> 
> Would this be a sensible feature for webgen itself? Are there
> extensions that can do this? Is there some ruby magic that could help?
I can''t think of a way that webgen could handle this itself. You
would first need to define what ''outdated'' means.

However, it should be rather easy to do this with a version control
system like git because you can track changes to the main file (e.g.
the english page) and then issue update requests to the maintainers of
the translated pages. It will get more complicated if original changes
can be introduced in many pages (e.g. in the German and the English
page).

-- Thomas

From Thomas Leitner, 2009-05-04:
> > As the new FSFE Fellowship pages are continuously updated with more
> > information, often with small changes like adding a new mailing list,
> > we were wondering what the best way would be to keep track of the
> > outdated translations.
> >
> > Would this be a sensible feature for webgen itself? Are there
> > extensions that can do this? Is there some ruby magic that could help?
>
> I can''t think of a way that webgen could handle this itself. You
> would first need to define what ''outdated'' means.
>
> However, it should be rather easy to do this with a version control
> system like git because you can track changes to the main file (e.g.
> the english page) and then issue update requests to the maintainers of
> the translated pages. It will get more complicated if original changes
> can be introduced in many pages (e.g. in the German and the English
> page).
I guessed that would be the way to go. Thanks for the reply.

all the best,
/Stian