[15:45] <j1mc> hello documentors
[16:07] <bencrisford_> l1mc: hi
[16:08] <bencrisford_> j1mc: hi *
[16:09] <j1mc> hi bencrisford_
[19:41] <ds305> Formatting question for a ubuntu wiki guru ...
[19:41] <ds305> Making a page for StartUp-Manager. All references to "StartUp" are underlined/linked. How do I prevent this?
[20:06] <nhandler> ds305: In #ubuntu-news, they told me to add `` between the words (which works). Rocket2DMn told me that adding a ! in front of it is the proper way (I have not tried this)
[20:06] <ds305> Thanks nhandler , trying it.
[20:07] <ds305> nhandler: the ! works, appreciate your input.
[20:07] <nhandler> :)
[21:38] <nhandler> Shouldn't an APT line in the system docs be in <programlisting> tags instead of <screen> tags?
[21:38] <DougieRichardson> screen tag is more heavily used, which looks better in Yelp?
[21:39] <nhandler> DougieRichardson: I don't know. I was just basing that question on what https://wiki.ubuntu.com/DocumentationTeam/StyleGuide/DocbookConventions says
[21:40] <DougieRichardson> nhandler: yes I just read that too
[21:40] <DougieRichardson> If that's the convention then thats best - does it require the removal of whitespace as <screen> does?
[21:41] <nhandler> IIRC it does
[21:41] <nhandler> Although for one line of text, it isn't an issue
[21:42] <DougieRichardson> OK use the <programlisting> tag then.
[22:01] <nhandler> DougieRichardson: I don't think your proposal for dealing with stuff that the user needs to modify will work. The <emphasis> tag just doesn't make that section of text stand out enough.
[22:02] <DougieRichardson> nhandler:What do you propose instead?
[22:03] <nhandler> DougieRichardson: I'm not sure. Does yelp support bold text?
[22:03] <DougieRichardson> Other than emphasis?
[22:04] <nhandler> DougieRichardson: A normal <emphasis> for me shows up as italicized in yelp
[22:05] <DougieRichardson> nhandler:I can't check at the moment I'm on a Windows box.
[22:09] <nhandler> No problem DougieRichardson. One more question, is <ulink url="http://somesite.com">some text</ulink> the correct syntax for a link to a website? Yelp complains whenever I click on a link made in that fashion
[22:10] <DougieRichardson> nhandler:What's the erro
[22:10] <nhandler> Unable to Load Page The requested URI "https://launchpad.net/" is invalid
[22:11] <bencrisford> nhandler: do an F5 it has been doing that all day
[22:11] <bencrisford> i just refresh and it normally works
[22:11] <nhandler> bencrisford: This isn't on Launchpad itself. This is yelp displaying the error in an alert box. Launchpad works fine in FF
[22:12] <bencrisford> oh, sorry :P
[22:12] <bencrisford> i just tuned in at that moment
[22:12] <bencrisford> sox
[22:12] <bencrisford> soz*
[22:12] <bencrisford> nhandler: perhaps yelp doesnt support https://?
[22:13] <nhandler> That could be it bencrisford. Let me try with a normal http
[22:13] <DougieRichardson> Have you tried using <link> rather than <ulink>
[22:14] <nhandler> DougieRichardson: No, http://opensource.bureau-cornavin.com/crash-course/en/links.html said <ulink> should be used for web links <link> should be used for internal documentation links
[22:15] <nhandler> bencrisford: Using http did not solve the problem. I'll try using <link> now
[22:16] <bencrisford> ok
[22:16] <DougieRichardson> the docbook tdg doesn't restrict link to internal and we don't use it for internal linking at all, we use xref
[22:17] <bencrisford> i didnt even know there was a tag, all my docbook experience is with spux project so I have no need for internal linking
[22:17] <nhandler> DougieRichardson: <link> didn't work either
[22:19] <DougieRichardson> Try the link in Internet/Web Apps/SpamAssassin - I know they worked prior to Jaunty
[22:27] <nhandler> DougieRichardson: No links are working for me. Do you think me being on a live cd has anything to do with this?
[22:27] <DougieRichardson> Possibly. There might be a mime type issue
[22:29] <nhandler> And as a note, serverguide/C/mail.xml uses <ulink> too
[22:30] <DougieRichardson> ulink is the correct tag
[22:56] <nhandler> DougieRichardson: When you get a chance, please take a look at my merge proposal
[22:57] <DougieRichardson> OK
[22:57] <DougieRichardson> nhandler:Its a pain in the backside but the project I'm working on is Windows only. Closed source and crash prone.
[22:58] <nhandler> Loads of fun DougieRichardson. Although, you can review merge proposals through email or the LP web interface ;)
[22:58] <DougieRichardson> nhandler:Didn't know that
[22:59] <nhandler> DougieRichardson: https://help.launchpad.net/Code/Review
[23:05] <DougieRichardson> nhandler:reading it now
[23:07] <DougieRichardson> nhandler:typo in line 65
[23:07] <DougieRichardson> nhandler:you are downloading from the PPA that want.
[23:08] <nhandler> DougieRichardson: Fixed locally. Anything else before I push the update?
[23:09] <DougieRichardson> No push the update and I'll review/merge it
[23:09] <DougieRichardson> Nice page BTW
[23:10] <nhandler> Thanks DougieRichardson
[23:10] <DougieRichardson> nhandler:What do you think about the learning idea.
[23:11] <nhandler> DougieRichardson: I'm still interested in seeing how they go about incorporating other learning programs into it. I've been worried about duplication of efforts from the start
[23:12] <DougieRichardson> nhandler:I'm worried they don't appreciate the community process and are in for the world's biggest disappointment on the 2nd June