String Ingestion Warnings Explained 

This warning is 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.

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.
See below for the specific HTML blocks that are checked by this warning:
<div>
<h>
<form>
<ul>
<li>
<ol>
<dl>
<dt>
<dd>
<nav>
<fieldset>
<canvas>
<video>
<p>
<pre>
<header>
<footer>
<section>
<aside>
<address>
<article>
<blockquote>
<figcaption>
<noscript>
<figure>
<table>
<tfoor>
<main>

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.

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.
Specifically, this warning checks for text following one of these patterns:
%(anyText)s
{{anyText}}
${anyText}
%#$s (where # is any digit)
%#$d (where # is any digit)

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

This flag occurs when strings are 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.

For GDN projects, read our documentation on URL Translation feature.

Depending on your source content, this may be a common occurrence, and it may not be an area of concern. This particular flag is useful in case you do not want to process number-only or code-like strings through a translation workflow. An example would be a string that is only the number 2023, or a string with an expression such as K12.