fix links so GH mirror works too

diff --git a/Home.md b/Home.md
index 298829c80e0bafb30bd280d1a075141fe30a08a4..ba5388347e6db3f49b9a2286b71871286e55e969 100644 (file)
--- a/Home.md
+++ b/Home.md
@@ -128,11 +128,11 @@ Mutators change the configuration of the game play, e.g. how weapon appears, whi
 
 ### [Translating](Translating)
 -   [Translation website](https://www.transifex.com/team-xonotic/xonotic/dashboard/)
--   [Translation guidelines](Translation guidelines)
-     -   [List of translation placeholders](List of translation placeholders)
-     -   [List of color codes](List of color codes)
-     -   [List of translation prefixes](List of translation prefixes)
--   [How to test your translations](Test your translations)
+-   [Translation guidelines](Translation-guidelines)
+     -   [List of translation placeholders](List-of-translation-placeholders)
+     -   [List of color codes](List-of-color-codes)
+     -   [List of translation prefixes](List-of-translation-prefixes)
+-   [How to test your translations](Test-your-translations)
 
 ### [Modeling](Modeling)
 -   [Textures know-how](Textures)

diff --git a/Translation-guidelines.md b/Translation-guidelines.md
index f2a80c9eb42c761ec9c1e5366867f75d9442fc73..25d685c7792975c31e59f2067c54d172748f60ea 100644 (file)
--- a/Translation-guidelines.md
+++ b/Translation-guidelines.md
@@ -2,13 +2,13 @@
 
 *  Always match newlines and white space with translation strings: if a string has 4 spaces in the beginning of it in English, do the same thing for the translation. If a string has 2 newlines at the end of it, or one in the middle and another at the end, repeat the same thing in the translated string.
 
-*  Be careful not to mess with variables in the strings and with other placeholders. [Variables and placeholders](List of translation placeholders) are codes that will be replaced with something else in the final text.
+*  Be careful not to mess with variables in the strings and with other placeholders. [Variables and placeholders](List-of-translation-placeholders) are codes that will be replaced with something else in the final text.
 
 *  Always match variables in the strings properly, as explained here: http://docs.translatehouse.org/projects/localization-guide/en/latest/guide/translation/variables.html
 
-*  Keep color codes the same, like `^BG` or `^TC` or `^F4` or `^2`, these are special color codes and are handled by the HUD/text rendering code. See the [List of color codes](List of color codes).
+*  Keep color codes the same, like `^BG` or `^TC` or `^F4` or `^2`, these are special color codes and are handled by the HUD/text rendering code. See the [List of color codes](List-of-color-codes).
 
-*  Some strings have prefixes which help you know the context of the string... For example, say there is a list box in the menu which controls effects settings, we can add a prefix into the translatable string for each item in the list like this: `PREFIX^translatable text`. In the case of effects, we can do: `EFFECTS^Low`, `EFFECTS^Medium`, and `EFFECTS^High`, and you can then know the context of the Low/Medium/High translation easily. When forming the final translated string, REMOVE THE PREFIX AND THE ^ SYMBOL. However, be careful not to confuse these with color codes or intentional placements of ^. If in doubt, read the code, context sensitive lines of code which use this prefix idea will have a ZCTX() or CTX() wrapper around the whole string, giving you a good clarification as to how to proceed. You can also refer to the [List of prefixes](List of translation prefixes).
+*  Some strings have prefixes which help you know the context of the string... For example, say there is a list box in the menu which controls effects settings, we can add a prefix into the translatable string for each item in the list like this: `PREFIX^translatable text`. In the case of effects, we can do: `EFFECTS^Low`, `EFFECTS^Medium`, and `EFFECTS^High`, and you can then know the context of the Low/Medium/High translation easily. When forming the final translated string, REMOVE THE PREFIX AND THE ^ SYMBOL. However, be careful not to confuse these with color codes or intentional placements of ^. If in doubt, read the code, context sensitive lines of code which use this prefix idea will have a ZCTX() or CTX() wrapper around the whole string, giving you a good clarification as to how to proceed. You can also refer to the [List of prefixes](List-of-translation-prefixes).
 
 *  Normally do not translate proper nouns, like most weapon names (excluding Machinegun, Shotgun, etc), or game mode names, unless they make sense in your language to be translated. Mutators CAN be translated, but not mutators which have proper names, like "MinstaGib", or "NIX" which is an acronym.
 
@@ -24,4 +24,4 @@
 
 *  Overall, just try and write the translation in a way which fits your language best... If something is silly in English and it's okay to do it silly in your language, then go ahead: just try and make it match the English meaning as closely as possible.
 
-*  After you have completed translations, please test them both in the menu and in game to make sure there aren't any mistakes: [Test your translations](Test your translations). WARNING: If you make a mistake while translating a notification system string, it CAN crash the game upon loading, as the notification system analyzes all strings and ensures they are written correctly! ( See here, an earlier problem that have been noticed on the old German translations: http://i.imgur.com/mePBYvO.jpg ).
\ No newline at end of file
+*  After you have completed translations, please test them both in the menu and in game to make sure there aren't any mistakes: [Test your translations](Test-your-translations). WARNING: If you make a mistake while translating a notification system string, it CAN crash the game upon loading, as the notification system analyzes all strings and ensures they are written correctly! ( See here, an earlier problem that have been noticed on the old German translations: http://i.imgur.com/mePBYvO.jpg ).