<p></p>
<p dir="auto">I spotted this in another repository, and it applies to us too:</p>
<blockquote>
<p dir="auto"><code class="notranslate">one</code> is used for numbers other than 1.<br>
A common mistake is to think that "one" is only for only the number 1.<br>
Instead, "one" is a category for any number that behaves like 1.<br>
So in some languages, for example, one → numbers that end in "1" (like 1, 21, 151) but that don't end in 11 (like 11, 111, 10311).</p>
<ul dir="auto">
<li><a href="http://cldr.unicode.org/index/cldr-spec/plural-rules" rel="nofollow">http://cldr.unicode.org/index/cldr-spec/plural-rules</a></li>
</ul>
</blockquote>
<p dir="auto">We have a mixture of examples in en.yml, e.g.</p>
<div class="highlight highlight-source-yaml" dir="auto"><pre class="notranslate"><span class="pl-ent">one</span>: <span class="pl-s">1 way</span>
<span class="pl-ent">one</span>: <span class="pl-s"><span class="pl-pds">"</span>%{count} new message<span class="pl-pds">"</span></span></pre></div>
<p dir="auto">Some of our translators have figured out that you can always use <code class="notranslate">%{count}</code> in these circumstances. For example, in Ukrainian they have translated <code class="notranslate">one: 1 way</code> as <code class="notranslate">one: '%{count} лінії'</code> and this will work fine for e.g. 51 ways. Other languages can also do the same, if they are affected by this.</p>
<p dir="auto">However, we should standardise on using the %{count} placeholder in en.yml, to help guide our translators to let them know this is possible. Not all translators will realise that they can use the <code class="notranslate">%{count}</code> placeholder, since it's not shown in the original string.</p>
<p dir="auto">It would also have a small benefit if we start validating that each translation takes the same placeholders as the original.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/3972">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLN4OM4663JFUVAN6PLW4IERLANCNFSM6AAAAAAV4HNZBA">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLIOG7A75YG7DOGWX7LW4IERLA5CNFSM6AAAAAAV4HNZBCWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHGB26FKM.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/issues/3972</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/3972",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/3972",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>