Closed GoogleCodeExporter closed 9 years ago
Original comment by chris.paiano@gmail.com
on 27 Oct 2008 at 5:33
I have to disagree with the usage of an encrypted file:
1) it's a free/libre software, if someone wants to mess with the code/CREDITS,
there's always going to be a way;
2) it's a pain to manage and put in place, i'd rather not do that.
I suggest we use different files for different languages with an extension that
corresponds to the 2-letter ISO code (e.g. CREDITS.fr, CREDITS.pt-br, etc.) and
fallback on CREDITS if the localized file does not exist.
Original comment by evily...@gmail.com
on 27 Oct 2008 at 12:56
Original comment by chris.paiano@gmail.com
on 13 Nov 2008 at 9:49
Original comment by chris.paiano@gmail.com
on 13 Nov 2008 at 9:49
While looking at the credits for Issue 451, seems you could just use a dict with
string keys for the lines that need translation (basically the headers) and
escape
them with some other character. This seems like it might be a pain for adding
tutorials in (as they have text that needs translating with them - they would
need to
be in the dict), but otherwise maintains the manageability of the CREDITS
format.
I'll check it out.
Original comment by aked...@gmail.com
on 20 Jan 2009 at 11:42
That's Issue 461, and r832 should take care of it.
Original comment by aked...@gmail.com
on 21 Jan 2009 at 12:57
Original issue reported on code.google.com by
chris.paiano@gmail.com
on 26 Oct 2008 at 4:29