Pipesmoker - I rolled back your change on KHangMan and deleted the language bar in KAlgebra. Please do not use the old i18n language bar. It doesn't work with the new translation extension, so anyone using it could lose their work. The new language bar gets added when the first translation is done. It's automatic - part of the process.
When you are all happy with your edu pages, please request preparation for translation. We will check that they meet the criteria set by our translators, then mark them ready to go.
Pages that you should watch, to be abreast of the latest developments are Translation_Workflow and its associated Talk page, PageLayout, Toolbox and Typographical_Guidelines. --annew 19:54, 14 June 2010 (CEST)
|Thread title||Replies||Last modified|
|Bug in template||0||09:36, 22 April 2011|
|The Archive namespace||2||12:23, 29 January 2011|
|LQT bug?||3||20:01, 14 January 2011|
|Still under construction?||2||19:06, 29 October 2010|
|Chihuahua||0||13:59, 6 September 2010|
|Translation discussion on Talk:Translation_Workflow||2||12:41, 29 June 2010|
When you have time could you please look at http://userbase.kde.org/Talk:KPDF#link_of_kde3_icon_1046 ? There is an intended action in the template that clearly isn't happening. I don't know whether we can correct it, but if not we should remove the implication that it will happen. Thanks.
When you created 500 as Archive, did you create 501 as Archive_talk? I'm just wondering about this after reading http://www.mediawiki.org/wiki/Manual:Using_custom_namespaces because it sounds as though I should have been asked if I wanted to move the associated talk pages, and I wasn't asked. Of course that may be because it ignores empty talk pages.
I came across this on the Mediawiki list, and though that it might be related? <quote> Don't write anything like: $wgExtraNamespaces[NS_FOO_TALK] = "Foo talk"; # no underscore
but: $wgExtraNamespaces[NS_FOO_TALK] = "Foo_talk"; # with underscore
See http://www.mediawiki.org/wiki/Manual:Using_custom_namespaces </quote> Could be a total "red herring" of course
Can you do a check for me please, just in case there is something wrong in the way I'm doing things?
I've noticed that if I reply to a LQT using the More/Reply link (I don't know whether it applies to the other Reply link) the Preview option doesn't work. While for short answers I don't bother, if what I've written is more complicated I like to preview, making me re-read before posting.
Strange, i cannot reproduce your issue during typing this answer. Could it depend on the depth of the thread perhaps?
OK, testing at this level, then (I think that was the level I saw it earlier today)
No, it seems OK at the moment. Let's try another two-way on this reply set and also test from the other Reply link, to see whether it occurs elsewhere. If not, I'll have to think it's something stale in Chrome again. I do find I have to re-start Chrome occasionally.
Kig/Macros has had the notice for a long time - are you still working on it?
We are close to moving UserBase to the new Chihuahua theme. There are some big advantages with Chihuahua, not the least being the ability to adapt to screen space, both large screens and small, hand-held ones. Much of the work I've been doing lately has been to prepare pages for the switch. As always, with something new, there are likely to be issues that we are not aware of until it is in more general use, so I'm approaching all who have made significant contribution in the last seven days, asking for help.
I'd like you to change your User Preferences to use Chihuahua, as soon as possible. The plan at the moment is that if at the end of this week we have no show-stopper issues we will make Chihuahua the default theme for UserBase, probably next weekend.
There is a public Etherpad at http://webteam.notes.kde.jefferai.org/14? - please add any notes, comments, issues there. It's also helpful if you say "Hi" in the chat window, because that ties a comment colour to your name, so I know who to approach if more discussion is needed.
Thanks for the help.