<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 9/21/2018 10:58 AM, Sanjeev Gupta wrote:<br>
<blockquote type="cite"
cite="mid:CAHZk5WfhA7x7f-sP6JoOWJ1=-LC_SPDgcbTE5Q-49_=RHFh_=Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div>Yes, having a sentence ...<br>
</div>
<div><br>
</div>
<div>The change in the value of the residual, after 2 hours or
35 iterations, should not exceed 23</div>
<div>ppm is a requirement of various standards, among which
are NIST 543:62 and FIPS <br>
</div>
<div>180 published in 2017.<br>
</div>
<div><br>
</div>
<div>... is slightly confusing wih the line breaks as above.<br>
</div>
<div> </div>
</div>
</div>
</blockquote>
Yep, exactly.<br>
<br>
<blockquote type="cite"
cite="mid:CAHZk5WfhA7x7f-sP6JoOWJ1=-LC_SPDgcbTE5Q-49_=RHFh_=Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>
... but you do not know how wide my terminal is when I
display the text ...<br>
</div>
</div>
</div>
</blockquote>
<br>
True. Which would argue for non-breaking space at virtually every
instance of a value/unit declaration.<br>
<br>
This is a tough one. I am not really competent with asciidoc and its
plenitude of options. I've already run across a few instances of
ascii escapes in the text files for rendering the microsecond symbol
and others - not a lot of them, but they are scattered about in the
various doc files, and implicitly muck up appearance if viewed in
one or another format (for me, emacs). <br>
<br>
So....now I'm starting to lean away from the NIST guidelines (sigh).
For example, they also recommend (#16, the very next line item)<tt>:</tt><span
style="color: rgb(0, 0, 0); font-family: "Exo 2";
font-size: medium; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: 700;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration-style: initial; text-decoration-color: initial;
display: inline !important; float: none;"><tt><br>
</tt></span>
<blockquote><tt>The digits of numerical values having more than four
digits on either side of the decimal marker are separated into
groups of three using a thin, fixed space counting from both the
left and right of the decimal marker. Commas are not used to
separate digits into groups of three.</tt><br>
</blockquote>
<blockquote><tt>proper:</tt><tt><br>
</tt><tt> 15 739.012 53</tt><tt><br>
</tt><tt>improper:</tt><tt><br>
</tt><tt> 15739.01253</tt><tt><br>
</tt><tt>15,739.012 53</tt><br>
</blockquote>
I find that completely wrongheaded. Not only would it further
disrupt documents regarding line breaks in asciidoc, I find
readability significantly _diminished_ by that style.<br>
<br>
So, great. here we are. I lobbied to conform to NIST guidelines, now
I'm rebelling against them. <br>
<br>
Let me throw this out there - I personally prefer conjoined
value/unit ( 53µs ). Sanjeev does also. Anyone else want to weigh
in? <br>
<br>
This is beginning to feel a bit like asking the board of directors
to spend a day deciding between Dixon Ticonderoga or Faber-Castell
pencils for the company.<br>
<br>
<pre class="moz-signature" cols="72">--
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a>
</pre>
</body>
</html>