Write each specialization value into packed backing storage and map entries to
that storage instead of leaving zero-initialized data.
Not used anywhere, but was still wrong.
Return complete VkSurfaceFormatKHR entries from the surface query, preserve
color spaces, and only choose an arbitrary format for the single
undefined-format case.
Create the buffer before allocation, intersect both memory-type masks, honor
size and dedicated requirements, and propagate bind failures.
Also require that the memory is coherent, because otherwise we'd have to resort
to architecture-specific cache flush methods. vkInvalidateMappedMemoryRanges()
is only valid on memory mapped by vkMapMemory().
Synchronize the actual offset and full pitched-row span written by image
readbacks, and invalidate the matching allocation range on the host.
Also fix the incorrect source stage.
After a badly-mannered arrival by a third party, I have decided to research on part of their suggested changes to find out whether or not was a reason to do so.
Here is a short summary of what I have found out:
- Usage of nonbreaking spaces -> Unlike the previously proposed changes, NBSPs are, in fact, recommended by Microsoft in the official public Style Guide for EU Spanish to avoid separation of units and the numbers that go with them.
- Usage of quotation marks -> Microsoft's Style Guide, on the other hand, does recommend using doubles (“”) instead of chevrons («»), so all chevrons have been replaced with simple doubles ("). Many other places (UIs from Sony, Nintendo...) do also use doubles in UIs.
- NOTE: I have also replaced cases where singles are used ('%1'), but Microsoft doesn't seem to contain info regarding the stacking of quotation marks (where RAE would say that singles go inside doubles). This change might need to be reverted.
- Usage of quotation marks to signal loanwords -> While RAE's rules do explicitly say that loanwords must be highlighted somehow (either with chevrons or italic text), multiple UIs researched (NVidia, ATI, various games from the 2010's) do not do this sort of highlighting at all. All quotation marks that were used to highlight loanwords just for being loanwords have been removed.
- Consistency pass of expressions like "If checked"/"If unchecked"/"When enabled"/"When disabled"/"When this option is chosen" -> "Al activar esta opción,"/"Al desactivar esta opción,"
- "Enable"/"Disable" from "habilitar"/"deshabilitar" to "activar"/"desactivar": This is a bit of a potato, potato situation, a preferential change. Microsoft has kept using "habilitar"/"deshabilitar" for many, many years, but it is also true that a non-minor number of references researched do use to "activar"/"desactivar" (it's hard to find examples for Enable/Disable, as many of the UIs I've checked are more of using ON/OFF switches, which are translated to SÍ/NO (YES/NO) for simplicity and less gendering issues). The main reason I was keeping the old ways was to keep elements from those translators who came before me, so it was also a preferential change to keep them as before. Switching to "activar"/"desactivar" and unified all instances.
- Minor pass to keep consistency with the "save state" translation as "guardado rápido".
- RetroAchievements: imported some approved RA translations such as casual mode -> modo casual, set -> set, subset -> subset.
- Other minor translation changes.