You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree:
e980e90d6e
00336
2ndAdjustmentVulkan
2ndgpuopts
Compatlist
Kernel
Update-some-barriers-test
astc_optimization1
astc_optimizations
atomicops-mxwell
auto-updater
bcn-ternary-soft
bump-httplib-minver
camillelavey-patch-1
civa
cyber/async-gpu-android
descriptor
descriptor_pool_opt
descriptor_set
discfix
dmnt2
dravee/remove-async
dynarmic
dynarmic-ppc64
eden-orbis-ps4
eds-true-adreno-fixes
eds-true-adreno-fixes-pre-0.1.0
eds_changes1
eds_changes_phasewise
feat/22.0.0
feat/android_kotlin_compose
feat/game_override
feat/new_lang
ffmpeg-cross-compile
fix-grid-autoalign
fix/discord-rpc
fix/socket
flatopsfixes23485
fs-try
gpuopts
interval-zero
kosmic_krisp
kosmickrisp
lanobu
lines
liz-crash-dumps-solaris
liz-dynarmic-macos-fbsd-port
liz-get-rid-of-mcl-intrusive-list
liz-heaptrack-fix
lizize/fixcrashwehenimagesizeexceed
lizzie/adreno5-mali-driver-fix
lizzie/anv-cached-mesa-hack
lizzie/astc-mp4-improv
lizzie/attempt2-better-list-dynarmic
lizzie/audio-remove-recursive-lock
lizzie/batched-draws-wip
lizzie/bsdsockets-mod-fix
lizzie/correcter-convert-abgr8-srgb-d24s8
lizzie/draw-state-inline
lizzie/dynarmic-faster-xbyak
lizzie/dynarmic-next-2026-03-26
lizzie/edit-handheld-mode
lizzie/evil-f32-u32-format-fix
lizzie/fix-dragonslayer-armnce
lizzie/fix-my-fuckup-with-vic
lizzie/fix-nvmap-handles
lizzie/fix-nvmap-handles-but-evil
lizzie/fix-rw-garten
lizzie/fix-vic-msvc-attempt-2
lizzie/fs-msvc-succks
lizzie/gutter-sw-blitter
lizzie/hleinlineremoveredundant
lizzie/inline-123
lizzie/inline-cmif-request
lizzie/inline-dynarmic-spooky
lizzie/invert-gyro
lizzie/ios-port-sud
lizzie/jit-addresschecks
lizzie/lrunsdfkdsjfl
lizzie/ltofix123
lizzie/macos-fix
lizzie/macos-network-ifaces
lizzie/macos-vk-metal-fix-stype
lizzie/mark-bl-dynarmic
lizzie/maxwell-dumb-tools
lizzie/mlp223
lizzie/multicore-macos-fix1
lizzie/nce-invalidate-split
lizzie/nce-port1123
lizzie/noexcept-dynarmic
lizzie/nuke-cubeb
lizzie/product-model-wawa
lizzie/qt-fix-user-dialogue
lizzie/rasterizer-recursive-mutex-not
lizzie/readonly-listicons
lizzie/remove-disassembler-dynarmic
lizzie/remove-mlp-2-level
lizzie/restore-fcsm
lizzie/settings-blocked-domains
lizzie/sgsr
lizzie/sm-AtmosphereHasService
lizzie/splay
lizzie/spscs-mpscs-queue
lizzie/stable-shader-pools
lizzie/stupid-socket-bullshit
lizzie/texture-pass-revert-1
lizzie/try-fix-win11-crash-fuck
lizzie/ulaunch-attempt1
lizzie/unaligned-attempt-2
lizzie/unity-build
lizzie/update-faq-link-wwa
lizzie/vids-ratatata
lizzie/vkexperiments1-highp-fucked
lizzie/wstring-uni-123
lizzie/xbyak-unor-mapfix-with-boost
lizzie/xcode-evil-shit-123
lock-term-1
macroify-surface-stuffs
master
memory_changes
mmap-fixews
msvc
mutliplayer-filter-better1
n64
nce_cpp
pipelinederivative
qcomopts2
queries
querybugfix
refactoreds2
release-early-fences
release/0.0.3
release/0.0.4
release/0.1.0
revert-2695
revert-noinline
revert-xbyak
revertrevert
sgsrtry
showcase
showcase2
sjkdbsdfjkbsdf-2834
spvopts
sured-revert
techno48473719
test-revert-gpu-optim
test2
tex_opt
texture_cache
true-eds
true-eds-graphics
true-eds-pre-0.0.1
uma
update-deps-040626
vk-fix-oom-force-maller-buffers
vk-symph
vkexperiments1
vkfixes1
vuid00336_1
vuid02999
vuid04553
vulkan-thingy
vulkanasync
woa-turnip-expr
workgroup
xbzk-dma-pusher-step-redesign
xbzk-saf-recursive-write-with-permission-request
xbzk/background-support
xbzk/bindless-textures-support
xbzk/dma-step-ondemand-flush
xbzk/flicker-fix
xbzk/input-delay-fix
xbzk/press-back-again-issue-fix
xbzk/settings-fragment-rework
xbzk/unreal-unsafe-junk-guards
xbzk/vulkan-vuid-goodies-pack
0.0.0
0.0.1-pre-alpha
0.0.2-pre-alpha
test-tag1
test-tag2
v0.0.3
v0.0.3-rc1
v0.0.3-rc2
v0.0.3-rc3
v0.0.3.git
v0.0.4
v0.0.4-rc1
v0.0.4-rc2
v0.0.4-rc2.test
v0.0.4-rc2.test2
v0.0.4-rc3
v0.0.4-rc3.test1
v0.0.4-rc3.test2
v0.0.4.test
v0.1.0
v0.1.0-rc1
v0.1.1
v0.2.0-rc1
v0.2.0-rc2
${ noResults }
Qt provides an overload of tr() that operates on quantities in relation to pluralization. This also allows the translation to adapt based on the target language rules better. For example, the previous code would result in an incorrect translation for the French language (which doesn't use the pluralized version of "result" in the case of a total of zero. While in English it's correct to use the pluralized version of "result", that is, "results" --- For example: English: "0 results" French: "0 résultat" (uses the singular form) In French, the noun being counted is singular if the quantity is 0 or 1. In English, on the other hand, if the noun being counted has a quantity of 0 or N > 1, then the noun is pluralized. --- For another example in a language that has different counting methods than the above, consider English and Irish. Irish has a special form of of a grammatical number called a dual. Which alters how a word is written when N of something is 2. This won't appear in this case with a direct number "2", but it would change if we ever used "Two" to refer to two of something. For example: English: "Zero results" Irish: "Toradh ar bith" English: "One result" Irish: "Toradh amháin" English: "Two results" Irish: "Dhá thorthaí" <- Dual case Which is an important distinction to make between singular and plural, because in other situations, "two" on its own would be written as "dó" in Irish. There's also a few other cases where the order the words are placed *and* whether or not the plural or singular variant of the word is used *and* whether or not the word is placed after or between a set of numbers can vary. Counting in Irish also differs depending on whether or not you're counting things (like above) or counting people, in which case an entirely different set of numbers are used. It's not important for this case, but it's provided as an example as to why one should never assume the placement of values in text will be like that of English or other languages. Some languages have very different ways to represent counting, and breaking up the translated string like this isn't advisable because it makes it extremely difficult to get right depending on what language a translator is translating text into due to the ambiguity of the strings being presented for translation. In this case a translator would see three fragmented strings on Transifex (and not necessarily grouped beside one another, but even then, it would still be annoying to decipher): - "of" - "result" - "results" There is no way a translator is going to know what those sets of words are actually used for unless they look at the code to see what is being done with them (which they shouldn't have to do). |
8 years ago | |
|---|---|---|
| .. | ||
| default | Add Dark theme, Icon theming | 8 years ago |
| qdarkstyle | Port #3769 from Citra: "Update Dark theme to latest version" | 8 years ago |