Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I understood you correctly you want to verify that every localizable text is indeed in fact localizable and not burned in the code. To do this you should not be using a real culture (Spanish), instead you should create resources for a fake unsupported culture and provide an automatic translation for every localizable resource entry available in the default resources.</p> <p>For example, if you have a default resource containing:</p> <ul> <li>Entry1: This is a test!</li> </ul> <p>you should create a resource in your fake culture containing:</p> <ul> <li>Entry1: Th1s 1s @ t€st!</li> </ul> <p>You could even (and should) perform the creation of the fake resources automatically using a simple character mapping. This way, when you set the application to use your custom fake culture you know that every entry has a translation so you can find harcoded text. <strong>This strategy is used by Windows</strong> and is known as <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd319106%28v=vs.85%29.aspx" rel="nofollow">pseudo-locales</a>. The use of pseudo translated strings makes it possible do development using the fake culture because the text is still readable and this <strong>improves your probability of finding hardcoded text</strong>.</p> <p>Windows supports pseudo-locales since Windows Vista and Windows 2008 R2, so if your build and testing environment uses these operating systems you can associate your fake culture to one of these pseudo locales (for example <code>qps-ploc</code>). If you have unsupported operating systems just associate your fake resources to a real culture that you probably will never be supporting or just create your own culture.</p> <p>Also note that even in a supported operating system, Visual Studio will not create satellite assemblies for these pseudo-locales unless you <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd374118%28v=vs.85%29.aspx" rel="nofollow">enable them on the registry</a>.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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