Scanning is a part of the localizaton process where Soluling reads the items of the project (i.e., your original file and database) to extract data to be localized. When you create a new project, Soluling scans the items for the first time. The scan process populates the project tree, and you can see all the nodes of the project in the project tree and the rows of the in the editing grid.
If you modify your original file or database, then your Soluling project becomes out of sync. To make it in sync, you must rescan the project.
Now Soluling rereads the items to find any new or change items. As a result an item or row in the project may change its state. The following table contains possible effects:
|New||Node or row is new. It was added during the scan process. A yellow dot is shown next to the node in the project tree or at the beginning of the row.|
|In use||Node or rows has not been changed. It was there previously and was still found during the scan process. No visual indicator is shown.|
|Value changed||The original value of the string changed. A red dot is shown at the beginning of the row. Also, every existing translation of the row has been invalidated (marked with a red dot).|
|Context changed||The context of the original strings changed. A gray dot is shown at the beginning of the row.|
|Unused||The node or row no longer exists. A blue dot is shown next to the node in the project tree or at the beginning of the row.|
Use the filter after scan, if you want to see the new and changed items.