Archived
deploy.
This commit is contained in:
+5
@@ -142,6 +142,11 @@ fourth — an alarm on controllers strict about their least input increment. Dig
|
||||
scanned per word family over the played source texts with comment spans masked, floored at 3/3/0 and
|
||||
capped at 9, and threaded through the whole write path. The word-suppression tolerances and the F
|
||||
comparison grid derive from the resolved digits instead of the old fixed literals.</li>
|
||||
<li><strong>Leading zeros follow the source, and the project can pin the spelling.</strong>
|
||||
<a class="xref" href="../../api/Hi.NcOpt.NcOptOption.html#Hi_NcOpt_NcOptOption_OmitLeadingZero">OmitLeadingZero</a> is an output style: on, the writer drops a leading
|
||||
zero before the decimal (<code>.5</code> rather than <code>0.5</code>); off, it writes the zero. The option is carried on
|
||||
the project so two machines produce the same bytes, and a report names which style the source
|
||||
itself used.</li>
|
||||
<li><strong>Optimized NC is written back in the source file's encoding.</strong> NC play reads and optimized writes go
|
||||
through <a class="xref" href="../../api/Hi.Common.FileLines.FileUtil.html#Hi_Common_FileLines_FileUtil_DetectRoundTripEncoding_">DetectRoundTripEncoding</a> — BOM, then strict UTF-8, then
|
||||
Latin-1 — so an ANSI-family file (GBK, Big5, Shift-JIS) re-encodes to its original bytes instead of
|
||||
|
||||
Reference in New Issue
Block a user