Fluent 1.0: a localization system for natural-sounding translations
One thing that I&#x27;ve always struggled w.r.t i18n is having to split messages up into often times less coherent chunks in order to add things like links or tooltips or styling elements in the middle of the text, which makes it more difficult to localize messages as a holistic piece independent of the source language.<p>For a slightly contrived example to demonstrate this, let&#x27;s say you have a string like this:<p>&quot;Please click here 7 times to confirm&quot;<p>Where you want to make the &quot;click here 7 times&quot; look like a link by wrapping it in a &lt;a&gt; tag, or just styled differently using a styled &lt;span&gt;.<p>Using something like react-intl, which is what I&#x27;ve used in the past, you&#x27;d have to do something like this:<p><pre><code>  &lt;FormattedMessage
    id=&quot;confirm&quot;
    defaultMessage={`Please { confirmLink } to confirm`}
    values={{
      confirmLink: 
        &lt;a&gt;
          &lt;FormattedMessage 
            id=&quot;confirm-link&quot;
            defaultMessage={`click here {clickCount, number} {clickCount, plural,
              one {time}
              other {times}
            }`}
            values={{ clickCount: 7 }}
          &#x2F;&gt;
        &lt;&#x2F;a&gt;
    }}
  &#x2F;&gt;
</code></pre>
If then some language happens to require a completely different sentence structure that changes the ordering such that the &quot;to confirm&quot; part needs to be interleaved somewhere in the middle of the &quot;click here 7 times&quot; message to sound fluent, this would not be able to accommodate that.<p>I&#x27;m wondering how people generally deal with this, in React and elsewhere.