[Gimp-docs] new content localisation

[Axel Wernicke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

in addition to what Vitaly wrote (which I completely agree too) I'd  
suggest to add

<!-- TODO ru <more lang tags here>: translation missing -->

comments for cases like this. The languages to add here are the ones  
that a translation for the new content is missing of course.

This way we can at least make sure that new paragraphs etc. will be  
translated to all languages.
On the other side there might be special cases where you need to have  
some content for a language you don't even can read :)

Such can occur in RARE CASES if you reorganize content. One example is  
making sections from an unstructured page, which means you have the  
choice of inventing a title for foreign languages or removing big  
chunks of content. In such cases I think it's the smaller pain to link  
the missing to en AND ADD A FIXME COMMENT.

Btw. in such cases it can help to have the standard section titles in  
the docs/templates for that language.


Greetings, lexA


Am 08.02.2008 um 18:23 schrieb Vitaly Lomov:

> Hi,
> Whoever creates new content, please don't bunch untranslated languages
> under english. I don't want the users see english when the rest of the
> manual is in russian. It's just as bad as putting russian translation
> under lang="en" by mistake. I understand it may cause some validation
> issues at first, but that can be fixed at the parent node by filtering
> out untranslated languages.
> Vitaly.
> _______________________________________________
> Gimp-docs mailing list
> Gimp-docs at lists.XCF.Berkeley.EDU
> https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs

- ---
/voodoo.css
#meinFeind {position: absolute; bottom: -6ft;}


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iD8DBQFHrWXrR9mXLVsAbiQRApweAKDs75bBXs1w40szD7BQsiQi6i6MNgCcCAtG
qTp6b7BPRH1ykvfo/+vtIPQ=
=QXmy
-----END PGP SIGNATURE-----