TildeClub
/
tilde.club
mirror of https://github.com/tildeclub/tilde.club.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

minor tidy to force name change

Edward Vielmetti 2014-10-14 19:03:30 -04:00
parent 908440a910
commit d3bf888aa9
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
--FOR-TRANSLATORS----.md → For-Translators.md

@ -1,6 +1,6 @@
Please follow these suggested guidlines when translating Tilde doc's: 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. here as a placeholder.
I would suggest linking translations to the specific github commit that 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 1) Diffing the "current" FAQ from the version linked by the translation to
see what changed. see what changed.
2) Translating/updating just the parts that 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 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 sync. And it becomes very apparent to a volunteer what needs to be done
next. next.
This process can be documented more intelligently than I have done here This process can be documented more intelligently than I have done here
inside the FAQ itself, in time, if it is adopted. inside the FAQ itself, in time, if it is adopted.