InContext Capture Users Guide: Difference between revisions

From Lingoport Wiki
Jump to navigation Jump to search
No edit summary
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Browse to a Lingoport Instrumented Application ==
Use three methods to capture context
Navigate to your internationalized application with resource instrumented with Lingoport, where the resources (strings) have been instrumented
* For a Web application, use the Chrome Extension
* For Figma, use the Figma plugin
* For others, associate screenshots to strings
 
Make sure the configuration is complete. For example,
* [[InContext_Capture_Installation | Chrome Extension Installation ]]
 
 
= 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 ==
== Capture ==
Click on InContext Capture icon to capture the current page and send to InContext server
Click on InContext Capture icon to capture the current page and send to InContext server
* If the current page is not instrumented, the status will change to [[File:In-context-status-error.png|25px]], and an error message will pop-up."IncontextCapture error: File does not contain valid LRM keys (RestFormApi)"
 
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 [[File:In-context-status-error.png|25px]], and an error message will pop-up.
** <code>IncontextCapture error: File does not contain valid LRM keys (RestFormApi)</code>
* If the current page is instrumented, the status will change to [[File:In-context-status-success.png|25px]], and capture page will be sent to InContext server
* If the current page is instrumented, the status will change to [[File:In-context-status-success.png|25px]], and capture page will be sent to InContext server


== Auto-capture this tab==
= Figma: Use the Figma Plugin =
* Right-click on InContext Capture icon and select "Auto-capture this tab"
 
* Wait for a second to let InContext Capture finish its sending
* See: [[ Figma_API_Project| Figma Plugin ]]
* When the status changes to green check [[File:In-context-status-success.png|25px]], you could navigate to next page for auto-capture
 
* When you finish your capture work, right-click on InContext Capture icon and select "Disable Auto-capture"
= Screenshot Association =
Note: If you navigate to a page without instrumented while Auto-capture turns on, the status will change to [[File:In-context-status-error.png|25px]], and an error message will pop-up. If you would like to continue Auto-capture, you could close the pop-up and navigate to an instrumented page, the Auto-capture will still work.
 
* See: [[Individual_Project_Tasks#Add_Screenshots | Screenshots ]]

Latest revision as of 20:57, 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

Make sure the configuration is complete. For example,


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

Figma: Use the Figma Plugin

Screenshot Association