Hi,
It would help the promotion of MW if we could make sure both the CSS and the
HTML are valid upon release of each version.
http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fen.wikipedia.o
rg%2Fwiki%2FMain_Page
I could do this when I get time and install the latest version is no one
else wants to?
...
Geoff Deering
In Turkish capital of i is capital I with dot. But in wiki automatic
capitalization on page titles makes it I without dot. How can i solve this
problem? input and output encoding is set to utf-8.
Thanks.
hello,
after the complete installation and the first start of mediawiki I got an
error:
pear_error: message="XML_ERROR_INVALID_TOKEN in
/home/cgi/schule/zier/mediawiki/templates/xhtml_slim.pt around line 1"
code=0 mode=return level=notice prefix="" info=""]
what's the problem??
with best regards
Oswin
--
NEU: GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++
I'm running the latest wiki and it's doing fine. I want to be able to
add CSS classes so I can play with certain page layouts using the
editing function. If I use a simple tag, like a DIV, and use an
existing class in the .css file (say, in the main.css file for
Monobook), it works just fine. But if I create a new class in the same
file (and yes, I'm scripting it right), the DIV does nothing. It's like
it won't read unique classes in the .css file. Any ideas how to get
around this?
Hello,
I would like to display stuff of a mediawiki database on a second page
without editing possibilities and without the framework around the content.
So is there a php content viewer for the mediawiki?
Or could I take the php code of the whole project and use only the part,
dispalying the conent?
Which part of your code parses the data and manages the correct
presentation of the content?
Many thanks for your help.
Matthias
Hello, all.
I have a question about templates. I understand that they are excellent for
building things that one might wish to repeat on many pages, so having the
template saves a lot of extra work. Not only that, if you need to update the
content, you need only update the template, and the changes show up everywhere.
That part I get, but here is what I'm wondering:
If I had a page structure that I wanted people to use, would that be
appropriately done with a template? For example, if I had a few sections, like
"Description", "Requirements", "Download" etc., would it make sense to build a
template with those pre-built as section headings? Could I then create custom
stubs and include them in the template? The custom stub would be like "Add the
product description here, blah, blah, blah."
I have this in mind because there will be a lot of pages that we want to look
exactly alike, save for the actual content. How could I set this up so that they
use the template to start a new page from scratch?
Hmm...lots of questions in this one. Thank you in advance for your assistance in
clarifying my understanding of templates.
Craig Hartel
http://codex.wordpress.org/
One thing to consider,
I find that the 'printable view' is useful for things *other* than printing
- i.e. screen captures. I find the omission of this function from the
monobook skin to be regretable.
Of course admins and poweruser's can be informed to switch skins, but the
casual user is unlikely to make the distinction. Of course the installation
can be modified to use an alternate skin as the default - but monobook is
*much more* attractive IMHO.
Best Regards,
JT
===
You said:
===
Date: Tue, 14 Sep 2004 20:06:02 +0100
From: Rowan Collins <rowan.collins(a)gmail.com>
Subject: Re: [Mediawiki-l] Printable Version?
To: MediaWiki announcements and site admin list
<mediawiki-l(a)wikimedia.org>
Message-ID: <9f02ca4c040914120612a6cc7a(a)mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII
Paul Johnson <baloo(a)ursine.dyndns.org> wrote:
> > OK, for my next dumb question ~
> > Does anyone know what and how to hack my wiki to show a "printable
version"
> > option on my pages in monobook?
>
> I thought that was called the "classic" skin. Am I wrong?
The Classic skin, I believe, had/has a link to a special "Print
Version" of each article. The MonoBook skin, by using CSS, simply
tells the browser to print the page differently than it displays it.
This is of course rather more "magic" than most users expect...
--
Rowan Collins BSc
[IMSoP]
Again this creates a problem for the casual user and a dependence upon the
client software to properly render a 'print preview.'
Perhaps it would be appropriate to include this in the user preferences
(apply to all skins?) to include/exclude the 'printable view' link.
This would allow the site administrator to easily change the default
preference profile as appropriate as well as allowing the user's to override
that behavior in their personal preference profile.
Best Regards,
JT
===
You Said:
===
Date: Wed, 15 Sep 2004 10:34:10 -0700
From: Nick Triantos <nick(a)triantos.com>
Subject: Re: [Mediawiki-l] Printable Version?
To: MediaWiki announcements and site admin list
<mediawiki-l(a)Wikimedia.org>
Message-ID: <41487D12.1070707(a)triantos.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Firefox, IE, and Opera all seem to have Print Preview capabilities, is
that inadequate for your needs?
I'd personally prefer to not clutter up Monobook with things like a
print icon or other text.
regards,
-Nick
i write a page title containing Turkish characters in the title bar of the
Internet Explorer and press enter. the page opened contains some other
characters instead of turkish ones. in opera there is no problem. I have
look in to source but can't understand what the function
checkTitleEncoding does in Language.php and Languageutf8.php.
$wgInputEncoding and $wgOutputEncoding is set to "UTF-8". How can i
overcome this problem.