<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 9/21/2018 1:07 AM, Sanjeev Gupta wrote:<br>
<blockquote type="cite"
cite="mid:CAHZk5Wf_v9iizqGzsWZFh7DxqTgATZ8h1+SU7vRq1WJxhbtVHg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div dir="ltr">
<div>Paul,</div>
<div><br>
</div>
<div>Personally, I find 25kg, 50ppm, 3m, more readable; but that
is neither here nor there.</div>
</div>
</blockquote>
<br>
I also prefer 'conjoined' value plus unit. It's a choice, not a law,
but I'm willing to conform to <br>
an objective resource in high standing (NIST) if that's what they
recommend, at least for <br>
published technical documents.<br>
<br>
<blockquote type="cite"
cite="mid:CAHZk5Wf_v9iizqGzsWZFh7DxqTgATZ8h1+SU7vRq1WJxhbtVHg@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>My concern is that the space between "25" and "kg" should
be non-breaking. Else, readability suffers badly. How do you
do this in asciidoc?</div>
</div>
</blockquote>
<br>
By non-breaking....I assume you mean some way to ensure that the
value doesn't get separated from the unit on a line-break during
conversion? I<br>
hadn't even thought of that.<br>
<br>
A quick search yielded this -
<a class="moz-txt-link-freetext" href="https://www.methods.co.nz/asciidoc/faq.html#_how_can_i_include_non_breaking_space_characters">https://www.methods.co.nz/asciidoc/faq.html#_how_can_i_include_non_breaking_space_characters</a><br>
<br>
<blockquote>Use the non-breaking space character entity reference <code> </code>
(see
the next question). You could also use the predefined <code>{nbsp}</code>
attribute reference.</blockquote>
<br>
But then - would that imply that the non-breaking space would have
to be inserted at nearly all value/unit entries, since we can't know
for sure<br>
where asciidoc may wind up doing a line break? I guess it could be
case-by-case, if a test conversion has it happen, insert one there.<br>
<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAHZk5Wf_v9iizqGzsWZFh7DxqTgATZ8h1+SU7vRq1WJxhbtVHg@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">-- <br>
Sanjeev Gupta<br>
+65 98551208 <a
href="http://www.linkedin.com/in/ghane" target="_blank"
moz-do-not-send="true">http://www.linkedin.com/in/ghane</a></div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Thu, Sep 20, 2018 at 3:56 AM Paul
Theodoropoulos via devel <<a href="mailto:devel@ntpsec.org"
moz-do-not-send="true">devel@ntpsec.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> NIST has a page of
guidelines for formatting units in documents - <br>
<br>
<a class="m_-5774758564791836381moz-txt-link-freetext"
href="https://physics.nist.gov/cuu/Units/checklist.html"
target="_blank" moz-do-not-send="true">https://physics.nist.gov/cuu/Units/checklist.html</a><br>
<br>
I am conforming unit presentation within the various
documents I'm editing to use the guidelines, mostly #15:<br>
<tt><br>
</tt>
<blockquote><tt>There is a space between the numerical value
and unit symbol, even when the value is used in an
adjectival sense, except in the case of superscript
units for plane angle.</tt><tt><br>
</tt><tt><br>
</tt><tt>proper: a 25 kg sphere</tt><tt><br>
</tt><tt> an angle of 2° 3' 4"</tt><tt><br>
</tt><tt> If the spelled-out name of a unit is
used, the normal rules of English apply: "a roll of
35-millimeter film."</tt><tt><br>
<br>
</tt><tt>improper: a 25-kg sphere</tt><tt><br>
</tt><tt> an angle of 2 ° 3 ' 4 "</tt><tt><br>
</tt></blockquote>
So for example, where there are instances of 50ppm, 8-ms,
I'm updating them to 50 ppm, 8 ms.<br>
<br>
Uniformity of presentation seems like a desireable goal -
are there any objections to following these particular
guidelines?<br>
<br>
There's a handful of other conventions codified that may
turn up needing conformance, which I'll also conform where I
find them - where reasonable.<br>
<br>
<pre class="m_-5774758564791836381moz-signature" cols="72">--
Paul Theodoropoulos
<a class="m_-5774758564791836381moz-txt-link-abbreviated" href="http://www.anastrophe.com" target="_blank" moz-do-not-send="true">www.anastrophe.com</a></pre>
</div>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@ntpsec.org" target="_blank"
moz-do-not-send="true">devel@ntpsec.org</a><br>
<a href="http://lists.ntpsec.org/mailman/listinfo/devel"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ntpsec.org/mailman/listinfo/devel</a><br>
</blockquote>
</div>
</blockquote>
<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>