Skip to content

07. Scanning the Target Project

tetherscript edited this page Feb 16, 2025 · 5 revisions

Scanning searches .xaml files used by the target project for any elements that have a x:Uid, are defined in XamlElements.json, and have a valid Hint Token.

It combines this with the items in TLocalizedGets.json and Specials.json and updates the target\Strings\en-US\Resources.resw. You put a blank Resources.resw there earlier, and its data section has now been replaced with the scan results. This .resw is the "truth" for what needs to be translated later. In that Resources.resw file, you'll see that the hint token (@, @@, !, !!) have been placed in the comments field. Don't edit this file.

No other '\Strings???\Resources.resw' files have been touched. That will happen when you translate.

The contents of DetectedXamlElements.json have also been replaced. This file is for your troubleshooting purposes only. It is not used by the Translate functionality. It's a good place to look if one of your xaml elements has not been translated. If it isn't in this file, it wasn't detected during the scan.

Note

Scanning is the greatest timesaver over other translation methods. You don't need to manually add items the the .resw files. That is huge.

Summary

When a scan is complete, you have found the things that need to be translated, but you have not actually translated anything yet.

Here's what scanning the sample app Sample-Packaged looks like.

scan1

Clone this wiki locally