> In the same way that using semantic tags when all you want is
> formatting is equally discouraged. Ideally (perhaps) there would be
> ways of indicating both semantics, and pure formatting.
You can still use <b>bold</b> and <i>italic</i> tags if that's all you
mean, though I think that is rare.
> If there
> isn't, then either solution is really equally bad.
True.
> I would say that
> ''italics'' are very rarely used for emphasis in our articles, and
> much more commonly for simple formatting - names of albums,
> symphonies, quotations etc. I could be wrong there.
Ah. It seems to me that emphasis is used more often than simple
formatting, and I was changing ''quote marks'' to <i>italic tags</i>
in the few cases where it's appropriate, based on the way I learned
when I first started editing. Then I was looking through the source
code one day, and realized they were both being rendered as italics,
so I was confused.
So, if I understand correctly, a bunch of people were misusing
emphasis tags to mean italics, so someone changed the emphasis tags to
mean italics, and now people are misusing italics tags to mean
emphasis? :-)
: Are we going to change the dictionary definition colon markup to
render as CSS indentation now, since many people use it for
indentation?
> What's the specific problem that <I> tags are causing?
None at all from a practical standpoint. Just curious.
> >> No, on purpose. That was like a year and a half ago, I think.
> >
> > ...because?
>
> To stop abusing semantic markup (such abuse renders the semantics meaningless).
Well, maybe you can point me to a previous discussion so we don't have
to have the same discussion again, but I think it would be superior to
use semantic markup. I'm sure everyone's aware of this already, but
using visual formatting tags to represent emphasis is discouraged:
"The proper HTML elements should be used to mark up emphasis: EM and
STRONG. The B and I elements should not be used; they are used to
create a visual presentation effect. The EM and STRONG elements were
designed to indicate structural emphasis that may be rendered in a
variety of ways (font style changes, speech inflection changes, etc.)"
An automated run of parserTests.php showed the following failures:
Running test Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)... FAILED!
Running test Magic Word: {{NUMBEROFFILES}}... FAILED!
Running test BUG 1887, part 2: A <math> with a thumbnail- math enabled... FAILED!
Passed 298 of 301 tests (99%) FAILED!
Hello Wilinckx,
Here are my responses to your questions:
Q.the kind of URL you'd like to have
- I would like to have url look like how it is in en.wikipedia.org ie
en.wikipedia.org/Unix etc etc..
Q. the URL's MediaWiki links to when he links to an Article
Also please note, I am unable to login or do anything at all once I
try to make non ugly urls.
- Currently the links look like this
http://wiki/wiki/index.php?title=FEC if the changes do work I would
anticipate they look like http://wiki/wiki/FEC
Q. the URL MediaWiki says in it's HTML output the MonoBook CSS files
should be found
- Here's the entry in the html output that you are asking for.
<style type="text/css" media="screen,projection">/*<![CDATA[*/
@import "/wiki/skins/monobook/main.css"; /*]]>*/</style>
Q. the name of the directory MediaWiki is installed in
- Mediawiki is installed in /opt/local/htdocs/wiki
Q. the part of LocalSettings.php containing $wgScriptPath, $wgStylePath , etc
- Settings from Localsettings.php are as follows.
$wgScriptPath = "/wiki";
$wgStylePath = "$wgScriptPath/skins";
$wgScript = "$wgScriptPath/index.php";
$wgRedirectScript = "$wgScriptPath/redirect.php";
Q. and the mod-rewrite rules you've setup in httpd.conf ?
- The .htaccess in /opt/local/htdocs/wiki/ contains the following entries.
-----------------------------
# close the php security hole...
# not actually needed but probably a good idea anyway
php_flag register_globals off
# first, enable the processing - Unless your ISP has it enabled
# already. That might cause weird errors.
RewriteEngine on
# uncomment this rule if you want Apache to redirect from www.mysite.com/ to
# www.mysite.com/wiki/Main_Page
RewriteRule ^/$ /wiki/Main_Page [R]
# do the rewrite
RewriteRule ^wiki/?(.*)$ /w/index.php?title=$1 [L,QSA]
-----------------------------
The httpd.conf has the following entries in the very end.
## Wiki Settings
Alias /wiki /opt/local/htdocs/wiki/index.php
Alias /index.php /opt/local/htdocs/wiki/index.php
RewriteEngine on
RewriteLog "logs/rewrite.log"
RewriteLogLevel 5
As a way of cheating, you could always make the link point to some
long, descriptive name which redirects to the real thing.
Steve
On 4/5/06, Rich Morin <rdm(a)cfcl.com> wrote:
> I would like to be able to put arbitrary text into a
> hover box (aka, HTML title tag), to give the user a
> short precis of where a link will go. Looking at
> http://meta.wikimedia.org/wiki/Help:Link, I don't see
> any way to do this.
>
> If I'm missing something, please let me know. If not,
> perhaps we should discuss the possible syntax for this.'
>
> -r
> --
> http://www.cfcl.com/rdm Rich Morin
> http://www.cfcl.com/rdm/resume rdm(a)cfcl.com
> http://www.cfcl.com/rdm/weblog +1 650-873-7841
>
> Technical editing and writing, programming, and web development
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/wikitech-l
>
Hello,
Does MediaWiki allows to automatically put a certain text in advance on a
non-existing page? What I am trying to do is this: when users click on a
picture, a (link to a) new page is generated with the name
"{{PAGENAME}}-more-detailed-name".
Is it possible to already put automatically some text (e.g. "{{template}}")
on this new (non existing) page?
greetings,
JAN
Now that email confirmations have been enabled, there has been a fair
amount of traffic to the OTRS resulting from people replying to the
confirmation email they receive instead of clicking on the link in it.
The From: address of the confirmations is wiki(a)wikimedia.org, an address
which is being redirected to the info-en OTRS queue.
There is nothing we at OTRS can do to help these people.
I would like to suggest that perhaps another From: address be used,
ideally one that produces an automatic bounce.
The Uninvited Co., Inc.