StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIdentify unlocalized text
text
Body
copied!<p>In ASP.NET, an application can be localized using resource files. Resource files hold different translations. For example, one might have an English resource file and a Spanish resource file. When resource files are used, an attribute can be applied to controls on a web page to automatically populate that control with values from a resource file. Alternatively, the values can be programmatically loaded from a resource file and assigned to a control's property.</p> <p>ASP.NET uses a fallback mechanism for loading translations. It tries to find the resource file that is most similar to the current user's culture. If the current user's culture is Spanish, ASP.NET tries to load the appropriate resource from the Spanish resource file. If the Spanish resource is not available, it falls back to a default resource file. Because of this behavior, text for a Spanish user may be shown in the default language for two reasons:</p> <ol> <li>No Spanish translation is available. (The translators haven't provided a translation for this item yet.)</li> <li>The text is not localized. (This may be the result of plain text appearing in the page or the message being hard-coded somewhere.)</li> </ol> <p>If text appears in the default language, I want to know whether it was because of reason 1 or because of reason 2.</p> <p>For every missing translation, I could insert some kind of placeholder text in a resource file. However, this means that I am throwing away the fallback mechanism. Even worse, if placeholder text accidentally makes it through to production, it looks much worse than showing the default text.</p> <p>Does anyone have any suggestions (or solutions) for determining which of these two conditions is the reason for default text appearing during manual testing?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload