mirror of
https://github.com/tildeclub/tilde.club.git
synced 2026-11-20 14:35:38 +00:00
minor tidy to force name change
1 parent
908440a910
commit
d3bf888aa9
1 file changed
+3
-3
@@ -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.
|
||||
inside the FAQ itself, in time, if it is adopted.
|
||||
Reference in new issue
Block a user