<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt"><div><span style="color: rgb(192, 0, 0);">Hi :)</span><br style="color: rgb(192, 0, 0);"><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">I agree. I think we have to be specific for things like "gedit" in coding brackets so that people can just copy&paste without really understanding what is going on until they have tried it a few times.</span><br style="color: rgb(192, 0, 0);"><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">Often in answers section when/if we point people to documentation we make it clear that different distros use different default text-editors and some people prefer to use their own which is fine. Often we try to find clues about which version they are using although they are often shy if they feel they are cheekily asking in the wrong
forum.</span><br style="color: rgb(192, 0, 0);"><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">Also within the documentation itself we do sometimes see that people try so hard to re-explain the differences between the different versions that it makes the documentation very hard to follow. I think those differences could usefully be covered by a separate page which could then be linked to. In this case a page about </span><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">/community/text-editors</span><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">might help clear things up without interrupting the flow of the separate pages.</span><br style="color: rgb(192, 0, 0);"><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">Since linux is so versatile and people will have tweaked their own installation you could argue that giving any kind of help or documentation is
pointless as it will be inaccurate on at least one person's machine somewhere. I think we have to draw a line somewhere and have to hope that people are not completely stupid all the time and are in fact capable of working things out from a concrete example, after a bit of playing around perhaps</span><br style="color: rgb(192, 0, 0);"><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">Regards from</span><br style="color: rgb(192, 0, 0);"><span style="color: rgb(192, 0, 0);">Tom :)</span><br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Phil Bull <philbull@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Phillip Whiteside <phillw@phillw.net><br><b><span style="font-weight: bold;">Cc:</span></b>
lubuntu-desktop <lubuntu-desktop@lists.launchpad.net>; ubuntu-doc@lists.ubuntu.com<br><b><span style="font-weight: bold;">Sent:</span></b> Sun, 4 July, 2010 21:45:53<br><b><span style="font-weight: bold;">Subject:</span></b> Re: Using Mallard for Ubuntu docs<br></font><br>Hi Phill,<br><br>On Thu, 2010-07-01 at 23:36 +0100, Phillip Whiteside wrote:<br>> as one who does not use gnome, my little two cents worth is that<br>> instructions should not be tied 100% to gnome. Whilst the vast<br>> majority use 'vanilla' ubuntu, there are other flavours. As ubuntu is<br>> ubuntu, should we be as aware of that as we are translations? <br>> Xubuntu, Kubuntu etc. Each of the flavours has translation teams and<br>> I'm sure some translators work on more than one flavour, the 'base'<br>> installation documents need to cover all that is common (grub, kernel<br>> etc) after that how does for example, the chromium browser team from<br>>
ubuntu work with those from kde work with xfce, work with lxde etc ?<br>> I've seen some excellent wiki pages that put in the difference between<br>> gksudo and kdesu. One easy example for lubuntu (allbeit not a fully<br>> fledged ubuntu yet) is that it would be leafpad and not gedit that is<br>> the shipped programme for people to do that lower level of editing<br>> with.<br><br>The use of Mallard with other (non-GNOME) flavours of Ubuntu is a little<br>more complicated. I think Xfce may be willing to adopt Mallard, but I'm<br>not sure what the situation is with KDE. The others I have even less<br>idea about.<br><br>Where instructions can be written generically they should be, but there<br>are going to be lots of instances where GNOME-specific instructions have<br>to be used. Trying to write too generically will confuse users, and<br>providing multiple instructions in one topic would also be confusing<br>because then users have to figure
out which DE they're using every time.<br><br>In order to promote re-use between different flavours, perhaps we can<br>come up with some system of flagging-up completely reusable topics, and<br>topics which can be reused with some editing? That way, the job of<br>editing Ubuntu/GNOME docs to work with Kubuntu/KDE or whatever could be<br>made easier. There was also talk of a "conditional element" feature in<br>Mallard that would insert the right material depending on the DE that<br>was running, but that could get complicated and ugly. It's something we<br>should play around with, anyway.<br><br>Thanks,<br><br>Phil<br><br>-- <br>Phil Bull<br><a href="https://launchpad.net/%7Ephilbull" target="_blank">https://launchpad.net/~philbull</a><br><br><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></div></div>
</div><br>
</body></html>