From 4558a72cf18e7b291d871c7d4e098ba28ca54012 Mon Sep 17 00:00:00 2001 From: Jozen Blue Martinez Date: Thu, 27 Apr 2023 05:19:35 +0800 Subject: [PATCH] New Crowdin updates (#524) * New translations executable-arguments.md (Chinese Simplified) * New translations glob-regex-parser-input.md (Chinese Simplified) * New translations local-images.md (Chinese Simplified) * New translations special-glob-input.md (Chinese Simplified) * New translations title-from-variable.md (Chinese Simplified) * New translations user-accounts.md (Chinese Simplified) * New translations about.md (Chinese Traditional) * New translations itch-io-parser-input.md (Chinese Traditional) * New translations local-images.md (Chinese Traditional) * New translations special-glob-input.md (Chinese Traditional) * New translations user-accounts.md (Chinese Traditional) * New translations user-exceptions.md (Chinese Traditional) * New translations ea-desktop-parser-input.md (Chinese Traditional) * New translations user-accounts.md (Portuguese) * New translations user-accounts.md (Portuguese, Brazilian) * New translations steam-parser-input.md (Chinese Traditional) * New translations parsers-list.md (Chinese Traditional) * New translations langStrings.json (Chinese Simplified) * New translations ea-desktop-parser-input.md (Chinese Simplified) * New translations langStrings.json (Chinese Traditional) * New translations ea-desktop-parser-input.md (Chinese Traditional) * New translations langStrings.json (Romanian) * New translations langStrings.json (French) * New translations langStrings.json (Spanish) * New translations langStrings.json (Afrikaans) * New translations langStrings.json (Arabic) * New translations langStrings.json (Catalan) * New translations langStrings.json (Czech) * New translations langStrings.json (Danish) * New translations langStrings.json (German) * New translations langStrings.json (Greek) * New translations langStrings.json (Finnish) * New translations langStrings.json (Hebrew) * New translations langStrings.json (Hungarian) * New translations langStrings.json (Italian) * New translations langStrings.json (Japanese) * New translations langStrings.json (Korean) * New translations langStrings.json (Dutch) * New translations langStrings.json (Norwegian) * New translations langStrings.json (Polish) * New translations langStrings.json (Portuguese) * New translations langStrings.json (Russian) * New translations langStrings.json (Serbian (Cyrillic)) * New translations langStrings.json (Swedish) * New translations langStrings.json (Turkish) * New translations langStrings.json (Ukrainian) * New translations langStrings.json (Vietnamese) * New translations langStrings.json (Portuguese, Brazilian) * New translations langStrings.json (Spanish, Latin America) * New translations ea-desktop-parser-input.md (French) * New translations ea-desktop-parser-input.md (Spanish) * New translations ea-desktop-parser-input.md (Arabic) * New translations ea-desktop-parser-input.md (German) * New translations ea-desktop-parser-input.md (Italian) * New translations ea-desktop-parser-input.md (Japanese) * New translations ea-desktop-parser-input.md (Korean) * New translations ea-desktop-parser-input.md (Dutch) * New translations ea-desktop-parser-input.md (Polish) * New translations ea-desktop-parser-input.md (Portuguese) * New translations ea-desktop-parser-input.md (Russian) * New translations ea-desktop-parser-input.md (Turkish) * New translations ea-desktop-parser-input.md (Portuguese, Brazilian) * New translations ea-desktop-parser-input.md (Spanish, Latin America) * New translations ea-desktop-parser-input.md (Romanian) * New translations ea-desktop-parser-input.md (Afrikaans) * New translations ea-desktop-parser-input.md (Catalan) * New translations ea-desktop-parser-input.md (Czech) * New translations ea-desktop-parser-input.md (Danish) * New translations ea-desktop-parser-input.md (Greek) * New translations ea-desktop-parser-input.md (Finnish) * New translations ea-desktop-parser-input.md (Hebrew) * New translations ea-desktop-parser-input.md (Hungarian) * New translations ea-desktop-parser-input.md (Norwegian) * New translations ea-desktop-parser-input.md (Serbian (Cyrillic)) * New translations ea-desktop-parser-input.md (Swedish) * New translations ea-desktop-parser-input.md (Ukrainian) * New translations ea-desktop-parser-input.md (Vietnamese) --- src/lang/af-ZA/langStrings.json | 4 +++- .../af-ZA/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/ar-SA/langStrings.json | 4 +++- .../ar-SA/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/ca-ES/langStrings.json | 4 +++- .../ca-ES/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/cs-CZ/langStrings.json | 4 +++- .../cs-CZ/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/da-DK/langStrings.json | 4 +++- .../da-DK/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/de-DE/langStrings.json | 4 +++- .../de-DE/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/el-GR/langStrings.json | 4 +++- .../el-GR/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/es-419/langStrings.json | 4 +++- .../markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/es-ES/langStrings.json | 4 +++- .../es-ES/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/fi-FI/langStrings.json | 4 +++- .../fi-FI/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/fr-FR/langStrings.json | 4 +++- .../fr-FR/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/he-IL/langStrings.json | 4 +++- .../he-IL/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/hu-HU/langStrings.json | 4 +++- .../hu-HU/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/it-IT/langStrings.json | 4 +++- .../it-IT/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/ja-JP/langStrings.json | 4 +++- .../ja-JP/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/ko-KR/langStrings.json | 4 +++- .../ko-KR/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/nl-NL/langStrings.json | 4 +++- .../nl-NL/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/no-NO/langStrings.json | 4 +++- .../no-NO/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/pl-PL/langStrings.json | 4 +++- .../pl-PL/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/pt-BR/langStrings.json | 4 +++- .../pt-BR/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/pt-BR/markdown/user-accounts.md | 2 +- src/lang/pt-PT/langStrings.json | 4 +++- .../pt-PT/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/pt-PT/markdown/user-accounts.md | 2 +- src/lang/ro-RO/langStrings.json | 4 +++- .../ro-RO/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/ru-RU/langStrings.json | 4 +++- .../ru-RU/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/sr-SP/langStrings.json | 4 +++- .../sr-SP/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/sv-SE/langStrings.json | 4 +++- .../sv-SE/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/tr-TR/langStrings.json | 4 +++- .../tr-TR/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/uk-UA/langStrings.json | 4 +++- .../uk-UA/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/vi-VN/langStrings.json | 4 +++- .../vi-VN/markdown/ea-desktop-parser-input.md | 4 ++-- src/lang/zh-CN/langStrings.json | 4 +++- .../zh-CN/markdown/ea-desktop-parser-input.md | 4 ++-- .../zh-CN/markdown/executable-arguments.md | 2 +- .../zh-CN/markdown/glob-regex-parser-input.md | 2 +- src/lang/zh-CN/markdown/local-images.md | 2 +- src/lang/zh-CN/markdown/special-glob-input.md | 2 +- .../zh-CN/markdown/title-from-variable.md | 2 +- src/lang/zh-CN/markdown/user-accounts.md | 8 ++++---- src/lang/zh-TW/langStrings.json | 4 +++- src/lang/zh-TW/markdown/about.md | 6 +++--- .../zh-TW/markdown/ea-desktop-parser-input.md | 8 ++++---- .../zh-TW/markdown/itch-io-parser-input.md | 2 +- src/lang/zh-TW/markdown/local-images.md | 4 ++-- src/lang/zh-TW/markdown/parsers-list.md | 2 +- src/lang/zh-TW/markdown/special-glob-input.md | 6 +++--- src/lang/zh-TW/markdown/steam-parser-input.md | 2 +- src/lang/zh-TW/markdown/user-accounts.md | 8 ++++---- src/lang/zh-TW/markdown/user-exceptions.md | 20 +++++++++---------- 76 files changed, 188 insertions(+), 128 deletions(-) diff --git a/src/lang/af-ZA/langStrings.json b/src/lang/af-ZA/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/af-ZA/langStrings.json +++ b/src/lang/af-ZA/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/af-ZA/markdown/ea-desktop-parser-input.md b/src/lang/af-ZA/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/af-ZA/markdown/ea-desktop-parser-input.md +++ b/src/lang/af-ZA/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/ar-SA/langStrings.json b/src/lang/ar-SA/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/ar-SA/langStrings.json +++ b/src/lang/ar-SA/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/ar-SA/markdown/ea-desktop-parser-input.md b/src/lang/ar-SA/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/ar-SA/markdown/ea-desktop-parser-input.md +++ b/src/lang/ar-SA/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/ca-ES/langStrings.json b/src/lang/ca-ES/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/ca-ES/langStrings.json +++ b/src/lang/ca-ES/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/ca-ES/markdown/ea-desktop-parser-input.md b/src/lang/ca-ES/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/ca-ES/markdown/ea-desktop-parser-input.md +++ b/src/lang/ca-ES/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/cs-CZ/langStrings.json b/src/lang/cs-CZ/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/cs-CZ/langStrings.json +++ b/src/lang/cs-CZ/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/cs-CZ/markdown/ea-desktop-parser-input.md b/src/lang/cs-CZ/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/cs-CZ/markdown/ea-desktop-parser-input.md +++ b/src/lang/cs-CZ/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/da-DK/langStrings.json b/src/lang/da-DK/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/da-DK/langStrings.json +++ b/src/lang/da-DK/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/da-DK/markdown/ea-desktop-parser-input.md b/src/lang/da-DK/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/da-DK/markdown/ea-desktop-parser-input.md +++ b/src/lang/da-DK/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/de-DE/langStrings.json b/src/lang/de-DE/langStrings.json index 485c07833b..dd2f973565 100644 --- a/src/lang/de-DE/langStrings.json +++ b/src/lang/de-DE/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/de-DE/markdown/ea-desktop-parser-input.md b/src/lang/de-DE/markdown/ea-desktop-parser-input.md index 505a8ed32d..a0cd7f35ed 100644 --- a/src/lang/de-DE/markdown/ea-desktop-parser-input.md +++ b/src/lang/de-DE/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games-Verzeichnis +## EA Games Directory Override Standardmäßig geht der Steam ROM Manager davon aus, dass deine `EA Desktop` Spiele unter `C:\Program Files\EA Spiele installiert sind. Dieses Feld erlaubt es dir, den Speicherort zu ändern, unter dem deine Spiele installiert sind, z.B.`D:\Games\EA Games`. -## Starte über EA Desktop +## Launch Games Via EA Desktop Wenn aktiviert, wird SRM anstatt der ausführbaren Datei eine Verknüpfung zu `origin2://game/launch/?offerIds=${gameid}` hinzufügen. Dies stellt sicher, dass das Spiel über EA gestartet wird und Zugang zu Online-Diensten hat. `Dies ist erforderlich, um EA Play Spiele hinzuzufügen. EA Play Spiele werden nicht erkannt, wenn dies nicht eingeschaltet wird.` diff --git a/src/lang/el-GR/langStrings.json b/src/lang/el-GR/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/el-GR/langStrings.json +++ b/src/lang/el-GR/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/el-GR/markdown/ea-desktop-parser-input.md b/src/lang/el-GR/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/el-GR/markdown/ea-desktop-parser-input.md +++ b/src/lang/el-GR/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/es-419/langStrings.json b/src/lang/es-419/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/es-419/langStrings.json +++ b/src/lang/es-419/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/es-419/markdown/ea-desktop-parser-input.md b/src/lang/es-419/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/es-419/markdown/ea-desktop-parser-input.md +++ b/src/lang/es-419/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/es-ES/langStrings.json b/src/lang/es-ES/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/es-ES/langStrings.json +++ b/src/lang/es-ES/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/es-ES/markdown/ea-desktop-parser-input.md b/src/lang/es-ES/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/es-ES/markdown/ea-desktop-parser-input.md +++ b/src/lang/es-ES/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/fi-FI/langStrings.json b/src/lang/fi-FI/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/fi-FI/langStrings.json +++ b/src/lang/fi-FI/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/fi-FI/markdown/ea-desktop-parser-input.md b/src/lang/fi-FI/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/fi-FI/markdown/ea-desktop-parser-input.md +++ b/src/lang/fi-FI/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/fr-FR/langStrings.json b/src/lang/fr-FR/langStrings.json index ccf5176594..69ae5c3ae0 100644 --- a/src/lang/fr-FR/langStrings.json +++ b/src/lang/fr-FR/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/fr-FR/markdown/ea-desktop-parser-input.md b/src/lang/fr-FR/markdown/ea-desktop-parser-input.md index 4d3671f470..337d6162e8 100644 --- a/src/lang/fr-FR/markdown/ea-desktop-parser-input.md +++ b/src/lang/fr-FR/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # Entrées spécifiques de l'analyseur EA Desktop -## Répertoire des jeux EA Desktop +## EA Games Directory Override Par défaut, Steam ROM Manager assume que vos jeux `EA Desktop` sont installés sur ``C:\Program Files\EA Games\`. Ce champ vous permet de remplacer ce chemin à l'endroit où vos jeux sont installés, par exemple``D:\Games\EA Games`. -## Lancer via EA Desktop +## Launch Games Via EA Desktop Si cette option est activée, SRM ajoutera un raccourci à `origin2://game/launch/?offerIds=${gameid}` au lieu de l'exécutable du jeu. Cela garantit le lancement du jeu via EA et donnera accès aux services en ligne. `Ceci est nécessaire pour ajouter des jeux EA Play. Les jeux EA Play ne seront pas détectés si cette option n'est pas activée.` diff --git a/src/lang/he-IL/langStrings.json b/src/lang/he-IL/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/he-IL/langStrings.json +++ b/src/lang/he-IL/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/he-IL/markdown/ea-desktop-parser-input.md b/src/lang/he-IL/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/he-IL/markdown/ea-desktop-parser-input.md +++ b/src/lang/he-IL/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/hu-HU/langStrings.json b/src/lang/hu-HU/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/hu-HU/langStrings.json +++ b/src/lang/hu-HU/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/hu-HU/markdown/ea-desktop-parser-input.md b/src/lang/hu-HU/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/hu-HU/markdown/ea-desktop-parser-input.md +++ b/src/lang/hu-HU/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/it-IT/langStrings.json b/src/lang/it-IT/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/it-IT/langStrings.json +++ b/src/lang/it-IT/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/it-IT/markdown/ea-desktop-parser-input.md b/src/lang/it-IT/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/it-IT/markdown/ea-desktop-parser-input.md +++ b/src/lang/it-IT/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/ja-JP/langStrings.json b/src/lang/ja-JP/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/ja-JP/langStrings.json +++ b/src/lang/ja-JP/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/ja-JP/markdown/ea-desktop-parser-input.md b/src/lang/ja-JP/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/ja-JP/markdown/ea-desktop-parser-input.md +++ b/src/lang/ja-JP/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/ko-KR/langStrings.json b/src/lang/ko-KR/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/ko-KR/langStrings.json +++ b/src/lang/ko-KR/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/ko-KR/markdown/ea-desktop-parser-input.md b/src/lang/ko-KR/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/ko-KR/markdown/ea-desktop-parser-input.md +++ b/src/lang/ko-KR/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/nl-NL/langStrings.json b/src/lang/nl-NL/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/nl-NL/langStrings.json +++ b/src/lang/nl-NL/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/nl-NL/markdown/ea-desktop-parser-input.md b/src/lang/nl-NL/markdown/ea-desktop-parser-input.md index 0f337e42ac..7992e2b3fb 100644 --- a/src/lang/nl-NL/markdown/ea-desktop-parser-input.md +++ b/src/lang/nl-NL/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser-specifieke inputs -## EA-desktopgameslijst +## EA Games Directory Override Standaard gaat Steam ROM Manager ervan uit dat je `EA Desktop`-spellen zijn geïnstalleerd in ``C:\Program Files\EA Games\`. Met dit veld kun je dat wijzigen naar waar je games geïnstalleerd zijn, bijv.``D:\Games\EA Games`. -## Start via EA Desktop +## Launch Games Via EA Desktop Indien ingeschakeld, SRM voegt een snelkoppeling toe naar `origin2://game/launch/?offerIds=${gameid}` in plaats van alleen het uitvoerbare bestand van de game. Dit zorgt ervoor dat de game via EA wordt gelanceerd en toegang heeft tot online services. `Dit is vereist om EA Play-games toe te voegen. EA Play-games worden niet gedetecteerd als dit niet is ingeschakeld.` diff --git a/src/lang/no-NO/langStrings.json b/src/lang/no-NO/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/no-NO/langStrings.json +++ b/src/lang/no-NO/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/no-NO/markdown/ea-desktop-parser-input.md b/src/lang/no-NO/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/no-NO/markdown/ea-desktop-parser-input.md +++ b/src/lang/no-NO/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/pl-PL/langStrings.json b/src/lang/pl-PL/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/pl-PL/langStrings.json +++ b/src/lang/pl-PL/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/pl-PL/markdown/ea-desktop-parser-input.md b/src/lang/pl-PL/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/pl-PL/markdown/ea-desktop-parser-input.md +++ b/src/lang/pl-PL/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/pt-BR/langStrings.json b/src/lang/pt-BR/langStrings.json index 36444e2ccf..035e16f2c5 100644 --- a/src/lang/pt-BR/langStrings.json +++ b/src/lang/pt-BR/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/pt-BR/markdown/ea-desktop-parser-input.md b/src/lang/pt-BR/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/pt-BR/markdown/ea-desktop-parser-input.md +++ b/src/lang/pt-BR/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/pt-BR/markdown/user-accounts.md b/src/lang/pt-BR/markdown/user-accounts.md index a5ce7dad9c..0a770b212f 100644 --- a/src/lang/pt-BR/markdown/user-accounts.md +++ b/src/lang/pt-BR/markdown/user-accounts.md @@ -14,4 +14,4 @@ You can also mix and match: `${56489124}${Apple}` is fine. ## Warning -Você **deve** usar o nome de usuário que você usa para **entrar** no Steam **se** [usar credenciais de conta](#what-does-use-account-credentials-do) estiver ativado: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. +Você **deve** usar o nome de usuário que você usa para **entrar** no Steam **se** [usar credenciais de conta](#what-does-use-account-credentials-do) estiver ativado: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. Você **deve** usar o nome de usuário que você usa para **entrar** no Steam **se** [usar credenciais de conta](#what-does-use-account-credentials-do) estiver ativado: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. diff --git a/src/lang/pt-PT/langStrings.json b/src/lang/pt-PT/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/pt-PT/langStrings.json +++ b/src/lang/pt-PT/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/pt-PT/markdown/ea-desktop-parser-input.md b/src/lang/pt-PT/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/pt-PT/markdown/ea-desktop-parser-input.md +++ b/src/lang/pt-PT/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/pt-PT/markdown/user-accounts.md b/src/lang/pt-PT/markdown/user-accounts.md index 3d71ce410e..86e9e674ce 100644 --- a/src/lang/pt-PT/markdown/user-accounts.md +++ b/src/lang/pt-PT/markdown/user-accounts.md @@ -14,4 +14,4 @@ You can also mix and match: `${56489124}${Apple}` is fine. ## Warning -You **must** use the username you use to **log in** into Steam **if** [use account credentials](#what-does-use-account-credentials-do) is enabled: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. +You **must** use the username you use to **log in** into Steam **if** [use account credentials](#what-does-use-account-credentials-do) is enabled: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. diff --git a/src/lang/ro-RO/langStrings.json b/src/lang/ro-RO/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/ro-RO/langStrings.json +++ b/src/lang/ro-RO/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/ro-RO/markdown/ea-desktop-parser-input.md b/src/lang/ro-RO/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/ro-RO/markdown/ea-desktop-parser-input.md +++ b/src/lang/ro-RO/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/ru-RU/langStrings.json b/src/lang/ru-RU/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/ru-RU/langStrings.json +++ b/src/lang/ru-RU/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/ru-RU/markdown/ea-desktop-parser-input.md b/src/lang/ru-RU/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/ru-RU/markdown/ea-desktop-parser-input.md +++ b/src/lang/ru-RU/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/sr-SP/langStrings.json b/src/lang/sr-SP/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/sr-SP/langStrings.json +++ b/src/lang/sr-SP/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/sr-SP/markdown/ea-desktop-parser-input.md b/src/lang/sr-SP/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/sr-SP/markdown/ea-desktop-parser-input.md +++ b/src/lang/sr-SP/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/sv-SE/langStrings.json b/src/lang/sv-SE/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/sv-SE/langStrings.json +++ b/src/lang/sv-SE/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/sv-SE/markdown/ea-desktop-parser-input.md b/src/lang/sv-SE/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/sv-SE/markdown/ea-desktop-parser-input.md +++ b/src/lang/sv-SE/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/tr-TR/langStrings.json b/src/lang/tr-TR/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/tr-TR/langStrings.json +++ b/src/lang/tr-TR/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/tr-TR/markdown/ea-desktop-parser-input.md b/src/lang/tr-TR/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/tr-TR/markdown/ea-desktop-parser-input.md +++ b/src/lang/tr-TR/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/uk-UA/langStrings.json b/src/lang/uk-UA/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/uk-UA/langStrings.json +++ b/src/lang/uk-UA/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/uk-UA/markdown/ea-desktop-parser-input.md b/src/lang/uk-UA/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/uk-UA/markdown/ea-desktop-parser-input.md +++ b/src/lang/uk-UA/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/vi-VN/langStrings.json b/src/lang/vi-VN/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/vi-VN/langStrings.json +++ b/src/lang/vi-VN/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/vi-VN/markdown/ea-desktop-parser-input.md b/src/lang/vi-VN/markdown/ea-desktop-parser-input.md index 944db0f2fc..7990efb5b5 100644 --- a/src/lang/vi-VN/markdown/ea-desktop-parser-input.md +++ b/src/lang/vi-VN/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory +## EA Games Directory Override By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. `This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/zh-CN/langStrings.json b/src/lang/zh-CN/langStrings.json index 506bc43f76..a35e301096 100644 --- a/src/lang/zh-CN/langStrings.json +++ b/src/lang/zh-CN/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/zh-CN/markdown/ea-desktop-parser-input.md b/src/lang/zh-CN/markdown/ea-desktop-parser-input.md index f948924291..803b31ed9e 100644 --- a/src/lang/zh-CN/markdown/ea-desktop-parser-input.md +++ b/src/lang/zh-CN/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop 解析器特定输入 -## EA Desktop 游戏目录 +## EA Games Directory Override 默认情况下，Steam ROM Manager 假定您的 `EA Desktop` 游戏已安装在 `C:\Program Files\EA Games\。 该字段允许您更改游戏安装的位置，例如`D:\Games\EA Games。 -## 通过 EA Desktop 启动 +## Launch Games Via EA Desktop 如果启用了 SRM，它将添加一个快捷方式到 `origin2://game/launch/?offerIds=${gameid}` 而不仅仅是游戏的可执行文件。 这将确保游戏通过 EA 启动，并且可以访问在线服务。 `需要这个才能添加 EA Play 游戏。 This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/zh-CN/markdown/executable-arguments.md b/src/lang/zh-CN/markdown/executable-arguments.md index bb4388465f..ad1d42da5c 100644 --- 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/glob-regex-parser-input.md b/src/lang/zh-CN/markdown/glob-regex-parser-input.md index e798af79a9..84c6a0d022 100644 --- 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/local-images.md b/src/lang/zh-CN/markdown/local-images.md index e4f5803d78..d3c6550307 100644 --- a/src/lang/zh-CN/markdown/local-images.md +++ b/src/lang/zh-CN/markdown/local-images.md @@ -1,6 +1,6 @@ # 本地图片（可选）`[支持变量]`{.noWrap} -允许使用本地存储的图像。 A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. +允许使用本地存储的图像。 A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Any variable you use in this field that contains special glob characters will have those characters escaped. diff --git a/src/lang/zh-CN/markdown/special-glob-input.md b/src/lang/zh-CN/markdown/special-glob-input.md index b966ab089b..5715088325 100644 --- 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}.*` diff --git a/src/lang/zh-CN/markdown/title-from-variable.md b/src/lang/zh-CN/markdown/title-from-variable.md index def846e0f4..917f633aca 100644 --- 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`。 diff --git a/src/lang/zh-CN/markdown/user-accounts.md b/src/lang/zh-CN/markdown/user-accounts.md index 8525cf72fa..d84717fb71 100644 --- a/src/lang/zh-CN/markdown/user-accounts.md +++ b/src/lang/zh-CN/markdown/user-accounts.md @@ -4,14 +4,14 @@ This field is used to limit SRM's effects to specific user accounts, and takes v `${...}` -This will limit SRM's effects to accounts `XXX` and `YYY` (you may specify as many accounts as you like). Here `XXX` and `YYY` stand in for either: Here `XXX` and `YYY` stand in for either: +This will limit SRM's effects to accounts `XXX` and `YYY` (you may specify as many accounts as you like). Here `XXX` and `YYY` stand in for either: Here `XXX` and `YYY` stand in for either: Here `XXX` and `YYY` stand in for either: -* The account id is the name of the account directory that appears in `/path/to/steam/userdata`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. +* The account id is the name of the account directory that appears in `/path/to/steam/userdata`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. -* A `Steam Username` (the username you use to actually log in to Steam). A `Steam Username` (the username you use to actually log in to Steam). For example you would specify the users `Banana` and `Apple` like `${Banana}${Apple}`. +* A `Steam Username` (the username you use to actually log in to Steam). A `Steam Username` (the username you use to actually log in to Steam). For example you would specify the users `Banana` and `Apple` like `${Banana}${Apple}`. A `Steam Username` (the username you use to actually log in to Steam). For example you would specify the users `Banana` and `Apple` like `${Banana}${Apple}`. You can also mix and match: `${56489124}${Apple}` is fine. ## Warning -**如果** 启用了 [使用帐户凭据](#what-does-use-account-credentials-do)，则 **必须** 使用您在 Steam **登录** 时使用的用户名： If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. +**如果** 启用了 [使用帐户凭据](#what-does-use-account-credentials-do)，则 **必须** 使用您在 Steam **登录** 时使用的用户名： If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. diff --git a/src/lang/zh-TW/langStrings.json b/src/lang/zh-TW/langStrings.json index 609eed5ea4..69e86b7564 100644 --- a/src/lang/zh-TW/langStrings.json +++ b/src/lang/zh-TW/langStrings.json @@ -24,7 +24,9 @@ "remainingImages": "Retrieving urls:", "stopUrlRetrieving": "Stop", "exportSelections": "Export", - "importSelections": "Import" + "importSelections": "Import", + "backButton": "Back", + "logButton": "Log" }, "service": { "info": { diff --git a/src/lang/zh-TW/markdown/about.md b/src/lang/zh-TW/markdown/about.md index e8394f8bd3..2a8ab4f349 100644 --- a/src/lang/zh-TW/markdown/about.md +++ b/src/lang/zh-TW/markdown/about.md @@ -1,6 +1,6 @@ ## System info -In case you're having trouble with SRM, feel free to visit the [discord](https://discord.gg/bnSVJrz) or the [subreddit](https://www.reddit.com/r/SteamRomManager/) and ask for our help. In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: +In case you're having trouble with SRM, feel free to visit the [discord](https://discord.gg/bnSVJrz) or the [subreddit](https://www.reddit.com/r/SteamRomManager/) and ask for our help. In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: In order for us to help you, we would like you to provide this info: * SRM version: **#{APP[version]}** * Operating System: **#{APP[os]}** @@ -22,7 +22,7 @@ Help support continued progress on Steam ROM Manager at: Buy Me A Coffee -If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. +If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. If you enjoy Steam ROM Manager and want it to continue to be useful also consider supporting [SteamGridDB](https://www.steamgriddb.com/)'s Patreon. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. [SteamGridDB](https://www.steamgriddb.com/) hosts all of the artwork Steam ROM Manager uses to make your Steam library the envy of the town, so we should probably help them keep their lights on. @@ -48,6 +48,6 @@ If you enjoy Steam ROM Manager and want it to continue to be useful also conside ### Community * `HE Spoke`{.noWrap} - created a community around SRM. `HE Spoke`{.noWrap} - created a community around SRM. `HE Spoke`{.noWrap} - created a community around SRM. Creator of [Steam](https://steamcommunity.com/groups/steamrommanager) and [Discord](https://discord.gg/bnSVJrz) groups. Also helps users setup SRM in [Discord](https://discord.gg/bnSVJrz). Also helps users setup SRM in [Discord](https://discord.gg/bnSVJrz). Also helps users setup SRM in [Discord](https://discord.gg/bnSVJrz). -* `livedeht`{.noWrap} - Helps users setup SRM with and without [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). +* `livedeht`{.noWrap} - Helps users setup SRM with and without [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). Current maintainer of [EmuDeck](https://www.emudeck.com/). * `Choko`{.noWrap} - Helps users setup SRM in [Discord](https://discord.gg/bnSVJrz). * `Xav83`{.noWrap} - Creator and maintainer of SRM's [Chocolatey package](https://community.chocolatey.org/packages/steam-rom-manager) diff --git a/src/lang/zh-TW/markdown/ea-desktop-parser-input.md b/src/lang/zh-TW/markdown/ea-desktop-parser-input.md index f6cb853000..fc4cf45e9e 100644 --- a/src/lang/zh-TW/markdown/ea-desktop-parser-input.md +++ b/src/lang/zh-TW/markdown/ea-desktop-parser-input.md @@ -1,9 +1,9 @@ # EA Desktop Parser specific inputs -## EA Desktop Games Directory -By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. +## EA Games Directory Override +By default Steam ROM Manager assumes your `EA Desktop` games are installed at ``C:\Program Files\EA Games\`. This field allows you to change that to wherever your games are installed, e.g.``D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. This field allows you to change that to wherever your games are installed, e.g.D:\Games\EA Games`. -## Launch via EA Desktop +## Launch Games Via EA Desktop If enabled SRM will add a shortcut to `origin2://game/launch/?offerIds=${gameid}` instead of just the game's executable. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. This ensures the game launches via EA and will have access to online services. -`This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` +`This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on. This is required to add EA Play games. This is required to add EA Play games. EA Play games will not be detected if this is not toggled on.` diff --git a/src/lang/zh-TW/markdown/itch-io-parser-input.md b/src/lang/zh-TW/markdown/itch-io-parser-input.md index 3482f25b06..fabef17d1d 100644 --- a/src/lang/zh-TW/markdown/itch-io-parser-input.md +++ b/src/lang/zh-TW/markdown/itch-io-parser-input.md @@ -1,7 +1,7 @@ # itch.io Parser specific inputs ## itch.io AppData Path Override -By default Steam ROM Manager assumes your itch.io app data is located at `%APPDATA%\itch` on windows `$HOME/.config/itch` on linux and `$HOME/Library/Application Support/itch` on macos. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. +By default Steam ROM Manager assumes your itch.io app data is located at `%APPDATA%\itch` on windows `$HOME/.config/itch` on linux and `$HOME/Library/Application Support/itch` on macos. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. This field allows you to override that path if your itch.io user data is elsewhere. ## itch.io Windows-on-Linux Install Drive Redirect On Linux, Windows app locations are recorded with Windows paths, even if running via Proton/Wine. If set, this field replaces the root of game paths. On Linux, Windows app locations are recorded with Windows paths, even if running via Proton/Wine. If set, this field replaces the root of game paths. For example, this would change a `C:\\Path\To\Game.exe` to `\Path\To\Game.exe`. If set, this field replaces the root of game paths. On Linux, Windows app locations are recorded with Windows paths, even if running via Proton/Wine. If set, this field replaces the root of game paths. For example, this would change a `C:\\Path\To\Game.exe` to `\Path\To\Game.exe`. If set, this field replaces the root of game paths. For example, this would change a `C:\\Path\To\Game.exe` to `/Path/To/Game.exe`. diff --git a/src/lang/zh-TW/markdown/local-images.md b/src/lang/zh-TW/markdown/local-images.md index ec49fd667c..c8bb4895cb 100644 --- a/src/lang/zh-TW/markdown/local-images.md +++ b/src/lang/zh-TW/markdown/local-images.md @@ -1,12 +1,12 @@ # Local images (optional) `[supports variables]`{.noWrap} -Allows one to use images stored locally. Allows one to use images stored locally. A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. Allows one to use images stored locally. Allows one to use images stored locally. A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. +Allows one to use images stored locally. Allows one to use images stored locally. A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. Allows one to use images stored locally. Allows one to use images stored locally. A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. Allows one to use images stored locally. Allows one to use images stored locally. A [special glob input](#special-glob-input) string is used to retrieve images, so for example you might do `/path/to/heroes/${title}.@(png|jpg)`. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Backslashes can be used to escape characters, so that if your images live in `artwork [portraits]` you might do `/path/to/artwork \[portraits\]/${title}.@(png|jpg)`. A good idea is to set your artwork directory globally and then use the `${localimages}` dir environment variable in this field: `${localimagesdir}/emuname/heroes/${title}.@(png|jpg)` for example. Any variable you use in this field that contains special glob characters will have those characters escaped. ## Allowed image extensions -Only `JPEG`{.noWrap}, `JPG`{.noWrap}, `PNG`{.noWrap} and `TGA`{.noWrap} file extensions are supported. Even if parser finds files with other extensions, they are not included into the final list. Even if parser finds files with other extensions, they are not included into the final list. Even if parser finds files with other extensions, they are not included into the final list. +Only `JPEG`{.noWrap}, `JPG`{.noWrap}, `PNG`{.noWrap} and `TGA`{.noWrap} file extensions are supported. Even if parser finds files with other extensions, they are not included into the final list. Even if parser finds files with other extensions, they are not included into the final list. Even if parser finds files with other extensions, they are not included into the final list. Even if parser finds files with other extensions, they are not included into the final list. ## Can you move the directory of local images after saving app list? diff --git a/src/lang/zh-TW/markdown/parsers-list.md b/src/lang/zh-TW/markdown/parsers-list.md index 9a4a9b06f8..f2373740c7 100644 --- a/src/lang/zh-TW/markdown/parsers-list.md +++ b/src/lang/zh-TW/markdown/parsers-list.md @@ -1,3 +1,3 @@ # Parsers -In this page you can chose what systems you want to add to your Steam Library. In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** \ No newline at end of file +In this page you can chose what systems you want to add to your Steam Library. In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** In this page you can chose what systems you want to add to your Steam Library. Simply toggle them on or off, after that click on **Preview** and then on **Generate Apps** \ No newline at end of file diff --git a/src/lang/zh-TW/markdown/special-glob-input.md b/src/lang/zh-TW/markdown/special-glob-input.md index bd96e15366..717647bdc8 100644 --- a/src/lang/zh-TW/markdown/special-glob-input.md +++ b/src/lang/zh-TW/markdown/special-glob-input.md @@ -3,7 +3,7 @@ ## How does it work? Image paths are resolved in 4 step process: -1. String is evaluated to see if a glob based parser is used. String is evaluated to see if a glob based parser is used. Depending on the result, further parsing may continue with `2` glob sets. String is evaluated to see if a glob based parser is used. Depending on the result, further parsing may continue with `2` glob sets. +1. String is evaluated to see if a glob based parser is used. String is evaluated to see if a glob based parser is used. Depending on the result, further parsing may continue with `2` glob sets. String is evaluated to see if a glob based parser is used. Depending on the result, further parsing may continue with `2` glob sets. String is evaluated to see if a glob based parser is used. Depending on the result, further parsing may continue with `2` glob sets. 1. All provided variables are replaced with their corresponding values. 1. New string(s) is/are resolved against root directory (root directory is always a configuration's ROMs directory). 1. Final string(s) is/are passed to glob parser which then returns a list of available files. @@ -12,7 +12,7 @@ Image paths are resolved in 4 step process: ### Absolute paths -Let's say that the extracted title is `Metroid Fusion [USA]` and fuzzy title is `Metroid Fusion`. You can then construct an image path like this: You can then construct an image path like this: You can then construct an image path like this: +Let's say that the extracted title is `Metroid Fusion [USA]` and fuzzy title is `Metroid Fusion`. You can then construct an image path like this: You can then construct an image path like this: You can then construct an image path like this: You can then construct an image path like this: - `C:/path/to/images/${title}.*` - `C:/path/to/images/${fuzzyTitle}.*` @@ -24,7 +24,7 @@ which will be resolved to this: ### Relative paths -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: Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: +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: Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: Set up a relative path, using `${filePath}`{.noWrap} or `${dir}`{.noWrap} variables, for example: - `${filePath}/../../../path/to/images/${title}.*` - `${dir}/../../path/to/images/${title}.*` diff --git a/src/lang/zh-TW/markdown/steam-parser-input.md b/src/lang/zh-TW/markdown/steam-parser-input.md index 7edeb6bef5..9b84266e01 100644 --- a/src/lang/zh-TW/markdown/steam-parser-input.md +++ b/src/lang/zh-TW/markdown/steam-parser-input.md @@ -4,4 +4,4 @@ If enabled SRM will filter out any Steam applications that are not full games, such as demos and tools like `3DMark` or `Wallpaper Engine`. ## Find artwork for installed titles only -If enabled SRM will filter out any steam applications that are not currently installed locally. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. +If enabled SRM will filter out any steam applications that are not currently installed locally. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. If enabled SRM will filter out any steam applications that are not currently installed locally. If you install or uninstall a game, you need to restart Steam before the updated install list will be available to SRM. diff --git a/src/lang/zh-TW/markdown/user-accounts.md b/src/lang/zh-TW/markdown/user-accounts.md index 44eb256106..ccba506715 100644 --- a/src/lang/zh-TW/markdown/user-accounts.md +++ b/src/lang/zh-TW/markdown/user-accounts.md @@ -4,14 +4,14 @@ This field is used to limit SRM's effects to specific user accounts, and takes v `${...}` -This will limit SRM's effects to accounts `XXX` and `YYY` (you may specify as many accounts as you like). Here `XXX` and `YYY` stand in for either: Here `XXX` and `YYY` stand in for either: +This will limit SRM's effects to accounts `XXX` and `YYY` (you may specify as many accounts as you like). Here `XXX` and `YYY` stand in for either: Here `XXX` and `YYY` stand in for either: Here `XXX` and `YYY` stand in for either: -* The account id is the name of the account directory that appears in `/path/to/steam/userdata`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. +* The account id is the name of the account directory that appears in `/path/to/steam/userdata`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. For example, you would specify the account directory `userdata/56489124` like `${56489124}`. -* A `Steam Username` (the username you use to actually log in to Steam). A `Steam Username` (the username you use to actually log in to Steam). For example you would specify the users `Banana` and `Apple` like `${Banana}${Apple}`. +* A `Steam Username` (the username you use to actually log in to Steam). A `Steam Username` (the username you use to actually log in to Steam). For example you would specify the users `Banana` and `Apple` like `${Banana}${Apple}`. A `Steam Username` (the username you use to actually log in to Steam). For example you would specify the users `Banana` and `Apple` like `${Banana}${Apple}`. You can also mix and match: `${56489124}${Apple}` is fine. ## Warning -You **must** use the username you use to **log in** into Steam **if** [use account credentials](#what-does-use-account-credentials-do) is enabled: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. +You **must** use the username you use to **log in** into Steam **if** [use account credentials](#what-does-use-account-credentials-do) is enabled: If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. If you would like to use `Steam Usernames` here, go to `Steam > Settings > Account` and disable `Don't save account credentials on this computer`, then restart both Steam and SRM. diff --git a/src/lang/zh-TW/markdown/user-exceptions.md b/src/lang/zh-TW/markdown/user-exceptions.md index 3e90f7867f..979fda74da 100644 --- a/src/lang/zh-TW/markdown/user-exceptions.md +++ b/src/lang/zh-TW/markdown/user-exceptions.md @@ -3,39 +3,39 @@ This tool can be used to define per app exceptions that over rule the parsers. It should not be used to accomplish bulk tasks. For example, removing the colon character from titles can be accomplished via the title modifier `${/:/|${title}|}` and should not be done here. If a command line argument is common to every parsed app, then use the command line argument field - do not create a bunch of entries here! It should not be used to accomplish bulk tasks. For example, removing the colon character from titles can be accomplished via the title modifier `${/:/|${title}|}` and should not be done here. If a command line argument is common to every parsed app, then use the command line argument field - do not create a bunch of entries here! It should not be used to accomplish bulk tasks. For example, removing the colon character from titles can be accomplished via the title modifier `${/:/|${title}|}` and should not be done here. If a command line argument is common to every parsed app, then use the command line argument field - do not create a bunch of entries here! ## Extracted Title - *Mandatory* -The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. Once this is specified and the exception is saved, any game whose `Extracted Title` matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. Once this is specified and the exception is saved, any game whose `Extracted Title` matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). +The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. Once this is specified and the exception is saved, any game whose `Extracted Title` matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. Once this is specified and the exception is saved, any game whose `Extracted Title` matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. The only mandatory exception field is `Extracted Title`. Once this is specified and the exception is saved, any game whose `Extracted Title` matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). Once this is specified and the exception is saved, any game that matches will have its fields overridden by any non-blank exception fields (if left blank, the exception fields do nothing). The `Extracted Title` field matches in two ways: -* Based on the `Exception ID` (found by running test parser). Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. Based on the `Exception ID` (found by running test parser). Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. -* Based on the `Extracted Title` (found by running test parser). Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. +* Based on the `Exception ID` (found by running test parser). Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. Based on the `Exception ID` (found by running test parser). Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. Based on the `Exception ID` (found by running test parser). Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. Based on the `Exception ID` (found by running test parser). For example if the game were `Portal 1` and its `Exception ID` was `12345` then you might put `Portal 1 ${id:12345}`. If the `Exception ID` is present then it doesn't matter what label you put in front of it, but for readability and searchability it's nice to put the game's actual name in front of the `Exception ID`. +* Based on the `Extracted Title` (found by running test parser). Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. Based on the `Extracted Title` (found by running test parser). For example if the `Extracted Title` were `Portal 2` you would put `Portal 2`. -Thus you can either have an exception that applies to all games with the same name or an exception that applies only to an exact game (`Exception ID`s are unique). The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. Thus you can either have an exception that applies to all games with the same name or an exception that applies only to an exact game (`Exception ID`s are unique). The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. +Thus you can either have an exception that applies to all games with the same name or an exception that applies only to an exact game (`Exception ID`s are unique). The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. Thus you can either have an exception that applies to all games with the same name or an exception that applies only to an exact game (`Exception ID`s are unique). The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. Thus you can either have an exception that applies to all games with the same name or an exception that applies only to an exact game (`Exception ID`s are unique). The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. The reason for this is primarily backwards compatibility -- SRM formerly matched only on the `Extracted Title`. Exceptions generated from `Preview` will always be in the form `Extracted Title ${id:XXXXXX}`. ## New Display Title -This is the title that will display in Steam. It will not be used to search for images. It will not be used to search for images. It will not be used to search for images. It will not be used to search for images. +This is the title that will display in Steam. It will not be used to search for images. It will not be used to search for images. It will not be used to search for images. This is the title that will display in Steam. It will not be used to search for images. It will not be used to search for images. It will not be used to search for images. It will not be used to search for images. ## New Search Title -This is the title that will be used to search for images on [SteamGridDB](https://www.steamgriddb.com). There are two options for overriding it: There are two options for overriding it: There are two options for overriding it: There are two options for overriding it: +This is the title that will be used to search for images on [SteamGridDB](https://www.steamgriddb.com). There are two options for overriding it: There are two options for overriding it: There are two options for overriding it: There are two options for overriding it: There are two options for overriding it: * Specify the new search title as whatever text you want. -* Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. +* Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. Specify the exact game id to pull images from. Specify the exact game id to pull images from. For example to get images for the game [Flow](https://www.steamgriddb.com/game/5254019) which has SteamGridDB url `https://www.steamgriddb.com/game/5254019` you would put `${gameid:5254019}`. ## New Commandline Args -Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. +Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. Custom commandline arguments like `--fullscreen`, etc, that can be applied to a specific title. These only override the arguments field of the Steam shortcut and are never appended to the executable. ## Exclude Title -The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. +The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. The ability to exclude individual titles from being added to Steam. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. This allows you to keep titles that you don't want in Steam in the same folder as the rest of your games. ## Local Artwork Only Don't fetch artwork from remote providers (e.g. [steamgriddb](https://www.steamgriddb.com)). Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Don't fetch artwork from remote providers (e.g. [steamgriddb](https://www.steamgriddb.com)). Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game. Useful when SGDB is incorrectly matching the game or you just don't like any of the artwork available for it. ## Custom Variables -The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. +The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. The task of overriding specific titles can also be accomplished by manually editing the custom variables JSON file and using appropriate variables in the `Title Modifier` parser field. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten. It is recommended, however, that you use this tool instead since the custom variables JSON file will be updated over time and your edits may be overwritten.