Browse Source

add information how to find missing translations

Max Mehl 6 months ago
parent
commit
29fd96de60
Signed by: max.mehl <max.mehl@fsfe.org> GPG Key ID: 2704E4AB371E2E92
1 changed files with 16 additions and 1 deletions
  1. 16
    1
      TRANSLATE.md

+ 16
- 1
TRANSLATE.md View File

@@ -114,7 +114,10 @@ website.
114 114
 
115 115
 ### config.toml
116 116
 
117
-To activate your new language, please add it to [config.toml](https://git.fsfe.org/pmpc/website/src/branch/master/site/config.toml). Please do not change any existing content here. Your entry could look like this:
117
+To activate your new language, please add it to 
118
+[config.toml](https://git.fsfe.org/pmpc/website/src/branch/master/site/config.toml). 
119
+Please do not change any existing content here. Your entry could look 
120
+like this:
118 121
 
119 122
 ```
120 123
 [Languages.sv]
@@ -145,3 +148,15 @@ build README section:
145 148
 If you are unsure, you can also send the translations to [FSFE's translators
146 149
 list](https://lists.fsfe.org/mailman/listinfo/translators) to let them
147 150
 proofread by other speakers of your language.
151
+
152
+## How to show missing translations?
153
+
154
+If a string in your language isn't translated, the default English 
155
+version will be used. To find out which parts are missing, you need 
156
+`hugo` installed on your computer.
157
+
158
+Please navigate to the `site/` subdirectory and execute `hugo 
159
+--i18n-warnings | grep i18n`. This shows a list of all missing 
160
+translations of all languages. Please look out for your language code 
161
+in the third column. The fourth column shows the name of the string 
162
+which is missing in your i18n file.

Loading…
Cancel
Save