Difference between revisions of "InContext Capture Users Guide"
(→Browse to a Lingoport Instrumented Application) |
|||
| Line 1: | Line 1: | ||
| + | Use three methods to capture context |
||
| + | * For a Web application, use the Chrome Extension |
||
| + | * For Figma, use the Figma plugin |
||
| + | * For others, associate screenshots to strings |
||
| + | |||
| + | = Web Application: Use the Chrome Extension = |
||
== Browse to the Application in Context Locale == |
== Browse to the Application in Context Locale == |
||
Navigate to your internationalized application, display the application in the context locale. |
Navigate to your internationalized application, display the application in the context locale. |
||
Revision as of 20:45, 2 June 2025
Use three methods to capture context
- For a Web application, use the Chrome Extension
- For Figma, use the Figma plugin
- For others, associate screenshots to strings
Web Application: Use the Chrome Extension
Browse to the Application in Context Locale
Navigate to your internationalized application, display the application in the context locale.
Capture
Click on InContext Capture icon to capture the current page and send to InContext server
There are two options "Send page to InContext Server" and "Send selection to InContext Server", you can send the whole page or part of the page by selecting a different option.
- If the current page is not instrumented, the status will change to
, and an error message will pop-up."IncontextCapture error: File does not contain valid LRM keys (RestFormApi)" - If the current page is instrumented, the status will change to
, and capture page will be sent to InContext server
