String Ingestion Warnings Explained
String ingestion warnings are flags raised when Smartling ingests a string that appears to have a possible problem. The string will still be ingested. This Strings View filter allows you to view strings that might require further attention.
|High character to word ratio||
The ratio of character to words is high.
|Commonly seen when JSON or XML files are uploaded but the translate_paths directive is not well formed. For example strings that are actually keys/names or untranslatable metadata are ingested (e.g. manual_edit_address_state_selection). See also String is wrong language.|
|String has HTML blocks||The string has HTML block elements.||This might indicate an incomplete integration. This is most commonly seen when HTML documents are captured as a single string from a key/value resource file and Smartling HTML formatting is not applied to the string. Check the file format for support of the string_format_paths directive.|
|String has no words||
The string has no words.
|This warning occurs when strings have zero words, which is most commonly with strings that are just a placeholder or just HTML markup with no value in the elements. The string should most likely be excluded from translation in Smartling since translators will not be able to do anything with such strings. If you need attributes of HTML elements translated, you should consider extracting those attribute values as separate strings, ingesting them, and then reconstituting the localized/translated version in your application at run time or when preparing fully translated resource files.|
|String has nonintegrated placeholder||
The string contains what looks like a placeholder, but it hasn't been captured as a placeholder.
This might indicate an incomplete integration. For the best translation results, strings that have placeholders should be uploaded with those placeholders properly integrated. See Placeholders in Files for more.
String is very long
|Very long string (high character count).||This might indicate an incomplete integration. This is most commonly seen when HTML documents are captured as a single string from a key/value resource file and Smartling HTML formatting is not applied to the string. Check the file format for support of the string_format_paths directive|
|String is wrong language||The project's source language is different from this string's apparent language.||This flag occurs when content is uploaded with a different language than that of the source language in the project. This could mean that the content was uploaded to the wrong project or you need a new project with a new source language. If you have content sources with mixed languages you may need to re-evaluate your solution and split source content into multiple projects. It is bad for your translation memory to translate content when it's not actually the same language as the project is configured to be.|
|String looks like a URL||
The entire string looks like a URL or email address.
|For GDN projects please see URL Translation feature.
For other project types, strings with this warning should be carefully reviewed and possibly excluded.