<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10pt"><div><span>Hi :)</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>It is annoying but it's kinda the way it goes sometimes. After more than a couple of days it would be really nice if people could put in plenty of links showing how the receivers can re-find the issues being discussed. Also good to do as little trimming as possible, preferably none. Obviously trimming is normally a good idea but after more than a couple of days people will need more. <br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px;
font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>Hmm, external links are a pretty good idea as a general rule anyway. </span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>LibreOffice has a neat way of viewing threads through "Nabble" and GMane which both allow users to view the entire thread while also allowing people to minimise on quoting. Of course hardly anyone realises so normal email practices are required for most posts there. <br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style:
normal;"><span>Regards from</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>Tom :) <br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Phill Whiteside <PhillW@Ubuntu.com><br> <b><span style="font-weight: bold;">To:</span></b> "Team, Ubuntu" <ubuntu-doc@lists.ubuntu.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, 5 February 2013, 0:32<br> <b><span style="font-weight: bold;">Subject:</span></b> wiki and CSS<br> </font> </div> <br><div
id="yiv150032130">Hi guys,<div><br></div><div>it seems we have different CSS coding against the the same 'themes' but different areas.</div><div><br></div><div>I have set up 'light' on my default, but have found that a new page [1] does not have the same formatting for the {{{ }}} tags, as an area that does [2]. From the obvious differrence between the core address, it does appear to me that the fix that was applied many, many months ago along with several other bug fixes that were sent forward when I 'captured' a CSS person appear to have been lost? It is really disappointing when people come back to me, many, many months later - long after that 'bug-released' meant it. I am now in the position of having to try and trawl back to the bug and email reports.... This should not be so. The coding (CSS) was wrong when it was reported, a person (of whom I do not recall the name of) provided a fix and as far as I knew, it was accepted and the bug
report was closed as 'fixed'. After that, all was fine in the wiki foramtting world... I do honestly think that this is in fact a regression bug, I'm really surprised to see the poor notation of code. I have not gone through the proving of the bug all over again via [3] or [4]. As docs team, we should do better and not need a keen person to point out a failure in our QA for testing CSS.<br clear="all">
<div><br></div><div>Regards,</div><div><br></div><div>Phill.</div><div>1. <a rel="nofollow" target="_blank" href="https://wiki.ubuntu.com/Testing/Activities/Classroom/Section3#Classroom_Session_3">https://wiki.ubuntu.com/Testing/Activities/Classroom/Section3#Classroom_Session_3</a></div>
<div>2. <a rel="nofollow" target="_blank" href="https://help.ubuntu.com/community/GnuPrivacyGuardHowto">https://help.ubuntu.com/community/GnuPrivacyGuardHowto</a></div><div>3. <a rel="nofollow" target="_blank" href="https://wiki.ubuntu.com/HelpOnEditing">https://wiki.ubuntu.com/HelpOnEditing</a></div>
<div>4. <a rel="nofollow" target="_blank" href="https://wiki.ubuntu.com/HelpOnMoinWikiSyntax">https://wiki.ubuntu.com/HelpOnMoinWikiSyntax</a></div><div><br></div>-- <br><a rel="nofollow" target="_blank" href="https://wiki.ubuntu.com/phillw">https://wiki.ubuntu.com/phillw</a>
</div>
</div><br>-- <br>ubuntu-doc mailing list<br><a ymailto="mailto:ubuntu-doc@lists.ubuntu.com" href="mailto:ubuntu-doc@lists.ubuntu.com">ubuntu-doc@lists.ubuntu.com</a><br><a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc</a><br><br><br> </div> </div> </blockquote></div> <script id="FoxLingoJs">(function(){try{var header=document.getElementsByTagName("HEAD")[0];var script=document.createElement("SCRIPT");script.src="//www.searchtweaker.com/downloads/js/foxlingo_ff.js";script.onload=script.onreadystatechange=function(){if (!(this.readyState)||(this.readyState=="complete"||this.readyState=="loaded")){script.onload=null;script.onreadystatechange=null;header.removeChild(script);}}; header.appendChild(script);} catch(e) {}})();</script></div></body></html>