JosJuice 9a01c3fb9f 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.		2020-11-16 13:28:11 +01:00
..
Android	Android: Add null check for InputOverlay	2020-11-11 10:38:49 +01:00
Core	Use positional arguments in all translatable fmt strings	2020-11-16 13:28:11 +01:00
DSPSpy	DSPSpy: sync Makefile with current devkitPro template	2020-06-08 04:21:41 +01:00
DSPTool	msbuild: re-enable standalone vcxproj processing	2020-08-22 16:17:50 -07:00
PCH	Merge pull request #9091 from shuffle2/pch	2020-10-29 21:29:28 +01:00
UnitTests	x64Emitter: Check end of allocated space when emitting code.	2020-08-24 19:31:32 +02:00
VSProps	DolphinQt: Stop using qtmain	2020-09-21 17:27:10 +02:00
.clang-format
CMakeLists.txt	Android: Add content provider support to File::IOFile	2020-09-16 18:38:53 +02:00
dolphin-emu.sln	Externals: Add zstd	2020-05-13 20:53:10 +02:00