openstack-doc-core team mailing list archive
-
openstack-doc-core team
-
Mailing list archive
-
Message #00092
Re: How should we mark up nova-* services?
I think monospace is fine for now. In the long run think I'd like a different font (not italics/bold) to make it visually distinct from literals, but I'm not sure what would look good, and I don't want to create too much visual noise.
Take care,
Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
On May 18, 2012, at 5:13 PM, David Cramer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rather decide how you want it to render (monospace, bold, italics,
> quoted, red, green, different font size, different font, in a <blink>
> tag, or some combination) and let me know, I'll adjust the xslts and
> it will start doing that in the future (starting with that version of
> the plugin).
>
> David
>
> On 05/18/2012 04:01 PM, Razique Mahroua wrote:
>> Thanks, so I can, basically run a formatting test, send you the xml
>> file and you could show us how it'll render ? I've deployed the
>> maven env. on my comp ^^
>>
>> Razique
>>
>>> David Cramer <mailto:david.cramer@xxxxxxxxxxxxx> 18 mai 2012
>>> 21:18
>> Btw., I can make the html and pdf output (and the Oxygen wysioo
>> view) do whatever you want for that markup (or for any other
>> markup).
>>
>> David
>>
>>> Razique Mahroua <mailto:razique.mahroua@xxxxxxxxx> 18 mai 2012
>>> 10:37 Hi all, it would be interesting to see if the markup
>>> <systemitem class="service"> get interpreted for the html output,
>>> if so, we could give it a try. It would make the service
>>> designation in itself definitely clearer Best regards, Razique
>>>
>>>
>>> Anne Gentle <mailto:anne@xxxxxxxxxxxxx> 17 mai 2012 16:35 Thanks
>>> David for the guidance and Razique for knowing what our docs
>>> mostly do. :) I'm fine with adding the <systemitem
>>> class="service"> markup and see what it gains us later.
>>>
>>> Does anyone prefer quotation marks around the service names or
>>> is there another output style you'd like?
>>>
>>> Thanks, Anne
>>>
>>> Anne Gentle | http://justwriteclick.com/
>>>
>>> Facebook <http://facebook.com/conversationandcommunity>Linkedin
>>> <http://linkedin.com/annegentle>Twitter
>>> <http://twitter.com/annegentle>
>>>
>>>
>>>
>>>
>>> Razique Mahroua <mailto:razique.mahroua@xxxxxxxxx> 17 mai 2012
>>> 12:32 Actually it uses "" eg "nova-volume" is... I think 90% of
>>> the doc uses that convention. But it could be great to have a
>>> convention for it yes :)
>>>
>>> On Thu, 17 May 2012 05:21:40 +0200, David Cramer
>>> <david.cramer@xxxxxxxxxxxxx> wrote:
>>>
>>> David Cramer <mailto:david.cramer@xxxxxxxxxxxxx> 17 mai 2012
>>> 05:21 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>
>>> You probably want:
>>>
>>> <systemitem class="service">
>>>
>>> http://www.docbook.org/tdg5/en/html/systemitem.html
>>>
>>> The things to think about in deciding whether to mark something
>>> like this up are:
>>>
>>> 1) Do I want to be able to have this thing formatted in a
>>> particular way? E.g. monospace, bold. 2) Do I want to be able to
>>> do something else later (index, cross reference, etc) with this
>>> term?
>>>
>>> If either are true, then you should have a policy of marking it
>>> up and agree on a tag to use.
>>>
>>> Typing <systemitem class="service"> probably seems cumbersome,
>>> but I can add to oxygen a shortcut so that it feels like there's
>>> really a <service> tag. I.e. you press enter to pull up the
>>> context completion window, start typing "systemitem"...it
>>> autocompletes and you pick "systemitem-service" from thei list.
>>> Or we could even add a service tag to the schema.
>>>
>>> David
>>>
>>>
>>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iQEcBAEBAgAGBQJPtG7BAAoJEMHeSXG7afUhNeAH/jmNOn4Iw7MKKQr9enFhUdq1
>>> qL3xP6ixeqR+UZP0HrdTKchM2TLeljDY5gXLYKf1m9ZofIk5nnFKFBQGlACWC8Z3
>>> TjmEQM8XtAJeflmmWWEqnwWZ3kcjz3ivFB79liHpnkqhaqECcDEAISDLcLn+2xSW
>>> SqckiyCusDMffdhSZIZAx9pfY5B6utBJlSdDJYNauM+ARlPOtVq9UREy/UwK5oAe
>>> QzAzg6u1WkxFOqp+TdlLhqOcGOqMucL4qGvMQ+xb6nDMYo0lMJeIrNWzJXDYRBhi
>>> UaEtg2N+lJeu2cPbrEj+R95DNQ9ovPhXjtv3n6Pi1HRN746f01thDR+6HGMNCA4=
>>> =s5qz -----END PGP SIGNATURE-----
>>
>> -- Nuage & Co - Razique Mahroua razique.mahroua@xxxxxxxxx
>>
>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPtrtnAAoJEMHeSXG7afUhhRUH/jyYqZZV1pPL1/tw1848aVlP
> +nVwc1/RaHXj3h3W6zjQaKrCAkPE7wbLeLZD2OG+f7D7oPrIT4M+U1EXJgLf7SJk
> LMQz+5gJjXTMNxQxg8L4oLKuKv3GYcGR91A1G5Si3Fe6gSiFQr++mIaj9uVwGbWJ
> EOKz9owz0bC3kTXWzW4Kq4WU/al8ft8FXgzw4fYEgWZTY6esXCMsKeAKHAnQFEIN
> AYxI0hrOq8oYEXH68orXWX22MeR6yJl29lCJyHrh+6NWgisHDqIGSApmdMU5vU2L
> Ku9j8zMOuFknVQYWv2DlnRtWdyOOhmm7r/jY2TDdbj5zoD6AuOKAA0ZynWMUgOA=
> =CDl3
> -----END PGP SIGNATURE-----
>
> --
> Mailing list: https://launchpad.net/~openstack-doc-core
> Post to : openstack-doc-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-doc-core
> More help : https://help.launchpad.net/ListHelp
References
-
How should we mark up nova-* services?
From: Lorin Hochstein, 2012-05-16
-
Re: How should we mark up nova-* services?
From: Razique Mahroua, 2012-05-16
-
Re: How should we mark up nova-* services?
From: Lorin Hochstein, 2012-05-17
-
Re: How should we mark up nova-* services?
From: David Cramer, 2012-05-17
-
Re: How should we mark up nova-* services?
From: Razique Mahroua, 2012-05-17
-
Re: How should we mark up nova-* services?
From: Anne Gentle, 2012-05-17
-
Re: How should we mark up nova-* services?
From: Razique Mahroua, 2012-05-18
-
Re: How should we mark up nova-* services?
From: David Cramer, 2012-05-18
-
Re: How should we mark up nova-* services?
From: Razique Mahroua, 2012-05-18
-
Re: How should we mark up nova-* services?
From: David Cramer, 2012-05-18