New Crowdin updates (#491)

* New translations executable-arguments.md (Chinese Simplified) * New translations faq.md (Chinese Simplified) * New translations glob-regex-parser-input.md (Chinese Simplified) * New translations spec-glob-chars.md (Chinese Simplified) * New translations special-glob-input.md (Chinese Simplified) * New translations title-from-variable.md (Chinese Simplified) * New translations user-exceptions.md (Chinese Simplified) * New translations ea-desktop-parser-input.md (Chinese Traditional) * New translations UWP-parser-input.md (Chinese Traditional) * New translations UWP-parser.md (Chinese Traditional) * New translations langStrings.json (German) * New translations UWP-parser-input.md (German) * New translations UWP-parser.md (German)
SteamGridDB · Apr 1, 2023 · eba3195 · eba3195
1 parent d880e27
commit eba3195
Show file tree

Hide file tree

Showing 13 changed files with 38 additions and 26 deletions.
diff --git a/src/lang/de-DE/langStrings.json b/src/lang/de-DE/langStrings.json
@@ -111,10 +111,10 @@
     }
   },
   "UWPParser": {
-    "UWPDirTitle": "Games directory",
-    "UWPLauncherModeTitle": "Launch game as UWP instead of launcher helper.",
+    "UWPDirTitle": "Spiele-Verzeichnis",
+    "UWPLauncherModeTitle": "Starte das Spiel als UWP statt als Launcher Helfer.",
     "errors": {
-      "UWPNotCompatible": "> UWP parser failed with fatal error:\n ${error}",
+      "UWPNotCompatible": "> UWP Parser mit folgendem Fehler fehlgeschlagen:\n ${error}",
       "fatalError__i": "> UWP parser is not compatible in this platform."
     }
   },

diff --git a/src/lang/de-DE/markdown/UWP-parser-input.md b/src/lang/de-DE/markdown/UWP-parser-input.md
@@ -1,9 +1,9 @@
 # Unique inputs for UWP Parser
 
-## Games directory
+## Spiele-Verzeichnis
 
 UWP apps are supposed to say if they are games or apps, and this is not always correct. To remediate this, it's useful to say where you're installing your games to only scan for those UWP apps. Defaults to `C:\XboxGames`.
 
-## Launch as UWP or from GameLaunchHelper.exe
+## Starte als UWP oder von GameLaunchHelper.exe
 
-Gamepass games can be launched both ways, although UWP is preffered.
+Gamepass-Spiele können auf beiden Wegen gestartet werden, obwohl UWP bevorzugt ist.
diff --git a/src/lang/de-DE/markdown/UWP-parser.md b/src/lang/de-DE/markdown/UWP-parser.md
@@ -1,7 +1,7 @@
-# UWP Games Parser
+# UWP Spiele-Parser
 
-This parser imports `UWP` games in your Windows OS, having a games library path as reference. Useful for PC gamepass!
+Dieser Parser importiert `UWP` Spiele in dein Windows Betriebssystem, mit einem Pfad der Spielebibliothek als Referenz. Nützlich für PC-Gamepass!
 
-## Compatibility
+## Kompabilität
 
-This parser should only work on `Windows 10` and `Windows 11`.
+Dieser Parser sollte nur unter `Windows 10` und `Windows 11` funktionieren.
diff --git a/src/lang/zh-CN/markdown/executable-arguments.md b/src/lang/zh-CN/markdown/executable-arguments.md
@@ -186,7 +186,7 @@
 
 ### 函数变量示例
 
-Let's say that `${title}` variable equals to `Pokémon (USA) (Disc 1).iso`. Then these variables: Then these variables: 然后这些变量： 然后这些变量： 然后这些变量：
+Let's say that `${title}` variable equals to `Pokémon (USA) (Disc 1).iso`. Then these variables: Then these variables: 然后这些变量： 然后这些变量： 然后这些变量： 然后这些变量：
 ```
 ${/.*/|${title}}                           //匹配所有内容
 ${/(.*)/|${title}}                         //捕获所有内容

diff --git a/src/lang/zh-CN/markdown/faq.md b/src/lang/zh-CN/markdown/faq.md
@@ -1,6 +1,6 @@
 # 常见问题
 
-Read this if you're still having trouble with configuration. For most examples the following will be used unless specified otherwise: Read this if you're still having trouble with configuration. For most examples the following will be used unless specified otherwise: For most examples the following will be used unless specified otherwise: 除非另有说明，否则大多数情况下将使用以下内容： 除非另有说明，否则大多数情况下将使用以下内容：
+Read this if you're still having trouble with configuration. For most examples the following will be used unless specified otherwise: Read this if you're still having trouble with configuration. For most examples the following will be used unless specified otherwise: For most examples the following will be used unless specified otherwise: 除非另有说明，否则大多数情况下将使用以下内容： 除非另有说明，否则大多数情况下将使用以下内容： 除非另有说明，否则大多数情况下将使用以下内容：
 
 |            |                                            |
 | ---------- | ------------------------------------------ |

diff --git a/src/lang/zh-CN/markdown/glob-regex-parser-input.md b/src/lang/zh-CN/markdown/glob-regex-parser-input.md
@@ -6,7 +6,7 @@
 
 ## 它是如何工作的？
 
-In addition to special glob characters, glob parser requires you to enter `${/.../}`{.noWrap} variable. Parser will locate it's position inside your  glob, for example: 解析器将定位其位置在您的全局变量中，例如： 解析器将定位其位置在您的全局变量中，例如：
+In addition to special glob characters, glob parser requires you to enter `${/.../}`{.noWrap} variable. Parser will locate it's position inside your  glob, for example: 解析器将定位其位置在您的全局变量中，例如： 解析器将定位其位置在您的全局变量中，例如： 解析器将定位其位置在您的全局变量中，例如：
 
 | 用户的 glob              | 位置         |
 | --------------------- | ---------- |

diff --git a/src/lang/zh-CN/markdown/spec-glob-chars.md b/src/lang/zh-CN/markdown/spec-glob-chars.md
@@ -54,13 +54,13 @@
 - `C:/dir1/dir2/file.txt`
 - `C:/dir1/dir3/dir4/file.txt`
 
-Braced sets also have less useful range syntax `{x..x}` where `x` is a single character. For example, `C:/dir1/dir{2..4}/file.txt` will expand to: 例如，`C:/dir1/dir{2..4}/file.txt` 将会扩展为： 例如，`C:/dir1/dir{2..4}/file.txt` 将会扩展为：
+Braced sets also have less useful range syntax `{x..x}` where `x` is a single character. For example, `C:/dir1/dir{2..4}/file.txt` will expand to: 例如，`C:/dir1/dir{2..4}/file.txt` 将会扩展为： 例如，`C:/dir1/dir{2..4}/file.txt` 将会扩展为： 例如，`C:/dir1/dir{2..4}/file.txt` 将会扩展为：
 
 - `C:/dir1/dir2/file.txt`
 - `C:/dir1/dir3/file.txt`
 - `C:/dir1/dir4/file.txt`
 
-Braced set is expanded **before** actual parsing, therefore can be useful to generate different subdirectories or even [extended glob matchers](#extended-glob-matchers). For example, `C:/+(a|{b),c)}/file.txt` would expand to: 例如，`C:/+(a|{b),c)}/file.txt` 将扩展为： 例如，`C:/+(a|{b),c)}/file.txt` 将扩展为：
+Braced set is expanded **before** actual parsing, therefore can be useful to generate different subdirectories or even [extended glob matchers](#extended-glob-matchers). For example, `C:/+(a|{b),c)}/file.txt` would expand to: 例如，`C:/+(a|{b),c)}/file.txt` 将扩展为： 例如，`C:/+(a|{b),c)}/file.txt` 将扩展为： 例如，`C:/+(a|{b),c)}/file.txt` 将扩展为：
 
 - `C:/+(a|b)/file.txt`
 - `C:/+(a|c)/file.txt`
diff --git a/src/lang/zh-CN/markdown/special-glob-input.md b/src/lang/zh-CN/markdown/special-glob-input.md
@@ -12,7 +12,7 @@
 
 ### 绝对路径
 
-Let's say that the extracted title is `Metroid Fusion [USA]` and fuzzy title is `Metroid Fusion`. 然后，您可以像这样构建图像路径： 然后，您可以像这样构建图像路径： 然后，您可以像这样构建图像路径：
+Let's say that the extracted title is `Metroid Fusion [USA]` and fuzzy title is `Metroid Fusion`. 然后，您可以像这样构建图像路径： 然后，您可以像这样构建图像路径： 然后，您可以像这样构建图像路径： 然后，您可以像这样构建图像路径：
 
 - `C:/path/to/images/${title}.*`
 - `C:/path/to/images/${fuzzyTitle}.*`
@@ -24,7 +24,7 @@ Let's say that the extracted title is `Metroid Fusion [USA]` and fuzzy title is
 
 ### 相对路径
 
-For this example, let's say that ROMs directory is `C:/ROMS/GBA` and rom itself is `C:/ROMS/GBA/Metroid Fusion [USA].gba`. Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: 设置相对路径，使用 `${filePath}`{.noWrap} 或 `${dir}`{.noWrap} 变量，例如： 设置相对路径，使用 `${filePath}`{.noWrap} 或 `${dir}`{.noWrap} 变量，例如：
+For this example, let's say that ROMs directory is `C:/ROMS/GBA` and rom itself is `C:/ROMS/GBA/Metroid Fusion [USA].gba`. Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: 设置相对路径，使用 `${filePath}`{.noWrap} 或 `${dir}`{.noWrap} 变量，例如： 设置相对路径，使用 `${filePath}`{.noWrap} 或 `${dir}`{.noWrap} 变量，例如： 设置相对路径，使用 `${filePath}`{.noWrap} 或 `${dir}`{.noWrap} 变量，例如：
 
 - `${filePath}/../../../path/to/images/${title}.*`
 - `${dir}/../../path/to/images/${title}.*`

diff --git a/src/lang/zh-CN/markdown/title-from-variable.md b/src/lang/zh-CN/markdown/title-from-variable.md
@@ -18,7 +18,7 @@ ${RPCS3}${rpcs3}
 
 如果启用了此选项，则将执行不区分大小写的匹配，并使用第一个匹配的自定义变量。
 
-## 注意! 该功能是**实验性的**。
+## 注意! 注意! 该功能是**实验性的**。
 
 基本上，它可能会在未来的版本中更改（但很不可能）。 此外，目前唯一添加变量的方法是创建/编辑 SRM 直接使用的 `customVariables.json`。
 
@@ -48,6 +48,17 @@ ${RPCS3}${rpcs3}
         "The Legend Of Zelda": "The Legend Of Link"
     },
     ...
+}
+    {
+    "RPCS3": {
+        "NPUB30698": "Catherine",
+        "NPUB30024": "1942: Joint Strike",
+        ...
+    },
+    "Custom Stuff": {
+        "The Legend Of Zelda": "The Legend Of Link"
+    },
+    ...
 }
     },
     "Custom Stuff": {
@@ -56,6 +67,7 @@ ${RPCS3}${rpcs3}
     ...
 }
 }
+}
 ```
 
 如果您的用户全局变量是 `MyDir/${title}.wad`，并且您在 `MyDir` 中有一个名为 `The Legend of Zelda.wad` 的文件，则可以将标题从自定义变量字段设置为 `${Custom Stuff}` 以获得最终标题 “The Legend of Link”。