- Moved BSV initialization before autoload code
- Don't trigger autoload code if there is bsv movie state
Open question: What's the difference between entry state and autoload
state? Should BSV recording use the entry state even if playback does
not?
Co-authored-by: Joseph C. Osborn <jcoa2018@pomona.edu>
After PR libretro#14821 , the
contents of msg_hash_xx.c files are present in the normal translation
workflow. These files can and should be reduced to stub versions,
since new translations won't take effect otherwise.
One file missed from previous commit and stubbed completely.
Other files trimmed: only translated entries are kept, original English
entries and very partially translated items are removed.
eb9b273298 Merge pull request #2094 from LibretroAdmin/main
5029e30f0a (spirv_glsl.cpp) Fix error: no matching function for call to 'max(uint32_t&, unsigned int)'
git-subtree-dir: deps/SPIRV-Cross
git-subtree-split: eb9b2732982b8eea3395216be825a74dd84fe4be
* Don't start video recording when BSV recording starts
* Don't double-record inputs in BSV recording
- Will this work properly with the part of input handling outside of
input_state_wrap? Who knows?
Co-authored-by: Joseph C. Osborn <jcoa2018@pomona.edu>
After PR libretro#14821 , the
contents of msg_hash_xx.c files are present in the normal translation
workflow. These files can and should be reduced to stub versions,
since new translations won't take effect otherwise.
These languages had the original English text as help at the time of
commit, so it is safe to assume no translation content is lost.
Some content is preserved until Crowdin translation catches up.
After PR https://github.com/libretro/RetroArch/pull/14821 , the
contents of msg_hash_xx.c files are present in the normal translation
workflow. These files can and should be reduced to stub versions,
since new translations won't take effect otherwise.
These languages have reached 100% completeness on Crowdin at the
time of commit, so it is safe to assume no translation content is
lost.
