Read the language you need by function, not only by name
Updated
Seeing a language name on a store page does not tell you that every part of a game uses it. Decide whether you need interface text, subtitles, spoken audio or a particular combination. Then compare that requirement with the game's support information and verify it in the intended setting. The store display language and Steam's interface are different observations from the game's own language.
State the combination you want
Suppose you want readable menus and subtitles in a preferred language while keeping spoken dialogue in another. That is a combination of functions, not a single language switch. Identify each desired function before comparing the support table. If your requirement is subtitles, an audio-only indication would not answer it; if your requirement is spoken dialogue, translated menus would not be enough.
Use the exact title and edition you intend to play. A separate demo, another platform release or community translation is not automatically evidence for that installation. Keep those differences visible rather than merging everything described as the same game into one support claim. This makes the later settings check about the product you actually use.
Read each supported function separately
Compare the stated interface, subtitle and audio support for the required language. If information is absent or ambiguous, treat that function as unconfirmed instead of inferring full support from the language's presence elsewhere. An explanatory note may change the scope of a table entry, so include applicable notes in your comparison.
In the hypothetical requirement, text support can be confirmed while audio in that language is not. That may still fit a reader who deliberately wants another audio language, but it does not prove the game allows that combination. The support table and the available combination of settings answer related, separate questions.
Separate Steam, store and game choices
Steam's language guidance distinguishes client language from individual-game language, and notes that third-party games can have their own settings. Do not use a translated store page or client interface as proof of the selected game's output. Follow the current applicable per-game or in-game instructions instead of assuming that changing one display changes every other layer.
Steam also distinguishes platform-supported languages from languages developers can declare for games. Therefore, absence from the client selector alone does not disprove a game's declared support. Conversely, the platform supporting a language does not establish that a particular title includes it. Check the game-specific evidence for your desired function.
Check delivery and combination restrictions
A supported language choice can require additional files according to Steam's guidance. Observe any relevant download or publisher instruction before judging an unchanged screen. Do not invent a fixed language-pack size or assume all language changes need a separate download. The appropriate delivery check depends on the title and its implementation.
Look for the game's documented controls for text and audio. If it offers a combined choice only, do not claim that separate store support entries provide independent switches. If it supports the desired split, select it using the supported interface and note any required restart. A configuration-file workaround from an unrelated title is not evidence that this combination is supported here.
Test the functions rather than a single menu
Choose a suitable scene that exercises the required functions without risking important progress. Inspect an actual menu for interface text, enable and observe subtitles where supported, and listen to the intended dialogue for audio. A translated title screen alone cannot confirm the language of later dialogue or subtitles.
Suppose the menus match the plan but dialogue does not. Preserve the successful menu observation and review the audio requirement and selected setting. Do not describe the entire language setup as either supported or broken when only one function differs. If subtitles are absent because they are disabled, that is also a different question from missing translation.
Report unsupported, unresolved and observed states
Record which function is explicitly supported, which setting you chose and what you observed in the test. If a required function is not declared, label the requirement unmet or unconfirmed as appropriate. If support is declared but the output differs after the applicable setup, describe that discrepancy to the publisher without inventing the cause.
Use the result for the checked edition, version and combination. An update or another release can change the applicable information. The useful conclusion is that the desired functions were observed under the tested choices, not that a language name somewhere guarantees a fully localized experience.
Define the needed text and audio functions, read their support separately, follow the game's actual selection and delivery process, then test each function. Keep client language, store language and game output apart. That gives you a clearer decision than judging support from a single language name or translated menu.