From d3bf888aa9e354542745a778e01eb0e9571a6849 Mon Sep 17 00:00:00 2001 From: Edward Vielmetti Date: Tue, 14 Oct 2014 19:03:30 -0400 Subject: [PATCH] minor tidy to force name change --- --FOR-TRANSLATORS----.md => For-Translators.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename --FOR-TRANSLATORS----.md => For-Translators.md (77%) diff --git a/--FOR-TRANSLATORS----.md b/For-Translators.md similarity index 77% rename from --FOR-TRANSLATORS----.md rename to For-Translators.md index 402b761..8c0e3b1 100644 --- a/--FOR-TRANSLATORS----.md +++ b/For-Translators.md @@ -1,6 +1,6 @@ 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 +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 @@ -11,11 +11,11 @@ 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 +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 +inside the FAQ itself, in time, if it is adopted.