From 908440a91003ce97b814a0b838e529f766cb2e97 Mon Sep 17 00:00:00 2001 From: vimes1984 Date: Tue, 14 Oct 2014 15:07:01 -0700 Subject: [PATCH] Created --FOR TRANSLATORS---- (markdown) --- --FOR-TRANSLATORS----.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 --FOR-TRANSLATORS----.md diff --git a/--FOR-TRANSLATORS----.md b/--FOR-TRANSLATORS----.md new file mode 100644 index 0000000..402b761 --- /dev/null +++ b/--FOR-TRANSLATORS----.md @@ -0,0 +1,21 @@ +Please follow these suggested guidlines when translating Tilde doc's: + +This will sound like gobbledygook if you don't know git, but I'm putting it +here as a placeholder. + +I would suggest linking translations to the specific github commit that +they are translating (Just by adding a line with a link to the specific +commit on Github.) +This means that updating translations can be as simple as: + +1) Diffing the "current" FAQ from the version linked by the translation to +see what changed. +2) Translating/updating just the parts that changed. +3) Updating the "based on revision [LINK]" at the top of the translated FAQ + +Thus even if things go out of sync it will be very clear what went out of +sync. And it becomes very apparent to a volunteer what needs to be done +next. + +This process can be documented more intelligently than I have done here +inside the FAQ itself, in time, if it is adopted. \ No newline at end of file