The code is below. Note all the soft hyphens at each camel-case break, and yet note how there's a massive space after loadFont-<break>Catalog, even though what's after it has many soft hyphens where it could wrap.
Puzzled.
<p class="docpress-continuation">Camel-case naming debates add many near-duplicates. A review may compare <code>create­Render­Job</code>, <code>create­Renderer­Job</code>, <code>create­Pdf­Render­Job</code>, and <code>create­Published­Document­Render­Job</code>, then ask whether <code>load­Font­Catalog</code>, <code>load­Font­Set­Catalog</code>, <code>load­Document­Font­Set­Catalog</code>, and <code>load­Resolved­Document­Font­Set­Catalog</code> are too similar. It may mention <code>is­Preview­Mode</code>, <code>has­Preview­Mode</code>, <code>should­Use­Preview­Mode</code>, <code>can­Use­Preview­Mode</code>, and <code>was­Preview­Mode­Requested</code> in one dense paragraph. Those names should remain individually inspectable without turning the whole paragraph into a stripe of dark code spans.</p>
Puzzled.
<p class="docpress-continuation">Camel-case naming debates add many near-duplicates. A review may compare <code>create­Render­Job</code>, <code>create­Renderer­Job</code>, <code>create­Pdf­Render­Job</code>, and <code>create­Published­Document­Render­Job</code>, then ask whether <code>load­Font­Catalog</code>, <code>load­Font­Set­Catalog</code>, <code>load­Document­Font­Set­Catalog</code>, and <code>load­Resolved­Document­Font­Set­Catalog</code> are too similar. It may mention <code>is­Preview­Mode</code>, <code>has­Preview­Mode</code>, <code>should­Use­Preview­Mode</code>, <code>can­Use­Preview­Mode</code>, and <code>was­Preview­Mode­Requested</code> in one dense paragraph. Those names should remain individually inspectable without turning the whole paragraph into a stripe of dark code spans.</p>
