summaryrefslogtreecommitdiff
path: root/Source/Core/InputCommon/InputConfig.cpp
diff options
context:
space:
mode:
authorJosJuice <josjuice@gmail.com>2020-11-16 13:28:11 +0100
committerJosJuice <josjuice@gmail.com>2020-11-16 13:28:11 +0100
commit9a01c3fb9f137b666f27fcf8f1bfc3ac9c42346b (patch)
treedd94fa50b0a9c3fad783020c129ef8a8247b2bb0 /Source/Core/InputCommon/InputConfig.cpp
parent8a621c2d5e7722de5148a0a40d4072445cffb361 (diff)
Use positional arguments in all translatable fmt strings
We want to use positional arguments in translatable strings that have more than one argument so that translators can change the order of them, but the question is: Should we also use positional arguments in translatable strings with only one argument? I think it makes most sense that way, partially so that translators don't even have to be aware of the non-positional syntax and partially because "translatable strings use positional arguments" is an easier rule for us to remember than "transitional strings which have more than one argument use positional arguments". But let me know if you have a different opinion.
Diffstat (limited to 'Source/Core/InputCommon/InputConfig.cpp')
-rw-r--r--Source/Core/InputCommon/InputConfig.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/Source/Core/InputCommon/InputConfig.cpp b/Source/Core/InputCommon/InputConfig.cpp
index b531e56003..03d2874332 100644
--- a/Source/Core/InputCommon/InputConfig.cpp
+++ b/Source/Core/InputCommon/InputConfig.cpp
@@ -73,7 +73,7 @@ bool InputConfig::LoadConfig(bool isGC)
if (profiles.empty())
{
// TODO: PanicAlert shouldn't be used for this.
- PanicAlertFmtT("No profiles found for game setting '{}'", profile_setting);
+ PanicAlertFmtT("No profiles found for game setting '{0}'", profile_setting);
continue;
}