<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>
<div>One screen is fine – especially if the style of the output changes so that user can see the input versus the output. </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div style="color: rgb(0, 0, 0); "><font class="Apple-style-span" color="rgb(0, 0, 0)" face="Apple Chancery"><i>Diane</i></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); ">
<font class="Apple-style-span" color="rgb(0, 0, 0)"><i>----------------------------------------------</i></font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; color: rgb(0, 0, 0); ">
<font class="Apple-style-span" color="rgb(0, 0, 0)">Diane Fleming</font></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="color: rgb(0, 0, 0); ">Software Developer II - US</div>
</div>
diane.fleming@rackspace.com</div>
<div>Cell 512.323.6799</div>
<div>Office 512.874.1260<br>
<span class="Apple-style-span" style="font-family: Calibri, sans-serif; ">
<div style="font-family: Calibri, sans-serif; font-size: 14px; ">
<div style="color: rgb(0, 0, 0); ">Skype drfleming0227</div>
<div style="color: rgb(0, 0, 0); ">Google-plus diane.fleming@gmail.com</div>
</div>
</span></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, March 24, 2014 9:23 AM<br>
<span style="font-weight:bold">To: </span>Gauvain Pocentek <<a href="mailto:gauvain.pocentek@objectif-libre.com">gauvain.pocentek@objectif-libre.com</a>><br>
<span style="font-weight:bold">Cc: </span>Andreas Jaeger <<a href="mailto:aj@suse.com">aj@suse.com</a>>, Diane Fleming <<a href="mailto:diane.fleming@rackspace.com">diane.fleming@rackspace.com</a>>, openstack-docs <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-docs] Convention on <screen> use<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Mar 24, 2014 at 9:20 AM, Gauvain Pocentek <span dir="ltr">
<<a href="mailto:gauvain.pocentek@objectif-libre.com" target="_blank">gauvain.pocentek@objectif-libre.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey,<br>
<br>
Thank you for your answer Anne.<br>
<br>
Le 2014-03-24 14:18, Anne Gentle a écrit :
<div class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Mar 24, 2014 at 3:26 AM, Gauvain Pocentek<br>
<<a href="mailto:gauvain.pocentek@objectif-libre.com" target="_blank">gauvain.pocentek@objectif-<u></u>libre.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Le 2014-03-21 14:15, Anne Gentle a écrit :<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Mar 21, 2014 at 3:52 AM, Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 03/20/2014 09:37 PM, Diane Fleming wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But I'm willing to go along with the consensus on this. And I totally<br>
agree that we need to have one convention that we all use.<br>
<br>
But here's why I like two screens:<br>
<br>
1. You can insert text between the user input and the computer output,<br>
such an explanation of what the user might see in the output.<br>
</blockquote>
<br>
You still can do this, I see no problem with that.<br>
</blockquote>
<br>
In the Ops Guide, we standardized on one screen wrapping <userinput><br>
and <computeroutput> but even so it was causing oddities with their<br>
transforms. <br>
<br>
I'd prefer <screen> around each. <br>
</blockquote>
<br>
OK. So to sum up, we're (I'm?) not happy with our tools rendering when using multiple <screen>s, and we have rendering issues when using a single <screen> too, although this only concerns the ops guide. Did I understand correctly?<br>
<br>
Rendering set aside, I think that one screen is more logical, because you don't type the command in one terminal, and get the output in another one. And prompts explicitly define what is to be typed.<br>
<br>
To reuse an argument from the basic OS setup discussion that took place yesterday ([0]), we can probably assume that users know how to use the command line, and that they will understand what is to be typed and what is the output.<br>
</blockquote>
<br>
No, please don't use that argument again.<br>
</blockquote>
<br>
</div>
OK, this is certainly not the best argument I could have used. Sorry about that.<br>
What I was trying to say was that we probably don't have to spell everything for the reader, and that using 1 screen makes things clear enough (in my humble opinion).<br>
<br>
Please let me know if I'm completely out of line here, I'll just shut up :)<br>
</blockquote>
<div><br>
</div>
<div>No worries at all, and I agree using one screen is probably clear enough that someone won't stumble into disaster areas. :) Thanks for logging the bug! Let's see what Diane thinks about the semantic markup here. </div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
I was hoping a DocBook markup expert would give us guidance. I think<br>
that semantically speaking, <screen> is meant to indicate all that<br>
someone sees on a screen. To quote from the DocBook reference,<br>
<br>
</div>
<a href="http://docbook.org/tdg5/en/html/screen.html" target="_blank">http://docbook.org/tdg5/en/<u></u>html/screen.html</a> [1]<br>
<br>
A screen [1] is a verbatim environment for displaying text that the
<div class=""><br>
user might see on a computer terminal. It is often used to display the<br>
results of a command.<br>
<br>
</div>
Having less specific semantic overtones, screen [1] is often used
<div class=""><br>
wherever a verbatim presentation is desired, but the semantic<br>
</div>
of programlisting [2] is inappropriate.
<div class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Let's try to move forward and make a decision about this, this shouldn't be that hard :)<br>
</blockquote>
<br>
It's hard because the semantics aren't specific. I am fine with a<br>
single <screen> since that is what the user sees. I think we can make<br>
the output nicer. Feel free to file a bug with the doc-builds tag for<br>
openstack-manuals.<br>
</div>
</blockquote>
<br>
Reported as <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1296731" target="_blank">
https://bugs.launchpad.net/<u></u>openstack-manuals/+bug/1296731</a><span class="HOEnZb"><font color="#888888"><br>
<br>
Gauvain<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>