From mw_triad at users.sourceforge.net Tue Sep 1 21:05:43 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Tue, 01 Sep 2009 19:05:43 +0000 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors Message-ID: <1251831943.403902.8662.nullmailer@svn.kde.org> SVN commit 1018504 by mwoehlke: Update color kcm doc based on comments from Burkhard L?ck. Further comments/suggestions welcomed, please send to me and/or k-doc-en. CCMAIL: kde-doc-english at kde.org M +46 -6 index.docbook --- trunk/KDE/kdebase/workspace/doc/kcontrol/colors/index.docbook #1018503:1018504 @@ -147,18 +147,31 @@ Colors The Colors tab allows you to change the colors in - a color scheme. The Common Colors set, which is displayed - initially, is not actually a "set" in the sense used by &kde; (see next - section), but presents a number of color roles in a way that makes it - easier to edit the scheme as a whole. When creating a new color scheme, you - will usually change these colors first, and use the other sets to tweak - specific colors if needed. + a color scheme. Creating or changing a scheme is a simple matter of clicking on the swatch in the color list and selecting a new color. You can check your changes at any time by pressing Apply. It is suggested that you save your scheme when you are done. + The Common Colors set, which is displayed + initially, is not actually a "set" in the sense used by &kde; (see + next section), but presents a number of color roles in a way that makes it + easier to edit the scheme as a whole. When creating a new color scheme, you + will usually change these colors first, and use the other sets to tweak + specific colors if needed. + + Note that Common Colors makes available roles from + all sets. For example, "View Background" here is shorthand for the + Normal Background role from the View set. Also, setting colors that do not + refer to a specific set will change that color in all + sets. (As an exception, "Inactive Text" will change the color for + all sets except for Selection; there is a separate + "Selection Inactive Text" for Inactive Text in the Selection set.) + Some roles may not be visible under Common Colors at + all, and can only be changed (if needed) by selecting the appropriate + set. + Color Sets @@ -261,6 +274,32 @@ The choice of color role is left to the developer; the above are guidelines intended to represent typical usage. + + + Window Manager Roles + + As previously stated, the Window Manager set has its own roles, + independent of those in other sets. These are (currently) only accessible + via Common Colors, and are as follows: + + + Active Titlebar — + used to draw the title bar background, borders, and/or decorations for + active window (that is, the one with input focus). Not all window + decorations will use this in the same way, and some may even use the + Normal Background from the Window set to draw the title bar. + + Active Titlebar Text — + used to draw the title bar text when Active Titlebar is used to draw + the title bar background. May also be used for other foreground + elements which use Active Titlebar as the background. + + + + The Inactive Titlebar [Text] roles are the same as the above, but for + inactive windows, rather than active windows. + + @@ -350,6 +389,7 @@ slider produces no change, while maximum causes the text to completely disappear into the background. + From jasilva28 at gmail.com Wed Sep 2 03:45:29 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Tue, 1 Sep 2009 21:45:29 -0400 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <1251831943.403902.8662.nullmailer@svn.kde.org> References: <1251831943.403902.8662.nullmailer@svn.kde.org> Message-ID: <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> Wow, since I rarely use this module (even in the 3.x days), I never realized how flexible this was. Perhaps I'm using an old edition of the KDE Help Center (the Colors section refers to a Revision 3.2), but I don't actually see this documentation anywhere. So either I'm looking in the wrong place, or this revision is old, or this is a new addition to that document. Either way, I couldn't compare this to anything preexisting. Fortunately, I just got done and tried everything as described in the help document below, and for the most part I understand what is being said. I do have a few small adjustments I'd like to suggest, if they're not too unreasonable: ============================================================================================= ============================================================================================= 1 ################################################################## In the line: + a custom scheme. I would suggest "custom scheme" if possible. The wording "color scheme" as used in the sentence almost seemed to imply I could take any scheme from the list (say, Magma), change it to all sorts of wacky colors, and then have that scheme save permanently with said wacky colors. The reality, however, is that the color changes will ONLY affect the virtual scheme called "Current", which will not be permanent unless explicitly saved with the Save Scheme button. 2 ################################################################## In the line: that you save your scheme when you are done. I would recommend referencing the Scheme tab, as in "save your scheme in the Scheme tab". It sounds like an obsessive precaution, but it may not be necessarily obvious to the initiate where the Save Scheme button is. 3 ################################################################## The entire section from: + The Common Colors set, which is displayed to + all, and can only be changed (if needed) by selecting the appropriate + set. ...is not technically wrong -- in fact, it's admirably detailed. However, it does seem like it goes into too great length to explain what Common Colors is, which, as I would describe it, is merely the "Simple View" of the Colors tab, whereas the View, Window, Button, Selection and Tooltip combined make up a kind of "Advanced View". Perhaps the detail is necessary after all since Common Colors is, unfortunately, mixed in with the other sets and easy to confuse as one. Perhaps this is really more of a UI issue, and could be fixed if that color set dropdown were replaced by a toggle between "Quickly Modify Common Colors" and "Fine Tune Color Sets", the latter of which would enable the dropdown with only View, Window, Button, Selection and Tooltip. But I'm not a dev, so I'll just mention that in passing -- if anything, the current setup likely has a rhyme-and-reason to it. ^^; 4 ################################################################## I'm not sure what: The choice of color role is left to the developer; the above are guidelines intended to represent typical usage. ...refers to unfortunately. :( Judging by the symbols, it seems this is only a DIFF from the source document, so there are likely snippets here and there of unrelated documentation left over. 5 ################################################################## In the lines: + used to draw the title bar background, borders, and/or decorations for + active window (that is, the one with input focus). Not all window I would add the "the" before "active window", so the phrase will read as "used to draw the title bar background, borders, and/or decorations for the active window...". 6 ################################################################### For the section: + used to draw the title bar text when Active Titlebar is used to draw + the title bar background. May also be used for other foreground + elements which use Active Titlebar as the background. I understand what it means, but I can't shake the feeling that "Active Titlebar" alone sounds a bit broken. But I can't really say that "the Active Titlebar role" will make it any better. :( 7 ################################################################### Looking back on the entire section of Window Manager Roles, I can't help but feel a small contradiction regarding the role of Common Colors, given it does indeed contain UNIQUE elements not found in View, Window, Button, Selection, or Tooltip. In reality, there really should be a Window Manager set too in order for the Common Colors pseudo-set to be true to its name. But again, this is a dev issue. ;) ============================================================================================= ============================================================================================= And that concludes my analysis. Sorry for the length, and also for not actually doing these changes myself, but I don't know how and besides these are really suggestions only. The last call is yours. ^^b Thank you for allowing me to use this as my first substantial contribution to KDE. It's not much, but I hope it's a start. ^___^ Cheers! --Arturo "C-quel" Silva On Tue, Sep 1, 2009 at 3:05 PM, Matthew Woehlke < mw_triad at users.sourceforge.net> wrote: > SVN commit 1018504 by mwoehlke: > > Update color kcm doc based on comments from Burkhard L?ck. > > Further comments/suggestions welcomed, please send to me and/or k-doc-en. > > CCMAIL: kde-doc-english at kde.org > > > M +46 -6 index.docbook > > > --- trunk/KDE/kdebase/workspace/doc/kcontrol/colors/index.docbook > #1018503:1018504 > @@ -147,18 +147,31 @@ > Colors > > The Colors tab allows you to change the colors > in > - a color scheme. The Common Colors set, which is > displayed > - initially, is not actually a "set" in the sense used by &kde; (see next > - section), but presents a number of color roles in a way that makes it > - easier to edit the scheme as a whole. When creating a new color scheme, > you > - will usually change these colors first, and use the other sets to tweak > - specific colors if needed. > + a color scheme. > > Creating or changing a scheme is a simple matter of clicking on the > swatch in the color list and selecting a new color. You can check your > changes at any time by pressing Apply. It is > suggested > that you save your scheme when you are done. > > + The Common Colors set, which is displayed > + initially, is not actually a "set" in the sense used by &kde; > (see > + next section), but presents a number of color roles in a way that makes > it > + easier to edit the scheme as a whole. When creating a new color scheme, > you > + will usually change these colors first, and use the other sets to tweak > + specific colors if needed. > + > + Note that Common Colors makes available roles > from > + all sets. For example, "View Background" here is shorthand for > the > + Normal Background role from the View set. Also, setting colors that do > not > + refer to a specific set will change that color in > all > + sets. (As an exception, "Inactive Text" will change the color > for > + all sets except for Selection; there is a separate > + "Selection Inactive Text" for Inactive Text in the Selection > set.) > + Some roles may not be visible under Common Colors > at > + all, and can only be changed (if needed) by selecting the appropriate > + set. > + > > Color Sets > > @@ -261,6 +274,32 @@ > The choice of color role is left to the developer; the above are > guidelines intended to represent typical usage. > > + > + > + Window Manager Roles > + > + As previously stated, the Window Manager set has its own roles, > + independent of those in other sets. These are (currently) only > accessible > + via Common Colors, and are as follows: > + > + > + Active Titlebar — > + used to draw the title bar background, borders, and/or decorations > for > + active window (that is, the one with input focus). Not all window > + decorations will use this in the same way, and some may even use > the > + Normal Background from the Window set to draw the title bar. > + > + Active Titlebar Text — > + used to draw the title bar text when Active Titlebar is used to > draw > + the title bar background. May also be used for other foreground > + elements which use Active Titlebar as the background. > + > + > + > + The Inactive Titlebar [Text] roles are the same as the above, > but for > + inactive windows, rather than active windows. > + > + > > > > @@ -350,6 +389,7 @@ > slider produces no change, while maximum causes the text to completely > disappear into the background. > > + > > > > _______________________________________________ > kde-doc-english mailing list > kde-doc-english at kde.org > https://mail.kde.org/mailman/listinfo/kde-doc-english > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.kde.org/pipermail/kde-doc-english/attachments/20090901/d209541d/attachment.htm From davide.bettio at kdemail.net Wed Sep 2 01:00:46 2009 From: davide.bettio at kdemail.net (Davide Bettio) Date: Tue, 01 Sep 2009 23:00:46 +0000 Subject: [kde-doc-english] KDE/kdebase/workspace/kcontrol/style Message-ID: <1251846046.709332.18914.nullmailer@svn.kde.org> SVN commit 1018617 by bettio: GUI: New layout: button moved below the list. Changed a string: "New Theme" -> "Get New Themes". M +18 -18 theme.ui --- trunk/KDE/kdebase/workspace/kcontrol/style/theme.ui #1018616:1018617 @@ -6,37 +6,37 @@ 0 0 - 691 - 365 + 482 + 287 - + - + + + + Qt::Horizontal + + + + 348 + 20 + + + + + true - New Theme... + Get New Themes... - - - - Qt::Vertical - - - - 20 - 256 - - - - From lueck at hube-lueck.de Wed Sep 2 07:20:38 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Wed, 2 Sep 2009 07:20:38 +0200 Subject: [kde-doc-english] Fwd: Re: KDE/kdebase/workspace/doc/kcontrol/colors Message-ID: <200909020720.38615.lueck@hube-lueck.de> ---------- Weitergeleitete Nachricht ---------- Betreff: Re: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors Datum: Mittwoch 02 September 2009 Von: Arturo Silva An: For people writing documentation for KDE Wow, since I rarely use this module (even in the 3.x days), I never realized how flexible this was. Perhaps I'm using an old edition of the KDE Help Center (the Colors section refers to a Revision 3.2), but I don't actually see this documentation anywhere. So either I'm looking in the wrong place, or this revision is old, or this is a new addition to that document. Either way, I couldn't compare this to anything preexisting. Fortunately, I just got done and tried everything as described in the help document below, and for the most part I understand what is being said. I do have a few small adjustments I'd like to suggest, if they're not too unreasonable: ============================================================================================= ============================================================================================= 1 ################################################################## In the line: + a custom scheme. I would suggest "custom scheme" if possible. The wording "color scheme" as used in the sentence almost seemed to imply I could take any scheme from the list (say, Magma), change it to all sorts of wacky colors, and then have that scheme save permanently with said wacky colors. The reality, however, is that the color changes will ONLY affect the virtual scheme called "Current", which will not be permanent unless explicitly saved with the Save Scheme button. 2 ################################################################## In the line: that you save your scheme when you are done. I would recommend referencing the Scheme tab, as in "save your scheme in the Scheme tab". It sounds like an obsessive precaution, but it may not be necessarily obvious to the initiate where the Save Scheme button is. 3 ################################################################## The entire section from: + The Common Colors set, which is displayed to + all, and can only be changed (if needed) by selecting the appropriate + set. ...is not technically wrong -- in fact, it's admirably detailed. However, it does seem like it goes into too great length to explain what Common Colors is, which, as I would describe it, is merely the "Simple View" of the Colors tab, whereas the View, Window, Button, Selection and Tooltip combined make up a kind of "Advanced View". Perhaps the detail is necessary after all since Common Colors is, unfortunately, mixed in with the other sets and easy to confuse as one. Perhaps this is really more of a UI issue, and could be fixed if that color set dropdown were replaced by a toggle between "Quickly Modify Common Colors" and "Fine Tune Color Sets", the latter of which would enable the dropdown with only View, Window, Button, Selection and Tooltip. But I'm not a dev, so I'll just mention that in passing -- if anything, the current setup likely has a rhyme-and-reason to it. ^^; 4 ################################################################## I'm not sure what: The choice of color role is left to the developer; the above are guidelines intended to represent typical usage. ...refers to unfortunately. :( Judging by the symbols, it seems this is only a DIFF from the source document, so there are likely snippets here and there of unrelated documentation left over. 5 ################################################################## In the lines: + used to draw the title bar background, borders, and/or decorations for + active window (that is, the one with input focus). Not all window I would add the "the" before "active window", so the phrase will read as "used to draw the title bar background, borders, and/or decorations for the active window...". 6 ################################################################### For the section: + used to draw the title bar text when Active Titlebar is used to draw + the title bar background. May also be used for other foreground + elements which use Active Titlebar as the background. I understand what it means, but I can't shake the feeling that "Active Titlebar" alone sounds a bit broken. But I can't really say that "the Active Titlebar role" will make it any better. :( 7 ################################################################### Looking back on the entire section of Window Manager Roles, I can't help but feel a small contradiction regarding the role of Common Colors, given it does indeed contain UNIQUE elements not found in View, Window, Button, Selection, or Tooltip. In reality, there really should be a Window Manager set too in order for the Common Colors pseudo-set to be true to its name. But again, this is a dev issue. ;) ============================================================================================= ============================================================================================= And that concludes my analysis. Sorry for the length, and also for not actually doing these changes myself, but I don't know how and besides these are really suggestions only. The last call is yours. ^^b Thank you for allowing me to use this as my first substantial contribution to KDE. It's not much, but I hope it's a start. ^___^ Cheers! --Arturo "C-quel" Silva On Tue, Sep 1, 2009 at 3:05 PM, Matthew Woehlke < mw_triad at users.sourceforge.net> wrote: > SVN commit 1018504 by mwoehlke: > > Update color kcm doc based on comments from Burkhard L?ck. > > Further comments/suggestions welcomed, please send to me and/or k-doc-en. > > CCMAIL: kde-doc-english at kde.org > > > M +46 -6 index.docbook > > > --- trunk/KDE/kdebase/workspace/doc/kcontrol/colors/index.docbook > #1018503:1018504 > @@ -147,18 +147,31 @@ > Colors > > The Colors tab allows you to change the colors > in > - a color scheme. The Common Colors set, which is > displayed > - initially, is not actually a "set" in the sense used by &kde; (see next > - section), but presents a number of color roles in a way that makes it > - easier to edit the scheme as a whole. When creating a new color scheme, > you > - will usually change these colors first, and use the other sets to tweak > - specific colors if needed. > + a color scheme. > > Creating or changing a scheme is a simple matter of clicking on the > swatch in the color list and selecting a new color. You can check your > changes at any time by pressing Apply. It is > suggested > that you save your scheme when you are done. > > + The Common Colors set, which is displayed > + initially, is not actually a "set" in the sense used by &kde; > (see > + next section), but presents a number of color roles in a way that makes > it > + easier to edit the scheme as a whole. When creating a new color scheme, > you > + will usually change these colors first, and use the other sets to tweak > + specific colors if needed. > + > + Note that Common Colors makes available roles > from > + all sets. For example, "View Background" here is shorthand for > the > + Normal Background role from the View set. Also, setting colors that do > not > + refer to a specific set will change that color in > all > + sets. (As an exception, "Inactive Text" will change the color > for > + all sets except for Selection; there is a separate > + "Selection Inactive Text" for Inactive Text in the Selection > set.) > + Some roles may not be visible under Common Colors > at > + all, and can only be changed (if needed) by selecting the appropriate > + set. > + > > Color Sets > > @@ -261,6 +274,32 @@ > The choice of color role is left to the developer; the above are > guidelines intended to represent typical usage. > > + > + > + Window Manager Roles > + > + As previously stated, the Window Manager set has its own roles, > + independent of those in other sets. These are (currently) only > accessible > + via Common Colors, and are as follows: > + > + > + Active Titlebar — > + used to draw the title bar background, borders, and/or decorations > for > + active window (that is, the one with input focus). Not all window > + decorations will use this in the same way, and some may even use > the > + Normal Background from the Window set to draw the title bar. > + > + Active Titlebar Text — > + used to draw the title bar text when Active Titlebar is used to > draw > + the title bar background. May also be used for other foreground > + elements which use Active Titlebar as the background. > + > + > + > + The Inactive Titlebar [Text] roles are the same as the above, > but for > + inactive windows, rather than active windows. > + > + > > > > @@ -350,6 +389,7 @@ > slider produces no change, while maximum causes the text to completely > disappear into the background. > > + > > > > _______________________________________________ > kde-doc-english mailing list > kde-doc-english at kde.org > https://mail.kde.org/mailman/listinfo/kde-doc-english > ------------------------------------------------------------- -- Burkhard L?ck From mwoehlke at tibco.com Wed Sep 2 17:33:55 2009 From: mwoehlke at tibco.com (Matthew Woehlke) Date: Wed, 02 Sep 2009 10:33:55 -0500 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> References: <1251831943.403902.8662.nullmailer@svn.kde.org> <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> Message-ID: <4A9E9063.8080908@tibco.com> Arturo Silva wrote: > Wow, since I rarely use this module (even in the 3.x days), I never realized > how flexible this was. > > Perhaps I'm using an old edition of the KDE Help Center (the Colors section > refers to a Revision 3.2), but I don't actually see this documentation > anywhere. Correct; the new version only hit svn a few days ago, so it isn't in 4.3.0. If you want to see it in khelpcenter, you'll need to build trunk. > So either I'm looking in the wrong place, or this revision is > old, or this is a new addition to that document. Either way, I couldn't > compare this to anything preexisting. The version being patched in the referenced commit didn't exist (publicly) until August 24, and then only in svn. You could compare the Sep 1 version against the Aug 24 version, I guess, but that's the point I made in our previous exchange; since this is a total rewrite, right now it is best to ignore the old (3.2) doc and just look at the whole thing as it is currently in svn. > Judging by the symbols, it seems this is only a DIFF from the source > document, so there are likely snippets here and there of unrelated > documentation left over. Right. The whole thing is here: http://websvn.kde.org/trunk/KDE/kdebase/workspace/doc/kcontrol/colors/index.docbook?view=markup On to your specific points... > In the line: > > + a custom scheme. > > I would suggest "custom scheme" if possible. The wording "color scheme" as > used in the sentence almost seemed to imply I could take any scheme from the > list (say, Magma), change it to all sorts of wacky colors, and then have > that scheme save permanently with said wacky colors. The reality, however, > is that the color changes will ONLY affect the virtual scheme called > "Current", which will not be permanent unless explicitly saved with the Save > Scheme button. Good point. I'm not very fond of "custom scheme" however, but I changed this line to "the active color scheme", a term which is explained above?. Do you think that is sufficient? (? "The 'active' scheme is the set of colors as has been most recently edited by you, i.e. what you would get if you choose [Apply].") > In the line: > > that you save your scheme when you are done. > > I would recommend referencing the Scheme tab, as in "save your scheme in the > Scheme tab". It sounds like an obsessive precaution, but it may not be > necessarily obvious to the initiate where the Save Scheme button is. That's reasonable. Changed as follows: - that you save your scheme when you are done. + that you save your scheme (via the Scheme tab) + when you are done. > The entire section from: > > + The Common Colors set, which is displayed > to > + all, and can only be changed (if needed) by selecting the appropriate > + set. > > ...is not technically wrong -- in fact, it's admirably detailed. However, > it does seem like it goes into too great length to explain what Common > Colors is, which, as I would describe it, is merely the "Simple View" of the > Colors tab, whereas the View, Window, Button, Selection and Tooltip combined > make up a kind of "Advanced View". Ironically, I made that change based on comments from Burkhard L?ck, generally in the vein that the things there explained were not explained before. I'm going to cross-post this part to -usability and see what they think as well. > I'm not sure what: > > The choice of color role is left to the developer; the above are > guidelines intended to represent typical usage. > > ...refers to unfortunately. :( Basically, that the use of the various roles, as described above this part, is advisory to developers, who may choose to ignore that advice. It could probably be worded better. I'll think about this; meanwhile, anyone else have ideas? > In the lines: > > + used to draw the title bar background, borders, and/or > decorations for > + active window (that is, the one with input focus). Not all > window > > I would add the "the" before "active window", so the phrase will read as > "used to draw the title bar background, borders, and/or decorations for the > active window...". Oops, yes, that's clearly a simple typo. Thanks for the catch! > For the section: > > + used to draw the title bar text when Active Titlebar is used to > draw > + the title bar background. May also be used for other foreground > + elements which use Active Titlebar as the background. > > I understand what it means, but I can't shake the feeling that "Active > Titlebar" alone sounds a bit broken. But I can't really say that "the > Active Titlebar role" will make it any better. :( Yes, the color role name is being used as a noun. I'm basically in agreement with everything you said. Maybe some other method, such as putting all role names in quotes, or making them bold, or some such, would be better? > Looking back on the entire section of Window Manager Roles, I can't help but > feel a small contradiction regarding the role of Common Colors, given it > does indeed contain UNIQUE elements not found in View, Window, Button, > Selection, or Tooltip. In reality, there really should be a Window Manager > set too in order for the Common Colors pseudo-set to be true to its name. > But again, this is a dev issue. ;) I could do that, but it would have four colors ;-). (At one point, there was thought of having rather more WM roles, but so far nothing has happened there.) The problem is that "common" here means more along the lines of "popular", not "shared"... an ambiguity in the English language. Any ideas on a better (less ambiguous) word? > And that concludes my analysis. Sorry for the length, No worries :-), the feedback is much appreciated. > Thank you for allowing me to use this as my first substantial contribution > to KDE. It's not much, but I hope it's a start. ^___^ :-D -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- Hey! Where's the witty punchline? (with apologies to Hostess) From lueck at hube-lueck.de Wed Sep 2 18:00:18 2009 From: lueck at hube-lueck.de (Burkhard =?utf-8?q?L=C3=BCck?=) Date: Wed, 2 Sep 2009 18:00:18 +0200 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <4A9E9063.8080908@tibco.com> References: <1251831943.403902.8662.nullmailer@svn.kde.org> <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> <4A9E9063.8080908@tibco.com> Message-ID: <200909021800.18799.lueck@hube-lueck.de> Am Mittwoch 02 September 2009 17:33:55 schrieb Matthew Woehlke: > Arturo Silva wrote: > > Wow, since I rarely use this module (even in the 3.x days), I never > > realized how flexible this was. > > > > Perhaps I'm using an old edition of the KDE Help Center (the Colors > > section refers to a Revision 3.2), but I don't actually see this > > documentation anywhere. > > Correct; the new version only hit svn a few days ago, so it isn't in > 4.3.0. If you want to see it in khelpcenter, you'll need to build trunk. > The documentation seems to apply also for branch, so I'd like to backport to 4.3 in a few days, so it could be in 4.3.2, Matthew, any objections? -- Burkhard L?ck From mw_triad at users.sourceforge.net Wed Sep 2 17:58:55 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Wed, 02 Sep 2009 10:58:55 -0500 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> References: <1251831943.403902.8662.nullmailer@svn.kde.org> <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> Message-ID: <4A9E963F.2060501@users.sourceforge.net> While discussing the doc for the color kcm, Arturo brought up an interesting point. I'd like to also ask y'all at -usability if you have anything to add. For reference, the latest doc version is here: http://websvn.kde.org/trunk/KDE/kdebase/workspace/doc/kcontrol/colors/index.docbook?view=markup Arturo Silva wrote: > The entire section from: > > + The Common Colors set, which is displayed > > to > > + all, and can only be changed (if needed) by selecting the appropriate > + set. > > ...is not technically wrong -- in fact, it's admirably detailed. However, > it does seem like it goes into too great length to explain what Common > Colors is, which, as I would describe it, is merely the "Simple View" of the > Colors tab, whereas the View, Window, Button, Selection and Tooltip combined > make up a kind of "Advanced View". > > Perhaps the detail is necessary after all since Common Colors is, > unfortunately, mixed in with the other sets and easy to confuse as one. > > Perhaps this is really more of a UI issue, and could be fixed if that color > set dropdown were replaced by a toggle between "Quickly Modify Common > Colors" and "Fine Tune Color Sets", the latter of which would enable the > dropdown with only View, Window, Button, Selection and Tooltip. Hmm... that might work. On the down side, it is harder to "switch modes"... but it might make things a bit less strange. Anyone else want to weigh in? (There are, in fact, some other advantages from a technical standpoint, but nothing the user would notice.) -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- Hey! Where's the witty punchline? (with apologies to Hostess) From mw_triad at users.sourceforge.net Wed Sep 2 18:09:12 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Wed, 02 Sep 2009 11:09:12 -0500 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <200909021800.18799.lueck@hube-lueck.de> References: <1251831943.403902.8662.nullmailer@svn.kde.org> <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> <4A9E9063.8080908@tibco.com> <200909021800.18799.lueck@hube-lueck.de> Message-ID: <4A9E98A8.1000108@users.sourceforge.net> Burkhard L?ck wrote: > Am Mittwoch 02 September 2009 17:33:55 schrieb Matthew Woehlke: >> Arturo Silva wrote: >>> Wow, since I rarely use this module (even in the 3.x days), I never >>> realized how flexible this was. >>> >>> Perhaps I'm using an old edition of the KDE Help Center (the Colors >>> section refers to a Revision 3.2), but I don't actually see this >>> documentation anywhere. >> Correct; the new version only hit svn a few days ago, so it isn't in >> 4.3.0. If you want to see it in khelpcenter, you'll need to build trunk. >> > The documentation seems to apply also for branch, so I'd like to backport to > 4.3 in a few days, so it could be in 4.3.2, > > Matthew, any objections? Not at all! The only reason I haven't done so is because I am not familiar with policy for backporting doc changes, especially major changes like this total rewrite :-). For now, feel free to do so. (Given some of the discussions going on, I expect there will be UI changes for 4.4, but so far that isn't the case.) I also committed the changes I'd made so far based on Arturo's comments, so you'd have those available. -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- Hey! Where's the witty punchline? (with apologies to Hostess) From lueck at hube-lueck.de Wed Sep 2 18:37:46 2009 From: lueck at hube-lueck.de (Burkhard =?utf-8?q?L=C3=BCck?=) Date: Wed, 2 Sep 2009 18:37:46 +0200 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <4A9E98A8.1000108@users.sourceforge.net> References: <1251831943.403902.8662.nullmailer@svn.kde.org> <200909021800.18799.lueck@hube-lueck.de> <4A9E98A8.1000108@users.sourceforge.net> Message-ID: <200909021837.46369.lueck@hube-lueck.de> Am Mittwoch 02 September 2009 18:09:12 schrieb Matthew Woehlke: > Burkhard L?ck wrote: > > Am Mittwoch 02 September 2009 17:33:55 schrieb Matthew Woehlke: > >> Arturo Silva wrote: > >>> Wow, since I rarely use this module (even in the 3.x days), I never > >>> realized how flexible this was. > >>> > >>> Perhaps I'm using an old edition of the KDE Help Center (the Colors > >>> section refers to a Revision 3.2), but I don't actually see this > >>> documentation anywhere. > >> > >> Correct; the new version only hit svn a few days ago, so it isn't in > >> 4.3.0. If you want to see it in khelpcenter, you'll need to build trunk. > > > > The documentation seems to apply also for branch, so I'd like to backport > > to 4.3 in a few days, so it could be in 4.3.2, > > > > Matthew, any objections? > > Not at all! The only reason I haven't done so is because I am not > familiar with policy for backporting doc changes, especially major > changes like this total rewrite :-). > Policy is simple: NO string change in branch, not even a one char typo fix is allowed (there are really good reasons for that). I'm allowed to break the documentation string freeze as usual in the last few years, but of course only with approval from our translators :-P > For now, feel free to do so. (Given some of the discussions going on, I > expect there will be UI changes for 4.4, but so far that isn't the case.) > > I also committed the changes I'd made so far based on Arturo's comments, > so you'd have those available. I'm just extracting the translation templates, so the top teams can pick it up tomorrow and notice problems, breaking a freeze requires double checking. -- Burkhard L?ck From jasilva28 at gmail.com Wed Sep 2 20:47:32 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Wed, 2 Sep 2009 14:47:32 -0400 Subject: [kde-doc-english] KDE/kdebase/workspace/doc/kcontrol/colors In-Reply-To: <4A9E98A8.1000108@users.sourceforge.net> References: <1251831943.403902.8662.nullmailer@svn.kde.org> <955730e10909011845s7d04a5bcua44a22f81945825a@mail.gmail.com> <4A9E9063.8080908@tibco.com> <200909021800.18799.lueck@hube-lueck.de> <4A9E98A8.1000108@users.sourceforge.net> Message-ID: <955730e10909021147mb5bf926h250246d657670542@mail.gmail.com> hi. ^^ Seem this is already being taken care of and seems to have resulted in some pretty possitive contributions. So I'll just supply residual comments to some things, as I'm in complete agreement with just about everything else.... ^^ >> Good point. I'm not very fond of "custom scheme" however, but I changed >> this line to "the active color scheme", a term which is explained >> above?. Do you think that is sufficient? More than sufficient! ^__^ >> That's reasonable. Changed as follows: Perfect! >> Yes, the color role name is being used as a noun. I'm basically in >> agreement with everything you said. Maybe some other method, such as >> putting all role names in quotes, or making them bold, or some such, >> would be better? I would say more towards the bolding idea, since it provides a visual reference to the reader that Active Titlebar is a full reference to the prior section. On the other hand, this would beg the question on whether additional elements in the help docs should be bolded as well, in which case this could be the proverbial can of worms. In all honesty, it's too minor a point (I'd rather we use the time to write new documentation that doesn't exist) so maybe we can leave as is. ^^b >> I could do that, but it would have four colors ;-). (At one point, there >> was thought of having rather more WM roles, but so far nothing has >> happened there.) >> The problem is that "common" here means more along the lines of >> "popular", not "shared"... an ambiguity in the English language. Any >> ideas on a better (less ambiguous) word? LOL! Yeah, I imagined it would be too tiny a color set. :P As for suggestions, the UI adjustment would pretty much take care of this to an extent (if it is feasible for implementation). As for alternative suggestions,... besides "General", can't really think of anything else that wouldn't sound out of place. ^^; >> Hmm... that might work. On the down side, it is harder to "switch >> modes"... but it might make things a bit less strange. Anyone else want >> to weigh in? >> (There are, in fact, some other advantages from a technical standpoint, >> but nothing the user would notice.) As long as I'm not a software developer myself, I generally try to refrain from suggesting things like this since I don't have a full comprehension of how much work this will entail. Something that sounds easy to implement may be anything but. :( Still, it was worth the suggestion I feel, and more so if you also point out there may also be technical advantages to this. Hopefully as I get exposed to more documentation and artwork, I might be able to offer similar UI "tweaks" that are at least a bit more surgical and doable than broad wish list items. >> Policy is simple: NO string change in branch, not even a one char typo >> fix is allowed (there are really good reasons for that). I guess in time I'll know what this means. ^__^; Thanks again for reviewing my feedback! --Arturo "C-quel" Silva From kubito at gmail.com Sat Sep 5 23:56:30 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Sat, 5 Sep 2009 18:56:30 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> Message-ID: <68c3445d0909051456w6a5b235amc2364e6c6224a3fe@mail.gmail.com> Hi there, I'm one of the Ark maintainers, and while looking at bug 206284, it came to my attention that there is a man page for ark which was written in 2005 and has never been updated. I was thinking of removing it altogether, as it is likely not to be kept up-to-date. I tried to look for some kind of policy for this over Techbase, but didn't find anything. So my question is whether I can freely remove that man page from kdeutils/doc/ark or if it should remain there, even if not up-to-date and likely to confuse some users (besides, not many KDE applications seem to have man pages). Cheers, Raphael From winter at kde.org Sun Sep 6 15:00:58 2009 From: winter at kde.org (Allen Winter) Date: Sun, 6 Sep 2009 09:00:58 -0400 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909051456w6a5b235amc2364e6c6224a3fe@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <68c3445d0909051456w6a5b235amc2364e6c6224a3fe@mail.gmail.com> Message-ID: <200909060900.58569.winter@kde.org> On Saturday 05 September 2009 5:56:30 pm Raphael Kubo da Costa wrote: > Hi there, > > I'm one of the Ark maintainers, and while looking at bug 206284, it > came to my attention that there is a man page for ark which was > written in 2005 and has never been updated. I was thinking of removing > it altogether, as it is likely not to be kept up-to-date. > > I tried to look for some kind of policy for this over Techbase, but > didn't find anything. So my question is whether I can freely remove > that man page from kdeutils/doc/ark or if it should remain there, even > if not up-to-date and likely to confuse some users (besides, not many > KDE applications seem to have man pages). > Raphael, I think we have general policy that "no documentation is better than wrong documentation". Personally, I like man pages and wish we had at least basic man pages for all the apps. But if don't want to support a man page for Ark, then certainly you should remove the old, outdated file(s). -Allen From kubito at gmail.com Sun Sep 6 20:13:48 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Sun, 6 Sep 2009 15:13:48 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909060900.58569.winter@kde.org> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <68c3445d0909051456w6a5b235amc2364e6c6224a3fe@mail.gmail.com> <200909060900.58569.winter@kde.org> Message-ID: <68c3445d0909061113n53601c08t6c21185f30269179@mail.gmail.com> 2009/9/6 Allen Winter : > On Saturday 05 September 2009 5:56:30 pm Raphael Kubo da Costa wrote: >> Hi there, >> >> I'm one of the Ark maintainers, and while looking at bug 206284, it >> came to my attention that there is a man page for ark which was >> written in 2005 and has never been updated. I was thinking of removing >> it altogether, as it is likely not to be kept up-to-date. >> >> I tried to look for some kind of policy for this over Techbase, but >> didn't find anything. So my question is whether I can freely remove >> that man page from kdeutils/doc/ark or if it should remain there, even >> if not up-to-date and likely to confuse some users (besides, not many >> KDE applications seem to have man pages). >> > Raphael, > > I think we have general policy that "no documentation is better than wrong documentation". > > Personally, I like man pages and wish we had at least basic man pages for all the apps. > But if don't want to support a man page for Ark, then certainly you should remove > the old, outdated file(s). Hi, Allen, Is it up to the application's maintainer to keep the man page and other pieces of documentation updated, or is there any way the doc team can help me? I could try to update the man page, but I've never done anything related to DocBook, nor do I think I'll remember to do that very often. Thanks, Raphael From lueck at hube-lueck.de Sun Sep 6 21:21:49 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Sun, 6 Sep 2009 21:21:49 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909061113n53601c08t6c21185f30269179@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909060900.58569.winter@kde.org> <68c3445d0909061113n53601c08t6c21185f30269179@mail.gmail.com> Message-ID: <200909062121.49931.lueck@hube-lueck.de> Am Sonntag 06 September 2009 20:13:48 schrieb Raphael Kubo da Costa: > 2009/9/6 Allen Winter : > > On Saturday 05 September 2009 5:56:30 pm Raphael Kubo da Costa wrote: > >> Hi there, > >> > >> I'm one of the Ark maintainers, and while looking at bug 206284, it > >> came to my attention that there is a man page for ark which was > >> written in 2005 and has never been updated. I was thinking of removing > >> it altogether, as it is likely not to be kept up-to-date. > >> > >> I tried to look for some kind of policy for this over Techbase, but > >> didn't find anything. So my question is whether I can freely remove > >> that man page from kdeutils/doc/ark or if it should remain there, even > >> if not up-to-date and likely to confuse some users (besides, not many > >> KDE applications seem to have man pages). > > > > Raphael, > > > > I think we have general policy that "no documentation is better than > > wrong documentation". > > > > Personally, I like man pages and wish we had at least basic man pages for > > all the apps. But if don't want to support a man page for Ark, then > > certainly you should remove the old, outdated file(s). > > Hi, Allen, > > Is it up to the application's maintainer to keep the man page and > other pieces of documentation updated, or is there any way the doc > team can help me? I could try to update the man page, but I've never > done anything related to DocBook, nor do I think I'll remember to do > that very often. > Raphael, just send some plain text with an updated man page, I can markup it quickly to docbook and move it into svn documentation and into the i18n tool chain. You don't need to deal with docbook. -- Burkhard L?ck From kevindrou at gmail.com Mon Sep 7 21:42:25 2009 From: kevindrou at gmail.com (kevin) Date: Mon, 07 Sep 2009 19:42:25 -0000 Subject: [kde-doc-english] kde translations Message-ID: <200908131313.39601.kevindrou@gmail.com> Hello, I'm a french kde user, I've been using kde for nearly 2 years (I'm now using debian sid with kde 4.3) and would like to help writting documentation. I may write English as well as French. I'm ready to start working as soon as you like. K?vin Drouault From kare.sars at iki.fi Tue Sep 8 22:47:59 2009 From: kare.sars at iki.fi (=?utf-8?q?K=C3=A5re=20S=C3=A4rs?=) Date: Tue, 08 Sep 2009 20:47:59 +0000 Subject: [kde-doc-english] extragear/graphics/skanlite Message-ID: <1252442879.958878.31280.nullmailer@svn.kde.org> SVN commit 1021322 by sars: GUI: Reorganize the settings dialog and add the possibility to specify a preview resolution. Make the "save preview" image scalable. Use m_ prefix for class member variables. M +1 -1 CMakeLists.txt AM ImageViewer.cpp [License: GPL (v2/3)] AM ImageViewer.h [License: GPL (v2/3)] M +1 -1 main.cpp M +303 -185 settings.ui M +114 -97 skanlite.cpp M +12 -10 skanlite.h http://websvn.kde.org/?view=rev&revision=1021322 From kubito at gmail.com Sat Sep 12 04:37:23 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Fri, 11 Sep 2009 23:37:23 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909062121.49931.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909060900.58569.winter@kde.org> <68c3445d0909061113n53601c08t6c21185f30269179@mail.gmail.com> <200909062121.49931.lueck@hube-lueck.de> Message-ID: <68c3445d0909111937o7eac938bybc5edff2c80330cd@mail.gmail.com> 2009/9/6 Burkhard L?ck : > Am Sonntag 06 September 2009 20:13:48 schrieb Raphael Kubo da Costa: >> 2009/9/6 Allen Winter : >> > On Saturday 05 September 2009 5:56:30 pm Raphael Kubo da Costa wrote: >> >> Hi there, >> >> >> >> I'm one of the Ark maintainers, and while looking at bug 206284, it >> >> came to my attention that there is a man page for ark which was >> >> written in 2005 and has never been updated. I was thinking of removing >> >> it altogether, as it is likely not to be kept up-to-date. >> >> >> >> I tried to look for some kind of policy for this over Techbase, but >> >> didn't find anything. So my question is whether I can freely remove >> >> that man page from kdeutils/doc/ark or if it should remain there, even >> >> if not up-to-date and likely to confuse some users (besides, not many >> >> KDE applications seem to have man pages). >> > >> > Raphael, >> > >> > I think we have general policy that "no documentation is better than >> > wrong documentation". >> > >> > Personally, I like man pages and wish we had at least basic man pages for >> > all the apps. But if don't want to support a man page for Ark, then >> > certainly you should remove the old, outdated file(s). >> >> Hi, Allen, >> >> Is it up to the application's maintainer to keep the man page and >> other pieces of documentation updated, or is there any way the doc >> team can help me? I could try to update the man page, but I've never >> done anything related to DocBook, nor do I think I'll remember to do >> that very often. >> > Raphael, > just send some plain text with an updated man page, I can markup it quickly to > docbook and move it into svn documentation and into the i18n tool chain. > > You don't need to deal with docbook. Hi there, Sorry for taking so long to answer. I'm finally attaching an updated man page. I'm not sure if the language is as friendly as possible, so feel free to edit it (or add/remove sections if necessary). I also merged the Authors and Author section. Also feel free to add yourself to the Authors list. When you're done, please let me know to close the bug report. Thanks! -------------- next part -------------- = NAME = ark - KDE Archiving tool = SYNOPSYS = ark [-b [-a] [-e]] [-c [-f suffix] [-p] [-t file]] [-d] [-o directory] = DESCRIPTION = Ark is a program for managing various compressed file formats within KDE. Archives can be viewed, extracted, created and modified with Ark. The program can handle various formats such as tar, gzip, bzip2, zip and rar (when the appropriate libraries or command-line programs are installed). = OPERATION MODES = Ark can be used either as a stand-alone GUI program as well as a command-line program in order to perform some specific tasks. If invoked without the -b (--batch) or -c (--add) options, Ark is started as a normal GUI program. When the -b (--batch) option is used, Ark can be used to extract the contents of one or more files directly from the command-line, without launching its GUI. When the -c (--add) option is used, Ark prompts for files that should be added to a new archive or to an existing archive. = OPTIONS = -d, --dialog Show a dialog for specifying the options for a batch or add operation. -o, --destination Default the extraction directory to . If not passed, the current path is used. Options for adding files -c, --add Query the user for an archive filename and add specified files to it. Quit when finished. -t, --add-to Add the specified files to 'filename'. Create archive if it does not exist. Quit when finished. -p, --changetofirstpath Change the current dir to the first entry and add all other entries relative to this one. -f, --autofilename Automatically choose a filename, with the selected suffix (for example rar, tar.gz, zip or any other supported types) Options for batch extraction: -b, --batch Use the batch interface instead of the usual dialog. This option is implied if more than one url is specified. -e, --autodestination The destination argument will be set to the path of the first file supplied. -a, --autosubfolder Archive contents will be read, and if detected to not be a single folder archive, a subfolder by the name of the archive will be created. = EXAMPLES = ark --batch archive.tar.bz2 Will extract archive.tar.bz2 into the current directory without showing any GUI. ark -b -d archive.tar.bz2 archive2.zip Will first show an extraction options dialog and then extract both archive.tar.bz2 and archive2.zip into the directory chosen in the dialog. ark --add-to my-archive.zip photo1.jpg text.txt Will create my-archive.zip if does not exist and then add photo1.jpg and text.txt to it. = AUTHORS = Ark is currently maintained by Harald Hvaal and Raphael Kubo da Costa . This man page was first written by Lauri Watts in 2005 for KDE 3.4, and was later updated in 2009 by Raphael Kubo da Costa From cannewilson at googlemail.com Sat Sep 12 10:04:40 2009 From: cannewilson at googlemail.com (Anne Wilson) Date: Sat, 12 Sep 2009 09:04:40 +0100 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909111937o7eac938bybc5edff2c80330cd@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909062121.49931.lueck@hube-lueck.de> <68c3445d0909111937o7eac938bybc5edff2c80330cd@mail.gmail.com> Message-ID: <200909120904.50112.cannewilson@googlemail.com> On Saturday 12 September 2009 03:37:23 Raphael Kubo da Costa wrote: > 2009/9/6 Burkhard L?ck : > > Am Sonntag 06 September 2009 20:13:48 schrieb Raphael Kubo da Costa: > >> 2009/9/6 Allen Winter : > >> > On Saturday 05 September 2009 5:56:30 pm Raphael Kubo da Costa wrote: > >> >> Hi there, > >> >> > >> >> I'm one of the Ark maintainers, and while looking at bug 206284, it > >> >> came to my attention that there is a man page for ark which was > >> >> written in 2005 and has never been updated. I was thinking of > >> >> removing it altogether, as it is likely not to be kept up-to-date. > >> >> > >> >> I tried to look for some kind of policy for this over Techbase, but > >> >> didn't find anything. So my question is whether I can freely remove > >> >> that man page from kdeutils/doc/ark or if it should remain there, > >> >> even if not up-to-date and likely to confuse some users (besides, not > >> >> many KDE applications seem to have man pages). > >> > > >> > Raphael, > >> > > >> > I think we have general policy that "no documentation is better than > >> > wrong documentation". > >> > > >> > Personally, I like man pages and wish we had at least basic man pages > >> > for all the apps. But if don't want to support a man page for Ark, > >> > then certainly you should remove the old, outdated file(s). > >> > >> Hi, Allen, > >> > >> Is it up to the application's maintainer to keep the man page and > >> other pieces of documentation updated, or is there any way the doc > >> team can help me? I could try to update the man page, but I've never > >> done anything related to DocBook, nor do I think I'll remember to do > >> that very often. > > > > Raphael, > > just send some plain text with an updated man page, I can markup it > > quickly to docbook and move it into svn documentation and into the i18n > > tool chain. > > > > You don't need to deal with docbook. > > Hi there, > > Sorry for taking so long to answer. I'm finally attaching an updated man > page. > > I'm not sure if the language is as friendly as possible, so feel free > to edit it (or add/remove sections if necessary). I also merged the > Authors and Author section. Also feel free to add yourself to the > Authors list. > > When you're done, please let me know to close the bug report. > > Thanks! From a user point of view, this man page is a diamond of unusual clarity. :-) Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20090912/6d0a18d4/attachment.sig From gringras at gmail.com Sat Sep 12 15:32:03 2009 From: gringras at gmail.com (Jonathan Taylor) Date: Sat, 12 Sep 2009 09:32:03 -0400 Subject: [kde-doc-english] Bible Time 1.6.5.1 Message-ID: <1252762323.9160.5.camel@jttaylor-laptop> Dear Reader: I have recently started using the Bible time software on my Ubuntu 9.04 laptop. I only speak English but, I have an Arabic Bible in my bible list. It keeps opening, I think as some type of cross reference. I don't need a Arabic Bible, but I can't get rid of it. It's rather distracting. Can you tell me how to get rid of it?? From ubuntu at martin-graesslin.com Sun Sep 13 13:36:47 2009 From: ubuntu at martin-graesslin.com (=?utf-8?q?Martin=20Gr=C3=A4=C3=9Flin?=) Date: Sun, 13 Sep 2009 11:36:47 +0000 Subject: [kde-doc-english] KDE/kdebase/workspace/kwin Message-ID: <1252841807.632695.14783.nullmailer@svn.kde.org> SVN commit 1022861 by graesslin: Here comes the new TabBox. It is a complete rewrite using a MVC approach. Here some highlights: * Models and Delegates for Clients and Desktops * Horizontal, vertical and tabular layout * Layout of one item can be configured by an XML definition * A desktop item can include a client list * An optional second list view showing only the selected item * A new KCM "kwintabbox" * An alternative TabBox with independent settings and keybindings * Optional Highlight Windows effect integration * List scrolls instead of removing items * Scroll wheel support * Cursor key support * Middle click on item closes window BUG: 195745 BUG: 197187 BUG: 201103 FEATURE: 118184 FEATURE: 156723 FEATURE: 177441 FEATURE: 182897 FEATURE: 193882 GUI: M +12 -2 CMakeLists.txt M +6 -0 client.cpp M +8 -0 client.h M +23 -15 effects/boxswitch/boxswitch.cpp M +3 -0 effects/boxswitch/boxswitch.h M +8 -2 effects/coverswitch/coverswitch.cpp M +2 -0 effects/coverswitch/coverswitch.h M +3 -2 effects/flipswitch/flipswitch.cpp M +1 -0 effects/flipswitch/flipswitch.h M +4 -0 effects/highlightwindow/highlightwindow.cpp M +4 -3 effects/presentwindows/presentwindows.cpp M +1 -0 effects/presentwindows/presentwindows.h M +1 -0 kcmkwin/CMakeLists.txt M +32 -26 kcmkwin/kwincompositing/main.cpp A kcmkwin/kwintabbox (directory) A kcmkwin/kwintabbox/CMakeLists.txt A kcmkwin/kwintabbox/kwintabbox.desktop A kcmkwin/kwintabbox/layoutconfig.cpp [License: GPL (v2+)] A kcmkwin/kwintabbox/layoutconfig.h [License: GPL (v2+)] A kcmkwin/kwintabbox/layoutconfig.ui A kcmkwin/kwintabbox/main.cpp [License: GPL (v2+)] A kcmkwin/kwintabbox/main.h [License: GPL (v2+)] A kcmkwin/kwintabbox/main.ui A kcmkwin/kwintabbox/previewhandlerimpl.cpp [License: GPL (v2+)] A kcmkwin/kwintabbox/previewhandlerimpl.h [License: GPL (v2+)] M +2 -0 kwinbindings.cpp M +7 -1 lib/kwinglobals.h A tabbox (directory) M +391 -898 tabbox.cpp M +64 -120 tabbox.h A tabbox/DefaultTabBoxLayouts.xml A tabbox/clientitemdelegate.cpp [License: GPL (v2+)] A tabbox/clientitemdelegate.h [License: GPL (v2+)] A tabbox/clientmodel.cpp [License: GPL (v2+)] A tabbox/clientmodel.h [License: GPL (v2+)] A tabbox/desktopitemdelegate.cpp [License: GPL (v2+)] A tabbox/desktopitemdelegate.h [License: GPL (v2+)] A tabbox/desktopmodel.cpp [License: GPL (v2+)] A tabbox/desktopmodel.h [License: GPL (v2+)] A tabbox/itemlayoutconfig.cpp [License: GPL (v2+)] A tabbox/itemlayoutconfig.h [License: GPL (v2+)] A tabbox/tabboxconfig.cpp [License: GPL (v2+)] A tabbox/tabboxconfig.h [License: GPL (v2+)] A tabbox/tabboxhandler.cpp [License: GPL (v2+)] A tabbox/tabboxhandler.h [License: GPL (v2+)] A tabbox/tabboxview.cpp [License: GPL (v2+)] A tabbox/tabboxview.h [License: GPL (v2+)] M +17 -2 useractions.cpp M +2 -2 workspace.cpp M +14 -4 workspace.h http://websvn.kde.org/?view=rev&revision=1022861 From lueck at hube-lueck.de Sun Sep 13 15:25:57 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-15?q?L=FCck?=) Date: Sun, 13 Sep 2009 15:25:57 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909120904.50112.cannewilson@googlemail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <68c3445d0909111937o7eac938bybc5edff2c80330cd@mail.gmail.com> <200909120904.50112.cannewilson@googlemail.com> Message-ID: <200909131525.57838.lueck@hube-lueck.de> Am Samstag 12 September 2009 10:04:40 schrieb Anne Wilson: > On Saturday 12 September 2009 03:37:23 Raphael Kubo da Costa wrote: [...] > > Hi there, > > > > Sorry for taking so long to answer. I'm finally attaching an updated man > > page. > > > > I'm not sure if the language is as friendly as possible, so feel free > > to edit it (or add/remove sections if necessary). I also merged the > > Authors and Author section. Also feel free to add yourself to the > > Authors list. > > > > When you're done, please let me know to close the bug report. > > If markup your text and commited to trunk. Please proofread it. Btw, entities for your names/emails are not in kdelibs/kdoctools/customization/entities/contributor.entities so far, what about adding them? Thanks a lot for updating the man page. There is also an index.docbook in kdeutils/doc/ark > > From a user point of view, this man page is a diamond of unusual clarity. > :-) > > Anne Anne, why do I have to approve all your mails to this list? Seems you use a not subscribed email address for sending the mails, right? -- Burkhard L?ck From kubito at gmail.com Sun Sep 13 19:15:06 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Sun, 13 Sep 2009 14:15:06 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909131525.57838.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <68c3445d0909111937o7eac938bybc5edff2c80330cd@mail.gmail.com> <200909120904.50112.cannewilson@googlemail.com> <200909131525.57838.lueck@hube-lueck.de> Message-ID: <68c3445d0909131015q6b5babcfs4ff825466573e38e@mail.gmail.com> 2009/9/13 Burkhard L?ck : > Am Samstag 12 September 2009 10:04:40 schrieb Anne Wilson: >> On Saturday 12 September 2009 03:37:23 Raphael Kubo da Costa wrote: > [...] >> > Hi there, >> > >> > Sorry for taking so long to answer. I'm finally attaching an updated man >> > page. >> > >> > I'm not sure if the language is as friendly as possible, so feel free >> > to edit it (or add/remove sections if necessary). I also merged the >> > Authors and Author section. Also feel free to add yourself to the >> > Authors list. >> > >> > When you're done, please let me know to close the bug report. >> > > > If markup your text and commited to trunk. > Please proofread it. It looks fine. Thank you very much! > Btw, entities for your names/emails are not in > kdelibs/kdoctools/customization/entities/contributor.entities so far, what > about adding them? > > Thanks a lot for updating the man page. > There is also an index.docbook in kdeutils/doc/ark Actually, this is where I start getting confused. Is there some article on Techbase or somewhere else with instructions and documentation about these files? Wrt contributor.entities: * When should I have added myself to contributor.entities? * Can I just add a line with my information? I see some blank lines there, so I don't know if I should skip one as well. Wrt index.docbook: * Is there some sort of docbook guide that's easy to understand? Whenever I open a docbook file I feel it's something mere mortals can't understand ;) Cheers. From lawaladekunle at gmail.com Mon Sep 14 09:53:03 2009 From: lawaladekunle at gmail.com (Lawal Adekunle) Date: Mon, 14 Sep 2009 08:53:03 +0100 Subject: [kde-doc-english] Bible Time 1.6.5.1 In-Reply-To: <1252762323.9160.5.camel@jttaylor-laptop> References: <1252762323.9160.5.camel@jttaylor-laptop> Message-ID: Hello Jonathan to remove the Arabic Bible (AraSVD) 1. Go to Edit the click on the Module Manager 2. Click on Remove/Archive, Click on the drop down for Biblical Texts and Arabic 3. Check the box under the Minus sign (-) column of AraSVD 4. Then click remove, Then click the yes button for the window that pops up. Regards On Sat, Sep 12, 2009 at 2:32 PM, Jonathan Taylor wrote: > > Dear Reader: > > I have recently started using the Bible time software on my Ubuntu 9.04 > laptop. I only speak English but, I have an Arabic Bible in my bible > list. It keeps opening, I think as some type of cross reference. I > don't need a Arabic Bible, but I can't get rid of it. It's rather > distracting. Can you tell me how to get rid of it?? > > _______________________________________________ > kde-doc-english mailing list > kde-doc-english at kde.org > https://mail.kde.org/mailman/listinfo/kde-doc-english > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.kde.org/pipermail/kde-doc-english/attachments/20090914/85de8426/attachment.htm From kde at spatium.org Sun Sep 13 19:06:03 2009 From: kde at spatium.org (Michal Svoboda) Date: Sun, 13 Sep 2009 19:06:03 +0200 (CEST) Subject: [kde-doc-english] [Bug 207273] New: sysadmin documentation for nepomuk Message-ID: https://bugs.kde.org/show_bug.cgi?id=207273 Summary: sysadmin documentation for nepomuk Product: docs Version: unspecified Platform: unspecified OS/Version: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kde-doc-english at kde.org ReportedBy: kde at spatium.org Version: (using KDE 4.3.1) Installed from: Unspecified I am unable to find any documentation of the semantic desktop/nepomuk/strigi machinery from the sysadmin's point of view. For a few basic examples, I was not able to find answers to these questions: 1) Where are tags/ratings stored? Where is the indexer's database stored? 2) How do these two relate? 3) Can the locations and/or methods of storage be configured? 4) How does one do backups of these storages? 5) What are the tools to manipulate/examine/repair those storages? 6) Can these storages be shared between users on the same machine? How? 7) Between users on the network? 8) Are there any access controls for those storages? How granular? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From annma at kde.org Mon Sep 14 13:00:25 2009 From: annma at kde.org (Anne-Marie Mahfouf) Date: Mon, 14 Sep 2009 13:00:25 +0200 (CEST) Subject: [kde-doc-english] [Bug 207273] sysadmin documentation for nepomuk In-Reply-To: References: Message-ID: <20090914110025.9B66B20716@immanuel.kde.org> https://bugs.kde.org/show_bug.cgi?id=207273 Anne-Marie Mahfouf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |annma at kde.org --- Comment #1 from Anne-Marie Mahfouf 2009-09-14 13:00:24 --- Where do you want that doc please? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From lueck at hube-lueck.de Mon Sep 14 16:20:30 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Mon, 14 Sep 2009 16:20:30 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909131015q6b5babcfs4ff825466573e38e@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909131525.57838.lueck@hube-lueck.de> <68c3445d0909131015q6b5babcfs4ff825466573e38e@mail.gmail.com> Message-ID: <200909141620.30798.lueck@hube-lueck.de> Am Sonntag 13 September 2009 19:15:06 schrieb Raphael Kubo da Costa: > > Actually, this is where I start getting confused. Is there some > article on Techbase or somewhere else with instructions and > documentation about these files? > http://techbase.kde.org/Projects/Documentation http://l10n.kde.org/docs/ > Wrt contributor.entities: > * When should I have added myself to contributor.entities? When an entity is used more than one time, that happens already in the translations around 15 times. > * Can I just add a line with my information? I see some blank lines > there, so I don't know if I should skip one as well. > The list is sorted by family name, blank lines are used as separator to group the entries with the same first char of the family name. > Wrt index.docbook: > * Is there some sort of docbook guide that's easy to understand? > Whenever I open a docbook file I feel it's something mere mortals > can't understand ;) > That's my feeling opening source files;-) Just write in any format you like,- plain text preferred - because that could be used for the docbooks as for userbase.kde.org. -- Burkhard L?ck From kde at spatium.org Mon Sep 14 16:22:09 2009 From: kde at spatium.org (Michal Svoboda) Date: Mon, 14 Sep 2009 16:22:09 +0200 (CEST) Subject: [kde-doc-english] [Bug 207273] sysadmin documentation for nepomuk In-Reply-To: References: Message-ID: <20090914142209.84417205D5@immanuel.kde.org> https://bugs.kde.org/show_bug.cgi?id=207273 --- Comment #2 from Michal Svoboda 2009-09-14 16:22:08 --- (In reply to comment #1) > Where do you want that doc please? I'd prefer a googlable location, plus a link at http://nepomuk.kde.org/node/2 (ie. nepomuk->documentation) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From mw_triad at users.sourceforge.net Mon Sep 14 21:32:57 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Mon, 14 Sep 2009 14:32:57 -0500 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909141620.30798.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909131525.57838.lueck@hube-lueck.de> <68c3445d0909131015q6b5babcfs4ff825466573e38e@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> Message-ID: Burkhard ? wrote: /me wonders why Burkhard's last name is an unprintable character :-) > Am Sonntag 13 September 2009 19:15:06 schrieb Raphael Kubo da Costa: >> Wrt contributor.entities: >> * When should I have added myself to contributor.entities? > > When an entity is used more than one time, that happens already in the > translations around 15 times. Um... really? If so I did it wrong, I thought that was more-or-less the list of authors. (Though, if only for single-point-of-maintenance, I think I would disagree with "more than one time" here...) -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- "Microsoft doesn't really care about users." -- Robert Cringely From lueck at hube-lueck.de Mon Sep 14 22:11:07 2009 From: lueck at hube-lueck.de (Burkhard =?utf-8?q?L=C3=BCck?=) Date: Mon, 14 Sep 2009 22:11:07 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> Message-ID: <200909142211.07505.lueck@hube-lueck.de> Am Montag 14 September 2009 21:32:57 schrieb Matthew Woehlke: > Burkhard ? wrote: > > /me wonders why Burkhard's last name is an unprintable character :-) > > > Am Sonntag 13 September 2009 19:15:06 schrieb Raphael Kubo da Costa: > >> Wrt contributor.entities: > >> * When should I have added myself to contributor.entities? > > > > When an entity is used more than one time, that happens already in the > > translations around 15 times. > > Um... really? If so I did it wrong, I thought that was more-or-less the > list of authors. (Though, if only for single-point-of-maintenance, I > think I would disagree with "more than one time" here...) > Hmm, your entity is in contributor.entities in trunk, so you did it right. Imaging you would like to write your name with pretty, but sometimes unprintable "?" instead of "oe", just change the entity in kdelbs. Then each time a documentation and it's translattion is build and installed, this change is spread into all installed files, even into the translations. -- Burkhard L?ck From mw_triad at users.sourceforge.net Mon Sep 14 22:22:41 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Mon, 14 Sep 2009 15:22:41 -0500 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909142211.07505.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> <200909142211.07505.lueck@hube-lueck.de> Message-ID: Burkhard L?ck wrote: > Am Montag 14 September 2009 21:32:57 schrieb Matthew Woehlke: >> Burkhard ? wrote: >>> Am Sonntag 13 September 2009 19:15:06 schrieb Raphael Kubo da Costa: >>>> Wrt contributor.entities: >>>> * When should I have added myself to contributor.entities? >>> When an entity is used more than one time, that happens already in the >>> translations around 15 times. >> Um... really? If so I did it wrong, I thought that was more-or-less the >> list of authors. (Though, if only for single-point-of-maintenance, I >> think I would disagree with "more than one time" here...) >> > Hmm, your entity is in contributor.entities in trunk, so you did it right. > > Imaging you would like to write your name with pretty, but sometimes > unprintable "?" instead of "oe", just change the entity in kdelbs. > Then each time a documentation and it's translattion is build and installed, > this change is spread into all installed files, even into the translations. Yes, exactly my point. So I am confused, one /should/ add themselves to contributor.entities right away, or wait until their name is used more than once? (Well, if you count translations, I guess there is no such thing as "once"?) (In my case, as a native of that horribly backwards country which bestowed on me the en_US language, I don't even pronounce my last name anywhere close to the "proper German", much less have any desire to spell it W?hlke? :-), which it hasn't been for a few generations at least.) (? Wow, that looks odd... ;-) ) -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- "Microsoft doesn't really care about users." -- Robert Cringely From lueck at hube-lueck.de Tue Sep 15 07:59:38 2009 From: lueck at hube-lueck.de (Burkhard =?utf-8?q?L=C3=BCck?=) Date: Tue, 15 Sep 2009 07:59:38 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909142211.07505.lueck@hube-lueck.de> Message-ID: <200909150759.38880.lueck@hube-lueck.de> Am Montag 14 September 2009 22:22:41 schrieb Matthew Woehlke: > > Yes, exactly my point. So I am confused, one /should/ add themselves to > contributor.entities right away, or wait until their name is used more > than once? (Well, if you count translations, I guess there is no such > thing as "once"?) > You are right, there is no single use for that. So an entity should be added the first time name + mail are used in docbooks. -- Burkhard L?ck From kubito at gmail.com Tue Sep 15 19:30:50 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Tue, 15 Sep 2009 14:30:50 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909141620.30798.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909131525.57838.lueck@hube-lueck.de> <68c3445d0909131015q6b5babcfs4ff825466573e38e@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> Message-ID: <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> 2009/9/14 Burkhard L?ck : > Am Sonntag 13 September 2009 19:15:06 schrieb Raphael Kubo da Costa: >> ?* Can I just add a line with my information? I see some blank lines >> there, so I don't know if I should skip one as well. >> > The list is sorted by family name, blank lines are used as separator to group > the entries with the same first char of the family name. I see Danny Allen and Albert Astals Cid in the same group as Thorsten Zachmann and other people whose family name begins with "Z". Is this expected? And should I add myself to "C" or "K"? From mw_triad at users.sourceforge.net Tue Sep 15 18:32:10 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Tue, 15 Sep 2009 11:32:10 -0500 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909150759.38880.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909142211.07505.lueck@hube-lueck.de> <200909150759.38880.lueck@hube-lueck.de> Message-ID: Burkhard L?ck wrote: > Am Montag 14 September 2009 22:22:41 schrieb Matthew Woehlke: >> Yes, exactly my point. So I am confused, one /should/ add themselves to >> contributor.entities right away, or wait until their name is used more >> than once? (Well, if you count translations, I guess there is no such >> thing as "once"?) >> > You are right, there is no single use for that. > So an entity should be added the first time name + mail are used in docbooks. Okay, good to know. Thanks. -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- You're on your own for the pony. -- Richard Hughes, on feature requests From lueck at hube-lueck.de Tue Sep 15 20:02:19 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Tue, 15 Sep 2009 20:02:19 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> Message-ID: <200909152002.19433.lueck@hube-lueck.de> Am Dienstag 15 September 2009 19:30:50 schrieb Raphael Kubo da Costa: > 2009/9/14 Burkhard L?ck : > > Am Sonntag 13 September 2009 19:15:06 schrieb Raphael Kubo da Costa: > >> * Can I just add a line with my information? I see some blank lines > >> there, so I don't know if I should skip one as well. > > > > The list is sorted by family name, blank lines are used as separator to > > group the entries with the same first char of the family name. > > I see Danny Allen and Albert Astals Cid in the same group as Thorsten > Zachmann and other people whose family name begins with "Z". Is this > expected? > Seems both did not read the header of the file: "Please keep the list sorted on the family name" And sinply added their names at the end. > And should I add myself to "C" or "K"? > Uh, good question. but what's your family name? "Kubo da Costa"? I'd say it does not matter ;-) -- Burkhard L?ck From mw_triad at users.sourceforge.net Tue Sep 15 20:20:11 2009 From: mw_triad at users.sourceforge.net (Matthew Woehlke) Date: Tue, 15 Sep 2009 13:20:11 -0500 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909152002.19433.lueck@hube-lueck.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> <200909152002.19433.lueck@hube-lueck.de> Message-ID: (Please do not quote my e-mail address unobfuscated in message bodies.) Burkhard ? wrote: > Am Dienstag 15 September 2009 19:30:50 schrieb Raphael Kubo da Costa: >> should I add myself to "C" or "K"? > > Uh, good question. but what's your family name? > "Kubo da Costa"? > > I'd say it does not matter ;-) Well, it should be the first letter of 'surname', no? I assume 'Raphael' is correct. Which is correct for the rest?: 1. Kubo da Costa 2. Kuboda Costa 3. Kubo daCosta 4. something else? Note that (2) would mean sorting under 'd' :-). -- Matthew You're on your own for the pony. -- Richard Hughes, on feature requests From kubito at gmail.com Tue Sep 15 20:33:23 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Tue, 15 Sep 2009 15:33:23 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> <200909152002.19433.lueck@hube-lueck.de> Message-ID: <68c3445d0909151133o6fa4003g11a04999eea692c@mail.gmail.com> 2009/9/15 Matthew Woehlke : > (Please do not quote my e-mail address unobfuscated in message bodies.) > > Burkhard ? wrote: >> Am Dienstag 15 September 2009 19:30:50 schrieb Raphael Kubo da Costa: >>> should I add myself to "C" or "K"? >> >> Uh, good question. but what's your family name? >> "Kubo da Costa"? >> >> I'd say it does not matter ;-) > > Well, it should be the first letter of 'surname', no? > > I assume 'Raphael' is correct. Which is correct > for the rest?: > > 1. Kubo da Costa > 2. Kuboda Costa > 3. Kubo daCosta > 4. something else? > > Note that (2) would mean sorting under 'd' :-). That's something I've never thought of ;) I think everything else besides Raphael can be considered my surname. However, I also think that if I were to publish something I'd probably be indexed as "Costa, Raphael K." or something similar. From michael at michael-skiba.de Wed Sep 16 00:26:59 2009 From: michael at michael-skiba.de (Michael Skiba) Date: Wed, 16 Sep 2009 00:26:59 +0200 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> Message-ID: <200909160027.03316.michael@michael-skiba.de> Am Dienstag 15 September 2009 19:30:50 schrieb Raphael Kubo da Costa: > I see Danny Allen and Albert Astals Cid in the same group as Thorsten > Zachmann and other people whose family name begins with "Z". Is this > expected? > > And should I add myself to "C" or "K"? Where do you find yourself in the telephonebook? ;) Regards, Michael -- You are always doing something marginal when the boss drops by your desk. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20090916/4487a230/attachment.sig From jjesse at gmail.com Wed Sep 16 03:55:25 2009 From: jjesse at gmail.com (Jonathan Jesse) Date: Tue, 15 Sep 2009 21:55:25 -0400 Subject: [kde-doc-english] KDE User Guide outdated? Message-ID: Was looking at the help system the other day and noticed how out of date the KDE User Guide is. Is it worth taking a look at updating this guide as a big project? Or should I just move on? Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.kde.org/pipermail/kde-doc-english/attachments/20090915/973ea1aa/attachment.htm From jasilva28 at gmail.com Wed Sep 16 04:47:40 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Tue, 15 Sep 2009 22:47:40 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: References: Message-ID: <955730e10909151947xa649388v24a7f3258c417869@mail.gmail.com> On Tue, Sep 15, 2009 at 9:55 PM, Jonathan Jesse wrote: > Was looking at the help system the other day and noticed how out of date the > KDE User Guide is. Is it worth taking a look at updating this guide as a > big project? Or should I just move on? Hi there. :) Ah! Would that by any chance be the document that, at least in my distribution, reads: "Revision 0.0.1 (2004-06-16), Copyright ? 2004, 2005 The KDE Documentation Team"? :) Yeah, I think that looks... just a wee bit outdated. :D It's also fairly large, though, so not something that can be updated overnight unless divided up between various people. There's plenty of screenshots that can be updated, though not unfortunately all of them can be without first updating the adjacent text (e.g., the File Manager section naturally pours over Konqueror instead of Dolphin). From kubito at gmail.com Wed Sep 16 14:39:55 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Wed, 16 Sep 2009 09:39:55 -0300 Subject: [kde-doc-english] Outdated man page policy? In-Reply-To: <200909160027.03316.michael@michael-skiba.de> References: <68c3445d0909051452x55342df7n8db9822a54c5548@mail.gmail.com> <200909141620.30798.lueck@hube-lueck.de> <68c3445d0909151030l6dd55d37mc16ec03880c28cb3@mail.gmail.com> <200909160027.03316.michael@michael-skiba.de> Message-ID: <68c3445d0909160539rf3fb9dfv53bc85fb3cbfe33e@mail.gmail.com> 2009/9/15 Michael Skiba : > Am Dienstag 15 September 2009 19:30:50 schrieb Raphael Kubo da Costa: >> I see Danny Allen and Albert Astals Cid in the same group as Thorsten >> Zachmann and other people whose family name begins with "Z". Is this >> expected? >> >> And should I add myself to "C" or "K"? > > Where do you find yourself in the telephonebook? ;) Still on this matter: I was adding myself to "C", and saw the tag. Should I add "Kubo da" do or just add everything after Raphael to surname? From jasilva28 at gmail.com Fri Sep 18 03:26:16 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Thu, 17 Sep 2009 21:26:16 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909151947xa649388v24a7f3258c417869@mail.gmail.com> References: <955730e10909151947xa649388v24a7f3258c417869@mail.gmail.com> Message-ID: <955730e10909171826u5c66dbf4y2b8262160573f9c@mail.gmail.com> Hello again, I've actually been learning a bit more about how the SVN repositories worked and successfully managed to find where the User Guide is stored at in KDE4's trunk repository. Here it is using the WebSVN viewer: http://websvn.kde.org/trunk/KDE/kdebase/runtime/doc/userguide/ The actual files can be downloaded to your computer either by using this command in the test directory of your choice: svn co -N svn://anonsvn.kde.org/trunk/kdebase/runtime/doc Or by opening svn://anonsvn.kde.org/trunk/kdebase/runtime/doc in the KDESVN graphical client (as seen in the attached). The actual helpcenter manuals are stored here in your system: /usr/share/doc/kde/HTML/en/khelpcenter About the only thing I have not figured out yet is how to edit the DocBook files graphically or how to open them without overwriting the existing DocBooks. Hopefully someone can chime in there. =============== That issue aside, updating the User Manual (or for that matter the Quick Start Guide or Visual Dictionary) does look more and more possible, although clearly this is still a long-term thing. If there are no objections, I wouldn't mind at least starting to update a few of these pages. I figure it would be good practice for doing SVN commits and the like, and maybe to learn more things about KDE4 that I may have never noticed before. Some thoughts on the matter would be appreciated. Thanks! --Arturo "C-quel" Silva -------------- next part -------------- A non-text attachment was scrubbed... Name: snapshot8.png Type: image/png Size: 148454 bytes Desc: not available Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20090917/d6097774/attachment.png From yurchor at ukr.net Fri Sep 18 07:45:16 2009 From: yurchor at ukr.net (Yuri Chornoivan) Date: Fri, 18 Sep 2009 08:45:16 +0300 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909171826u5c66dbf4y2b8262160573f9c@mail.gmail.com> References: <955730e10909151947xa649388v24a7f3258c417869@mail.gmail.com> <955730e10909171826u5c66dbf4y2b8262160573f9c@mail.gmail.com> Message-ID: ?? Fri, 18 Sep 2009 04:26:16 +0300, Arturo Silva ???????: Hi! > About the only thing I have not figured out yet is how to edit the > DocBook files graphically or how to open them without overwriting the > existing DocBooks. Hopefully someone can chime in there. > You can try Syntext Serna Free (it is open source WYSIWYG XML editor). http://www.syntext.com/products/serna-free/ Best regards, Yuri From jasilva28 at gmail.com Fri Sep 18 07:52:56 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Fri, 18 Sep 2009 01:52:56 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: References: <955730e10909151947xa649388v24a7f3258c417869@mail.gmail.com> <955730e10909171826u5c66dbf4y2b8262160573f9c@mail.gmail.com> Message-ID: <955730e10909172252i6576613akcc08afa3c035e3bc@mail.gmail.com> On Fri, Sep 18, 2009 at 1:45 AM, Yuri Chornoivan wrote: > > > You can try Syntext Serna Free (it is open source WYSIWYG XML editor). > > http://www.syntext.com/products/serna-free/ > Aaaah! Eureka! This looks nice! ^__^b Course since you brought it up, I guess I'll take that as one vote that for "Yes", it's okay for me to try updating the User Manual. Now I'm hopeful. ^___^v Just so I don't get too ambitious at first (I am a bit sick at the moment), I figure I'll try updating the Visual Dictionary first. Maybe by end of next week. ^^b --Arturo From kubito at gmail.com Sat Sep 19 05:17:09 2009 From: kubito at gmail.com (Raphael Kubo da Costa) Date: Sat, 19 Sep 2009 03:17:09 +0000 Subject: [kde-doc-english] KDE/kdelibs/kdoctools/customization/entities Message-ID: <1253330229.686619.6022.nullmailer@svn.kde.org> SVN commit 1025552 by rkcosta: Add Harald Hvaal and myself to the contributor list. CCMAIL: kde-doc-english at kde.org CCMAIL: haraldhv at stud.ntnu.no M +4 -0 contributor.entities --- trunk/KDE/kdelibs/kdoctools/customization/entities/contributor.entities #1025551:1025552 @@ -83,6 +83,8 @@ cimrman3 at students.zcu.cz'> JohnCirillo'> '> +RaphaelKubo daCosta'> +kubito at gmail.com'> ClaudiuCostin'> claudiuc at kde.org'> NealCrook'> @@ -198,6 +200,8 @@ '> ChrisHowells'> howells at kde.org'> +HaraldHvaal'> +haraldhv at stud.ntnu.no'> GeertJansen'> g.t.jansen at stud.tue.nl'> From rjohnson at kde.org Sat Sep 19 05:52:40 2009 From: rjohnson at kde.org (Richard JOHNSON) Date: Fri, 18 Sep 2009 22:52:40 -0500 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: References: Message-ID: <20090919035240.GJ27621@3LockBox> On Tue, Sep 15, 2009 at 09:55:25PM -0400, Jonathan Jesse wrote: > Was looking at the help system the other day and noticed how out of date the > KDE User Guide is. Is it worth taking a look at updating this guide as a > big project? Or should I just move on? > > Jonathan I have this on my TODO list, but I would be more than happy for you to help out on it, or if you want to, take it on. You know what to do, and yes it is definitely worth it. -- Name| Richard JOHNSON Title| Developer WWW| http://kde.org Email| rjohnson at kde.org GnuPG| 3578 0981 A21D D662 2A96 7623 F4C1 838C D8C4 4738 Home| http://www.nixternal.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: Digital signature Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20090918/7a84ccaf/attachment.sig From jasilva28 at gmail.com Sat Sep 19 05:58:54 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Fri, 18 Sep 2009 23:58:54 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <20090919035240.GJ27621@3LockBox> References: <20090919035240.GJ27621@3LockBox> Message-ID: <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> On Fri, Sep 18, 2009 at 11:52 PM, Richard JOHNSON wrote: > > I have this on my TODO list, but I would be more than happy for you to help > out on it, or if you want to, take it on. You know what to do, and yes it > is definitely worth it. Hi! Sure, I'd love to at least try -- there's certainly nothing to be lost in trying, other than that I'd save you the work of doing some of the screenshots! :P I don't want to overestimate my capacity (as I am relatively new), so I will certainly start small with the Visual Dictionary first, and then maybe the Quick Start. If those go well, then I'll be happy to help you with the big fish. :D --Arturo From stickler at online.de Sat Sep 19 11:13:33 2009 From: stickler at online.de (Karl-Heinz Stickler) Date: Sat, 19 Sep 2009 11:13:33 +0200 Subject: [kde-doc-english] authentication f not supported Message-ID: <200909191113.33424.stickler@online.de> How i can solve this problem ? best regards From lueck at hube-lueck.de Sat Sep 19 19:37:37 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Sat, 19 Sep 2009 19:37:37 +0200 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> References: <20090919035240.GJ27621@3LockBox> <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> Message-ID: <200909191937.37656.lueck@hube-lueck.de> Am Samstag 19 September 2009 05:58:54 schrieb Arturo Silva: > On Fri, Sep 18, 2009 at 11:52 PM, Richard JOHNSON wrote: > > I have this on my TODO list, but I would be more than happy for you to > > help out on it, or if you want to, take it on. You know what to do, and > > yes it is definitely worth it. > > Hi! Sure, I'd love to at least try -- there's certainly nothing to be > lost in trying, other than that I'd save you the work of doing some of > the screenshots! :P > > I don't want to overestimate my capacity (as I am relatively new), so > I will certainly start small with the Visual Dictionary first, and > then maybe the Quick Start. If those go well, then I'll be happy to > help you with the big fish. :D > Yep, updating Visual Dictionary + Quick Start with new screenshots is a good start for the kdebase docs. Please go ahead. -- Burkhard L?ck From rjohnson at kde.org Sun Sep 20 18:33:20 2009 From: rjohnson at kde.org (Richard JOHNSON) Date: Sun, 20 Sep 2009 11:33:20 -0500 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> References: <20090919035240.GJ27621@3LockBox> <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> Message-ID: <20090920163320.GL27621@3LockBox> On Fri, Sep 18, 2009 at 11:58:54PM -0400, Arturo Silva wrote: [...] > Hi! Sure, I'd love to at least try -- there's certainly nothing to be > lost in trying, other than that I'd save you the work of doing some of > the screenshots! :P That would be awesome! and greatly appreciated. > I don't want to overestimate my capacity (as I am relatively new), so > I will certainly start small with the Visual Dictionary first, and > then maybe the Quick Start. If those go well, then I'll be happy to > help you with the big fish. :D Do not hesitate to ask any questions here or join us in #kde-docs on IRC. You can get a hold of someone every now and then in there :) -- Name| Richard JOHNSON Title| Developer WWW| http://kde.org Email| rjohnson at kde.org GnuPG| 3578 0981 A21D D662 2A96 7623 F4C1 838C D8C4 4738 Home| http://www.nixternal.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: Digital signature Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20090920/0ca32a79/attachment.sig From erickwessels at home.nl Sun Sep 20 16:12:07 2009 From: erickwessels at home.nl (Erick Wessels) Date: Sun, 20 Sep 2009 16:12:07 +0200 Subject: [kde-doc-english] Basket in Kontact Message-ID: <200909201612.07682.erickwessels@home.nl> hello Devs; First and foremost, I want to thank you for the beautiful KONTACT, with the PIM and KMail etc. etc. Now... I use the OS LINUX PARDUS 2009 with KDE 4.2 I did herefore use Pardus 2007 and 2008, and in BOTH 07 and 08 with KDE 3.5, it was so, that the application BASKET was inplemented and worked in KONTACT..! Now I use Basket again, and this is not so!!! How can I implement this??!! And I miss the insert on the taskbar, where I could pick anythig (images or text) in webbrowsers, and so on..... Please can you help me with this...!?? With the best regards; -- ERICK-PARDUS WESSELS per dolorem ad veritatem ;-) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.kde.org/pipermail/kde-doc-english/attachments/20090920/23c5ff08/attachment.htm From jjesse at gmail.com Mon Sep 21 03:17:21 2009 From: jjesse at gmail.com (Jonathan Jesse) Date: Sun, 20 Sep 2009 21:17:21 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <20090920163320.GL27621@3LockBox> References: <20090919035240.GJ27621@3LockBox> <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> <20090920163320.GL27621@3LockBox> Message-ID: On Sun, Sep 20, 2009 at 12:33 PM, Richard JOHNSON wrote: > On Fri, Sep 18, 2009 at 11:58:54PM -0400, Arturo Silva wrote: > [...] > > Hi! Sure, I'd love to at least try -- there's certainly nothing to be > > lost in trying, other than that I'd save you the work of doing some of > > the screenshots! :P > > That would be awesome! and greatly appreciated. > > > I don't want to overestimate my capacity (as I am relatively new), so > > I will certainly start small with the Visual Dictionary first, and > > then maybe the Quick Start. If those go well, then I'll be happy to > > help you with the big fish. :D > > Do not hesitate to ask any questions here or join us in #kde-docs on IRC. > You can get a hold of someone every now and then in there :) > > -- > Name| Richard JOHNSON > Title| Developer > WWW| http://kde.org > Email| rjohnson at kde.org > GnuPG| 3578 0981 A21D D662 2A96 7623 F4C1 838C D8C4 4738 > Home| http://www.nixternal.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iQIcBAEBAgAGBQJKtllQAAoJEPTBg4zYxEc4zLMP/3yroUxCkcNgZDxn60LL814t > lKUvd8zDB/Pf1xNYKjqhoCavLENZ0ZGU9k6MndzxweDZZXIjfolvyIdUv7lenayi > 3DAMf3LYpeOlHLjfxh63BPru34UPt4IGgr05H5nzIKr4LELTRi/igfGYfiqDDwVd > cK9o/VOS9yhxRI07bynciquFrggIxagrbq2yH6fu89RhLL2FNMjVdAikz/9pDBON > e/6NbP4rroEAD1hNZPmWv7tfAYHgI34FiTO+C0ou6BfE3V9Wl5RvV7B6plDCFL8X > gO1GtA1DL22GDJQlzjlVPe33NFmnW2IamRs2yTDFi0ZW0NXX4neLTGHCxluezy6U > tI/pXF5IxPnaSMHvew/Um0QLpf9YvpkDAeRHpEmDrVvOdByjmkm+Gz2EzUd18m3X > yk77m2lZ9fq3ZdHI7O1QmCyetwgiatrvrlCxvX4sIP/NuV9/65SAHUQwC2k5rtMy > N8oaBKRkey7nnupCh0FYuFGGE+D3DBxvFPYnj7BvDEqOH6IjFIIO1k4TSjBnv/rk > b4jJuM+abCEWOBGawUrTVWbUKNWUh+tDRsw5uosd2CypPry/G1Y+FhnejwYJqLbn > iwN5hZQxZIgjNTyAj7BEpbHs6aYZS6ZXr5uVIIiSCiWtan02l1eVJNE+H1E2f7ex > w+hWAkC3ctdMhDa6UB6t > =pBX9 > -----END PGP SIGNATURE----- > > _______________________________________________ > kde-doc-english mailing list > kde-doc-english at kde.org > https://mail.kde.org/mailman/listinfo/kde-doc-english > > Volunteering my service on this as well, is there a wiki we could start dividing up the sections that need to be updated and get this rockin and rolling. Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.kde.org/pipermail/kde-doc-english/attachments/20090920/1f25673d/attachment.htm From jasilva28 at gmail.com Mon Sep 21 04:19:44 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Sun, 20 Sep 2009 22:19:44 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: References: <20090919035240.GJ27621@3LockBox> <955730e10909182058x43476bc1p9757b29c0863746a@mail.gmail.com> <20090920163320.GL27621@3LockBox> Message-ID: <955730e10909201919w26f770c5qf64efcee43912629@mail.gmail.com> On Sat, Sep 19, 2009 at 1:37 PM, Burkhard L?ck wrote: > > Yep, updating Visual Dictionary + Quick Start with new screenshots is a good > start for the kdebase docs. > > Please go ahead. And that's two votes! Thank ye, I'll go ahead with it then. I'll aim for a Friday release, although I should warn I'm also assisting the Oxygen team, as well as one or two KDE game projects too. I guess I got too overzealous with my first contributions. ^^' On Sun, Sep 20, 2009 at 12:33 PM, Richard JOHNSON wrote: > > Do not hesitate to ask any questions here or join us in #kde-docs on IRC. > You can get a hold of someone every now and then in there :) > Ooh, I'm usually full of hesitation when it comes to IRC (can't really afford much schedule disruption, especially if I get engrossed in chat sessions). But I will keep that in mind once I start getting a little more active -- right now I feel I'm barely getting warmed up. ^^ On Sun, Sep 20, 2009 at 9:17 PM, Jonathan Jesse wrote: > > Volunteering my service on this as well, is there a wiki we could start > dividing up the sections that need to be updated and get this rockin and > rolling. > Hehe, well I personally don't know of one, but you now know where the guide files are stored at. I'd say you can start making landfall on the User Manual itself, and then post your updates here so that they can load them up for you. That's probably what I will do until I learn how to commit these files on my own. ^^ --Arturo From kare.sars at iki.fi Sun Sep 20 23:58:22 2009 From: kare.sars at iki.fi (=?utf-8?q?K=C3=A5re=20S=C3=A4rs?=) Date: Sun, 20 Sep 2009 21:58:22 +0000 Subject: [kde-doc-english] KDE/kdegraphics/libs/libksane/libksane Message-ID: <1253483902.444135.9025.nullmailer@svn.kde.org> SVN commit 1026156 by sars: Add support for inverting the colors of the scanned image. There is a checkbox to enable/disable it, that is enabled if the source = transparency and film = negative. GUI: Add a splitter to enable hiding the options + a "splittercollapser" copied from gwenview. Make the zoom-in/out/... buttons toolbuttons in a toolbar, to deuglyfy the interface a bit. (hardcoded to icons only) M +1 -0 CMakeLists.txt M +48 -57 ksane_widget.cpp M +89 -30 ksane_widget_private.cpp M +22 -9 ksane_widget_private.h M +5 -1 options/ksane_opt_combo.cpp M +3 -0 options/ksane_opt_combo.h A splittercollapser.cpp trunk/KDE/kdegraphics/gwenview/lib/splittercollapser.cpp#1025850 [License: GPL (v2+)] A splittercollapser.h trunk/KDE/kdegraphics/gwenview/lib/splittercollapser.h#1025850 [License: GPL (v2+)] M +7 -0 widgets/labeled_checkbox.cpp M +1 -0 widgets/labeled_checkbox.h M +6 -0 widgets/labeled_combo.cpp M +7 -2 widgets/labeled_combo.h http://websvn.kde.org/?view=rev&revision=1026156 From lueck at hube-lueck.de Mon Sep 21 07:37:46 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-15?q?L=FCck?=) Date: Mon, 21 Sep 2009 07:37:46 +0200 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: References: <20090920163320.GL27621@3LockBox> Message-ID: <200909210737.46614.lueck@hube-lueck.de> Am Montag 21 September 2009 03:17:21 schrieb Jonathan Jesse: > > Volunteering my service on this as well, is there a wiki we could start > dividing up the sections that need to be updated and get this rockin and > rolling. > The userguide is already divided into 49 docbooks in the svn archiv (http://websvn.kde.org/trunk/KDE/kdebase/runtime/doc/userguide/). -- Burkhard L?ck From lueck at hube-lueck.de Wed Sep 23 12:16:27 2009 From: lueck at hube-lueck.de (Burkhard Lueck) Date: Wed, 23 Sep 2009 12:16:27 +0200 (CEST) Subject: [kde-doc-english] [Bug 78597] links in kioslave documentations are dead In-Reply-To: References: Message-ID: <20090923101627.56BA92154A@immanuel.kde.org> https://bugs.kde.org/show_bug.cgi?id=78597 Burkhard Lueck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |lueck at hube-lueck.de Resolution| |FIXED --- Comment #14 from Burkhard Lueck 2009-09-23 12:16:20 --- This was fixed with https://bugs.kde.org/show_bug.cgi?id=106066 SVN commit 883365 by lueck: reorganize the kioslave documentation: WebSVN link: http://websvn.kde.org/?view=rev&revision=883365 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From jasilva28 at gmail.com Sun Sep 27 06:56:48 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Sun, 27 Sep 2009 00:56:48 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <200909210737.46614.lueck@hube-lueck.de> References: <20090920163320.GL27621@3LockBox> <200909210737.46614.lueck@hube-lueck.de> Message-ID: <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> Well, after wasting a little bit of time and being relatively unimpressed by the [very few] WYSIWYG editors that [presumably] support the DocBook format, I finally decided to simply edit the DocBook files manually using good ol' fashioned Kwrite. It brought back good ol' memories of my old HTML days. ^__^ The only problem was that I still couldn't figure out how to actually READ the DocBook files using a standalone application that wasn't KHelpCenter. Not having luck with that, I ended up making /usr/share/doc/kde/HTML/en/khelpcenter read-write, backing the original contents up somewhere, and then making all the new changes directly to the files. That way, i could follow my changes regularly by swapping back and forth between pages in KHelpCenter -- very crude, but got the job done. ;) ---- I started with the KDE Viisual Dictionary as promised and for the most part modernized all the example screenshots. However, I also did some edits to the introductory text and presentation as well, since my goal (now that I know what I can do) is to MERGE the Quick Start Guide with the Visual Guide, making it a Visual Quick Start Guide of sorts that more-or-less fulfills the original goal of creating a graphical tour of KDE. For the moment, please review my work on the Visual Dictionary: http://pigux.com/kde4/documentation/visualguide_2009-0927.zip Thanks! --Arturo "C-quel" Silva From yurchor at ukr.net Sun Sep 27 08:26:47 2009 From: yurchor at ukr.net (Yuri Chornoivan) Date: Sun, 27 Sep 2009 09:26:47 +0300 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> References: <20090920163320.GL27621@3LockBox> <200909210737.46614.lueck@hube-lueck.de> <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> Message-ID: Hi! ?? Sun, 27 Sep 2009 07:56:48 +0300, Arturo Silva ???????: > Well, after wasting a little bit of time and being relatively > unimpressed by the [very few] WYSIWYG editors that [presumably] > support the DocBook format, I finally decided to simply edit the > DocBook files manually using good ol' fashioned Kwrite. It brought > back good ol' memories of my old HTML days. ^__^ > > The only problem was that I still couldn't figure out how to actually > READ the DocBook files using a standalone application that wasn't > KHelpCenter. Not having luck with that, I ended up making > /usr/share/doc/kde/HTML/en/khelpcenter read-write, backing the > original contents up somewhere, and then making all the new changes > directly to the files. That way, i could follow my changes regularly > by swapping back and forth between pages in KHelpCenter -- very crude, > but got the job done. ;) > You can use Kate with Konsole (Window->Tool Views->Show Terminal) KPart. Just enter in command line (after the corresponding directory change): meinproc4 your_docbook && konqueror index.html and you will see docbook HTML version in Konqueror. When you make changes in docbook issue the command meinproc4 your_docbook again and push F5 in Konqueror. Hope this helps, Yuri From jasilva28 at gmail.com Sun Sep 27 08:45:00 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Sun, 27 Sep 2009 02:45:00 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: References: <20090920163320.GL27621@3LockBox> <200909210737.46614.lueck@hube-lueck.de> <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> Message-ID: <955730e10909262345g3cc84e0exed668d2622b057eb@mail.gmail.com> On Sun, Sep 27, 2009 at 2:26 AM, Yuri Chornoivan wrote: > > You can use Kate with Konsole (Window->Tool Views->Show Terminal) KPart. > > Just enter in command line (after the corresponding directory change): > meinproc4 your_docbook && konqueror index.html > and you will see docbook HTML version in Konqueror. > > When you make changes in docbook issue the command meinproc4 your_docbook > again and push F5 in Konqueror. > > Hope this helps, > Yuri hehe, well it certainly helps in that I don't have to stick my nose into a root directory anymore, so I can continue from the safety of my home folder. ^^ However, it does seem a bit awkward to have to keep converting this thing to an HTML file after each change. Not hard to do, but just awkward in that it's not already a feature somewhere. You would think given the importance of our documentation, there'd be more DocBook tools to help potential new contributors submit their work. Having worked with the format this evening, I actually don't find it that hard (in fact, it's even a little easier than HTML in some parts), and that's why I don't know for the life of me why there are so few WYSIWYG editors and even viewers that work exclusively with this format. I'd hope that creating a simple DocBook viewer for KDE4 wouldn't be any harder than taking KHelpCenter and adding on a few extra menu options and maybe Kate integration. Maybe an actual Dev can prove me wrong, but it's just something that's been on my mind. ;) --Arturo "C-quel" Silva From cannewilson at googlemail.com Sun Sep 27 11:03:23 2009 From: cannewilson at googlemail.com (Anne Wilson) Date: Sun, 27 Sep 2009 10:03:23 +0100 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909172252i6576613akcc08afa3c035e3bc@mail.gmail.com> References: <955730e10909172252i6576613akcc08afa3c035e3bc@mail.gmail.com> Message-ID: <200909271003.30514.cannewilson@googlemail.com> On Friday 18 September 2009 06:52:56 Arturo Silva wrote: > On Fri, Sep 18, 2009 at 1:45 AM, Yuri Chornoivan wrote: > > You can try Syntext Serna Free (it is open source WYSIWYG XML editor). > > > > http://www.syntext.com/products/serna-free/ > > Aaaah! Eureka! This looks nice! ^__^b > > Course since you brought it up, I guess I'll take that as one vote > that for "Yes", it's okay for me to try updating the User Manual. Now > I'm hopeful. ^___^v > > Just so I don't get too ambitious at first (I am a bit sick at the > moment), I figure I'll try updating the Visual Dictionary first. > Maybe by end of next week. ^^b > There has been quite a lot of talk about the relative simplicity of wiki editing, but of course the need then is for import and export. Burkhard L?ck identified a mediawiki extension - http://www.mediawiki.org/wiki/DocBook_XML_export - and I've put in a request to sysadmins to have this installed (bug #205912). As you know, sysadmins are always overworked, so if anyone feel they can help with this, please add to the bug report and/or contact danimo. Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20090927/fc103019/attachment.sig From lueck at hube-lueck.de Sun Sep 27 12:18:01 2009 From: lueck at hube-lueck.de (Burkhard =?iso-8859-1?q?L=FCck?=) Date: Sun, 27 Sep 2009 12:18:01 +0200 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> References: <200909210737.46614.lueck@hube-lueck.de> <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> Message-ID: <200909271218.01663.lueck@hube-lueck.de> Am Sonntag 27 September 2009 06:56:48 schrieb Arturo Silva: > > I started with the KDE Viisual Dictionary as promised and for the most > part modernized all the example screenshots. However, I also did some > edits to the introductory text and presentation as well, since my goal > (now that I know what I can do) is to MERGE the Quick Start Guide with > the Visual Guide, making it a Visual Quick Start Guide of sorts that > more-or-less fulfills the original goal of creating a graphical tour > of KDE. > > For the moment, please review my work on the Visual Dictionary: > > http://pigux.com/kde4/documentation/visualguide_2009-0927.zip > Hi Arturo, thanks for your work. I downloaded your update, but there are a few issues to solve before I can proofread it: * index.docbook is broken, does not pass checkXML index.docbook here :-( * please don't change the folder layout (png's in a subfolder of visualdict, this breaks the current cmake macro kde4_create_handbook and makes your update unusable for the english documentation as for all language documentations as well. * please send only the changed files (or even just a svn diff). In your zip archive with a mixture of files from kdelibs and from kdebase/runtime and even from your distro I can not recognize which files from the svn archiv are changed and therefore check, if and how your update can be integrated into the kde system. -- Burkhard L?ck From jasilva28 at gmail.com Sun Sep 27 20:10:03 2009 From: jasilva28 at gmail.com (Arturo Silva) Date: Sun, 27 Sep 2009 14:10:03 -0400 Subject: [kde-doc-english] KDE User Guide outdated? In-Reply-To: <200909271218.01663.lueck@hube-lueck.de> References: <200909210737.46614.lueck@hube-lueck.de> <955730e10909262156i708300fbx47a628d4158ecc8@mail.gmail.com> <200909271218.01663.lueck@hube-lueck.de> Message-ID: <955730e10909271110q54af4184v28fc80941d1087fe@mail.gmail.com> On Sun, Sep 27, 2009 at 6:18 AM, Burkhard L?ck wrote: > > * index.docbook is broken, does not pass checkXML index.docbook here :-( > > * please don't change the folder layout (png's in a subfolder of visualdict, > this breaks the current cmake macro kde4_create_handbook and makes your update > unusable for the english documentation as for all language documentations as > well. > > * please send only the changed files (or even just a svn diff). In your zip > archive with a mixture of files from kdelibs and from kdebase/runtime and even > from your distro I can not recognize which files from the svn archiv are > changed and therefore check, if and how your update can be integrated into the > kde system. > Hmm, that is kind of overestimating the extent of my contribution or what little knowledge I managed to scrape up over the course of the week regarding this format. I don't even understand half of what you're saying (diff?), and I really explained before this is not taken from the SVN copy nor really meant to be committed back to SVN in its current form. All I really need is for it to be reviewed, and then whoever is knowledgeable enough (and also happens to have an SVN account) can take the best of my draft copies and apply it to the trunk copies in a way that doesn't break anything. If for whatever reason you can't read what I sent you (and welcome to my world if you can't), then try using the attached HTML copies if you want.