You can access your translation history in the Saved area of the translator, under History. DeepL has no access to your translation history. The texts in your translation history are stored locally, on your device only. This means that your translations will be saved automatically every 10 seconds. We’ll enable the translation history feature for you by default. It might not yet be available for all users. Please note that this is a new feature that is being released gradually to all desktop apps. More information about the translation history feature on the mobile apps can be found in this article. It's not yet available on the web translator. This feature is available on Mac and Windows, as well as on the DeepL mobile apps for iOS and Android. With this feature enabled, your translations will be stored temporarily. Yes, the translation history feature makes it possible for both free users and Pro subscribers to have their past translations saved, so they can view, edit, and reuse them later. For other examples and for help in viewing the source code, see Samples.Can I save and access my previous translations? See also keyword.įor examples of using this API, see the history sample directory and the history API test directory. See also keyword_generated.Ĭorresponds to a visit generated for a keyword. The URL was generated from a replaceable keyword other than the default search provider. Session restore and Reopen closed tab use this transition type, too. The user reloaded the page, either by clicking the reload button or by pressing Enter in the address bar. Note that in some situations-such as when a form uses script to submit contents-submitting a form does not result in this transition type. The user filled out values in a form and submitted it. The page was specified in the command line or is the start page. These are not quite the same as typed navigations because the user didn't type or see the destination URL. For example, a match might have the URL of a Google search result page, but it might appear to the user as "Search Google for. The user got to this page by typing in the address bar and selecting an entry that did not look like a URL. An explicitly requested frame is probably more important than an automatically loaded frame because the user probably cares about the fact that the requested frame was loaded. The user may not even realize the content in these pages is a separate frame, and so may not care about the URL (see also manual_subframe).įor subframe navigations that are explicitly requested by the user and generate new navigation entries in the back/forward list. For example, if a page consists of several frames containing ads, those ad URLs have this transition type. This is any content that is automatically loaded in a non-top-level frame. The user got to this page through a suggestion in the UI-for example, through a menu item. See also generated, which is used for cases where the user selected a choice that didn't look at all like a URL. Also used for other explicit navigation actions. The user got this page by typing the URL in the address bar. The user got to this page by clicking a link on another page.
0 Comments
Leave a Reply. |