[kde-doc-english] Where are the compose key docs?
Thu, 07 Jun 2012 07:46:48 +0300, Greg Metcalfe gmetcalfe at centurytel.net: Systems settings help is a locator service, at best. I'm glad the compose key location seems to have stabilized from F13 onwards, save that in F16, it's defined by default as both left and right Win keys. I used to define it as just the left Win key. Fine. Whatever. But could you provide some doc on how to use the thing? There's nothing in kwrite or kate doc, and nothing in the settings 'help'. In Windows, this is all numeric, and impossible to remember for most people. X/KDE is a vastly better system. /usr/share/X11/locale/en_US.UTF-8/Compose is not the whole story. I know I used to be able to get a micron symbol, because I read a doc where I used it. I can't find it again. Slash u, or u slash doesn't work, no matter the case. Nor could I find any reference to it in that /usr/share/X11 doc. It could be in there, but it's not really searchable. 'Micron' came up empty, and there are innumerable 'u's. The file is 5359 lines! Searching the KDE online docs, I get four hits. None of them relevant. The only help available is random returns from Google--much of it dated. A grep through the filesystem turned up mostly Gnome docs. Which I supose I would have to go through, if I wanted it badly enough to waste hours in the chase. If a 'micron' compose key sequence still exists, it might as well not. Nobody can discover how to access it! Please, please, PLEASE don't use this as an argument for yet more dumbing-down of the interface, and just elliminate the feature. The more valuable, though harder, software engineering path is to stabilize and document the capability. I'm not going to learn C++ and the Qt libs to help you with this--I'm busy too. I just spent 12 hours writing bash, Python, and Go. But I'm willing to help with testing and doc writing. Hi, There is a good tutorial on this topic on UserBase [1]. Please follow it (tested here, Mageia 2, KDE 4.8.2, works). You can assign for micron any combination that is convenient for you. Hope this helps. Best regards, Yuri [1] http://userbase.kde.org/Tutorials/ComposeKey
[kde-doc-english] Meaning of sentence is unclear in konversationdocumentation
Thu, 07 Jun 2012 02:44:17 +0300, Jack ostroffjh at sbcglobal.net: On 2012.06.06 07:50, Yuri Chornoivan wrote: I found the following text to be translated in message #1002 in the pot file of konversation in docmessages/extragear-network. This is a list of all topics that have been set for this channel while its tab was open.\n \n Duplicates, that is consecutively set topics with identical text and the same author, have been merged into a single list entry. The date and time shown is that of the last time the topic was set.\n \n When you select a topic in the list, the edit field below it will receive its text. Once you start modifying the contents of the field, however, the list will switch from the regular entry selection mode to allowing you to perform text selection on the entries in case you may wish to incorporate some of their text into the new topic. To return to entry selection mode and a synchronized edit field, undo back to the original text or close and reopen the dialog. The second sentence, which start with Duplicates is quite unclear to me. Hi, Actually, it is not the pure documentation question [1, line 5002]. I am not a native speaker, but I interpreted the second sentence as follows: 1. Duplicates are the topics with identical text and the same author, have been merged into a single list entry. 2. The duplicates will be merged into a single list entry. 3. The date and time shown for this single entry is the date and time of the last time the topic was set. Hope this helps. However, it will be good to have an opinion of some native speaker or Eike Hein himself. Best regards, Yuri [1] http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/konversation.pot?revision=1298368view=markup Yuri - I absolutely agree with your interpretation. (I am a native speaker.) Would it make sense to reword the original as: When there are multiple entries in the list with identical text and author, they have been merged into a single list entry. The date and time shown for that entry are the last date and time the topic was set. Jack Committed. Many thanks for your suggestion. Best regards, Yuri
[kde-doc-english] Where are the compose key docs?
On donderdag 7 juni 2012 06:46:48 Greg Metcalfe wrote: If a 'micron' compose key sequence still exists, it might as well not. Nobody can discover how to access it! Please, please, PLEASE don't use this as an argument for yet more dumbing-down of the interface, and just elliminate the feature. The more valuable, though harder, software engineering path is to stabilize and document the capability. When you start the application kcharselect and you enter greek in the search field you will get all Greek characters, among which the micron sign. -- fr.gr. Freek de Kruijf
[kde-doc-english] autogenerate directory indexes?
(From clicking the Feedback link in 'khelpcenter'...) OS: Linux Distribution: Debian Squeeze KHelpcenter version: 4.4.5 (Yes, i know, old version, so maybe this issue has been addressed already) Given there is a directory : /usr/share/doc/kde/HTML/en/kioslave I would expect (hope) khelpcenter help:/kioslave to provide the list of all the kioslaves that exist as subdirectories of that directory. Instead i am greeted with an error requestor: Error - KDE Help Center The file or folder help:/kioslave does not exist which is, at best, misleading. I would hope for at a minimum to see something like: no docbook index file found in directory help:/kioslave (/usr/share/doc/kde/HTML/en/kioslave) But, best case, i'd like to see the docbook file be autogenerated. I manually hacked up a index.docbook via: kioslave# find . -maxdepth 1 -type d \! -name '.' -printf listitemulink url=\%f/\%f/ulink/listitem\n listitemulink url=rlogin/rlogin/ulink/listitem listitemulink url=file/file/ulink/listitem ... listitemulink url=nntp/nntp/ulink/listitem listitemulink url=webdav/webdav/ulink/listitem (with other docbook metadata as gleaned from the ftp/index.docbook) Which works for my purposes in this one instance. But there are other directories like this (e.g. kcontrol), and it seems pretty unhelpful to assume that someone will instead have to know that they want to do ls /usr/share/doc/kde/HTML/en/kioslave to even figure out what contents of that master node exist. (defeats the purpose of having a document management tool like khelpcenter) (also, for something like kioslaves, where a third-party/updated kioslave might add itself to that directory, you really want the table-of-contents at ../kioslave to be dynamically generated anyway) thanks, --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy at ucar.edu- http://www.ral.ucar.edu/~sdowdy/
