This page is for discussion about content. If you want to discuss technical issues concerning UserBase, please use Userbase Technical Issues
If you want to post a question, click on Start a new discussion below. Enter a subject that describes the topic, write your message in the large text box and click on Show preview. If everything looks good, click on Save page to create the new thread.
Previous discussions can be found under Contents. If you want to reply to a thread, click on Add a reply at the bottom of the thread, enter your reply and click on Save page. To reply to a specific post, click on More under the post and then Reply in the pop-up menu.
| Thread title | Replies | Last modified |
|---|---|---|
| internal link button supplies bad template | 6 | 15:11, 12 November 2012 |
| Extension:Translate and chinese | 0 | 19:02, 14 March 2011 |
| Chinese language name translation issues | 0 | 19:01, 14 March 2011 |
| Can I import Lightning calendar to Korganizer? | 2 | 12:25, 30 January 2011 |
| Table of Contents | 3 | 17:23, 5 October 2010 |
| Enabling subpage feature | 2 | 19:15, 22 September 2010 |
| Template help | 6 | 19:12, 22 September 2010 |
| Please help make documentation more visual | 1 | 19:09, 22 September 2010 |
You know the button to "Internal link" adds the wrong template for an internal link. It serves up [[Link title]]
but it should serve up [[Link|title]]
Link - pipe - title not link - space - title
This is very annoying and a frustration when you are new editor. Can it be fixed?
Please use underscore (_) for internal links with spaces. It also would be good if you do so for images (it is almost impossible to parse image names with camel casing and unpredictable spacing).
Thanks in advance for your help.
I think you are misunderstanding that link. It is asking for the link-name, i.e. its page name. That is all that is required to make an internal link. However, we request that you use the pipe and text, as well as "Special:myLanguage:" so that it works better for translated pages and other-language readers. Naturally the mediawiki tools don't know about that, and it's probably a major task to adapt them.
The toolbar is served using MediaWiki core, and the text is contained within the message i18n files that come with the installation.
1. We don't edit the core files as it's impossible to keep a track of all the changes when we upgrade 2. If we change the english text for that, we also need to change the 385 other languages. Then we need to manually patch each language file every time we upgrade.
So primarily because of point 1, unfortunately, this cannot be fixed.
I guessed that it was probably pretty core. Maybe an enhancement request to MediaWiki pointing out the ambiguity in this buttons functionality then would be good. I reckon it should say [[<link title>]] rather than [[link title]]. Because as it stands it is not consistent with what the external link button offers up. which is [http://www.example.com link title] So for consistency the external link one could actually be [<http://www.example.com> <link title>]
or maybe [http://www.example.com LinkTitle] and [[LinkTitle]] But perhaps this is a discussion to by had on the MediaWiki web site not this one.
I will shut up now.
Hi All,
Just trying to find my way around Koffice & friends....
A simple(??) question..... Is it possible (allowed/recommended) to import calendar information like Tzasks/to dos/events from Lightning to KOrganizer?
If the answer is "yes" I presume it is also possible to export from KOrganizer to Lightning? And then.... is there a way of keeping the 2 calendars in sync, without having to cross-copy the data????
Thanks for a smart looking product!!!!!!
Dave
Lightning can export and import the data in iCal format. KOrganizer can work with iCal too. For the details please refer to KOrganizer handbook. You can make the same iCal file to be your calendar (locally or on some web service) and keep the data in sync.
Is it OK to add __noTOC__ to Welcome_to_KDE_UserBase?
Hi! If the subpage feature [1] is enabled for the Main (default) namespace we can get proper functioning of subpage links [2]. This saves a lot of work and avoids broken links when pages are moved around, helps with creating documentation (see e.g. Kexi/Handbook). Also breadctumbs shall work eventually.
I propose the same for techbase and community wikis.
Seems like a good idea. Though it might need some testing. And also, techbase and communitybase are not yet updated like userbase, which might involve issues with the old codebase. About to happen though, soon.
Sorry, not adding anything constructive to this discussion, but trying to squash a bug in the new theme. Hope you guys don't mind.
I've noticed some of the manuals that are split up into several pages have tables at the bottom with navigation links to the previous/next pages. I reckon this would be better served with Mediawiki templates. Then if you want you can change the style at a later date and everything will remain consistent. I made three templates just for this, Prev, Next and Prevnext if anyone wants to look. What do you think?
There are probably a bunch of other things I haven't noticed that might be better served by templates. I can help if anyone wants (I'm not great at makiI've noticed some of the manuals that are split up into several pages have tables at the bottom with navigation links to the previous/next pages. I reckon this would be better served with Mediawiki templates. Then if you want you can change the style at a later date and everything will remain consistent. I made three templates just for this, Prev, Next and Prevnext if anyone wants to look. What do you think?
There are probably a bunch of other things I haven't noticed that might be better served by templates. I can help if anyone wants (I'm not great at making them, but I know how to do it).ng them, but I know how to do it).
04:51, 2 June 2010 (UTC)
I'm definitely interested in discussing your ideas. We are in the process of updating the mediawiki engine (should be complete very soon as testing is advanced), and have several improvements in mind. Can you join us on IRC? - #kde-www - it makes sense to be planning now, so that we can get improvements out there in the new version.
09:23, 2 June 2010 (UTC)
Thinking a bit more about the Prev/Next templates, traditionally there was a centre entry, for Contents. What do you think about adding that? You could call it Manual Home, if that seems more appropriate.
10:29, 2 June 2010 (UTC)
I've made a slightly different prev/next template that uses a bit more syntax. Unfortunately due to the nature of mediawiki templates you have to specify the argument names in this one. It's similar to the one used on Wikibooks. It uses the {{PAGENAME}} variable for the text in the middle. I suppose you could change it to a link to the article index, but that would need another two arguments in the template and maybe that could be too complicated for casual users? Anyway, here is the link and this is what it looks like:
Check this page source for the syntax and how it's used. Do you think it's simple enough for everyday writers to understand? Unfortunately I am afk a lot of the time at the moment so I don't know when I'll be able to drop into IRC. But if you have any specific requests of me then tell me here or on my usertalk and I'll see what I can do. Or just dive in and change my current templates if you prefer :O) There's certainly a lot of room for improvement.
00:57, 3 June 2010 (UTC)
I didn't notice before that you have parserfunctions installed on this wiki. I've updated the second template to be an all-in-one navigation thingummy now. Still works the same way as described above, though.
04:31, 3 June 2010 (UTC)
That's really getting somewhere :-) Does {{PAGENAME}}/Manual work? I've tried it on http://userbase.kde.org/Template:Prevnext2
11:57, 3 June 2010 (UTC)
Appears to work just fine. Almost all of the arguments are completely optional, now. I hope the documentation makes enough sense. Glad you like it. It should probably be renamed if anyone is to use it, though. And the three original templates I made can probably be deleted now. Drop me a message if you want any more.
14:37, 3 June 2010 (UTC)
I noticed many pages in the documentation wiki are text only (that goes for techbase too), for example: Plasma [1] New users reading that might have no idea what that page is about.
In truth I had found that applications do have a screenshot (such as Okular [2]), but I don't think it is enough.
08:57, 26 March 2009 (UTC)
KDE UserBase Wiki 