Request to withdraw outdated tqsg translated version

Karsten Wade kwade at
Fri Nov 30 18:10:10 UTC 2007

On Fri, 2007-11-30 at 07:54 -0500, Paul W. Frields wrote:

> I wonder if it might make sense to have some sort of notice on the index
> page stating what the current released version is, to avoid confusion.
> However, that wouldn't be as much help if someone links directly to a
> locale-specific document.  In other words, we could put a notice here:
> But if someone linked to:
> ...they'd never see the notice.  Probably still worthwhile, I would
> think.
> I'm not too keen on constantly removing and adding documents from CVS,
> which could end up being a maintenance nightmare, not to mention a major
> abuse of SCM functionality.  Does anyone have some better ideas for
> marking these documents to make sure that readers know they're looking
> at something out of date?

Two thoughts:

1. Put a notice onthe t-q-s-g/index.html that says what is updated and
what is not;
1.1 Put a similar notice on the top of all translated guides that refers
to the canonical index.html as a reference to see what is up-to-date of
1.2 This is a manual process, so sucks for that.
1.3 This could be applied to other translated documents.

2. Another manual process would be to populate all out-of-date
translations with a watermark image "Translation Out of Date"
2.1 This could be made automagic, that is, when the POT file in CVS is
changed for a guide, all translated guides get the watermark until the
corresponding PO file is updated.

> /me notes ruefully that this would probably be easy in Plone.

Most likely, since this is an essential CMS need.

- Karsten
Karsten Wade, Developer Community Mgr.
Dev Fu :
Fedora :
gpg key : AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the fedora-docs-list mailing list