Transvision Beta

Use the Menu tab in the right top corner to select a different view.

Search will be performed on: Strings.

Repository

Default

Source Locale

Default

Target Locale

Default

Search in

Default

Advanced Search options Case Sensitive Each Word Entire String Entire Words

Show all results security toolkit

Displaying 2 results for the string encode in sco:

Entity	sco	en-US
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_FAILED_TO_ENCODE_DATA	sco Didnae encode data wi ASN1 encoder <source> Translate with: Google BING	en-US Failed to encode data with ASN1 encoder <source>
Entity # all locales toolkit • toolkit • neterror • nsserrors.ftl sec-error-failed-to-encode-data	sco Didnae encode data wi ASN1 encoder <source> Translate with: Google BING	en-US Failed to encode data with ASN1 encoder <source>

Entity	sco	en-US
Entity # all locales dom • chrome • layout • HtmlForm.properties CannotEncodeAllUnicode	sco Warning: Source string is missing <source>	en-US A form was submitted in the %S encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element. <source> Large string?
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_FAILED_TO_ENCODE_DATA	sco Didnae encode data wi ASN1 encoder <source> Translate with: Google BING	en-US Failed to encode data with ASN1 encoder <source>
Entity # all locales toolkit • toolkit • neterror • nsserrors.ftl sec-error-failed-to-encode-data	sco Didnae encode data wi ASN1 encoder <source> Translate with: Google BING	en-US Failed to encode data with ASN1 encoder <source>

APIThese results are also available as an API request to search in sco or en-US.
Learn more about the Transvision API.