User talk:Tom-
|
|
| Contents |
About the Other Languages picture...
Hi Tom,
There was that annoying problem that the image en:Image:Other-langs2.png (http://en.wikipedia.org/w/index.php?title=Image:Other-langs2.png&redirect=no), because it is also a redirect to Wikipedia:Languages, previously would have gotten displayed on top of that article if the user clicked the image on the home page (but not if they clicked the text link). I've fixed this by creating a redirect at meta:Redirecting_to_Wikipedia:languages... (http://meta.wikimedia.org/w/index.php?title=Redirecting_to_Wikipedia:languages...&redirect=no) and including that. So if the user clicks on the link on the Main Page here, they get redirected to the above page on Meta which in turn redirects them to Wikipedia:Languages. Because the image here at the English Wikipedia does no longer redirect straight to Wikipedia:Languages, the image no longer gets rendered on the top of the screen. It's a roundabout way, but it works.
Ropers 10:49, 10 Jan 2005 (UTC)
MSIE style sheet addition
Hi Tom. I've searched high and low for information about editing the Explorer-specific style sheets, and all I found was a sub-page of your user page.
MSIE/Win doesn't automatically substitute fonts for characters that aren't supported by the display font. Consequently, text with many International Phonetic Alphabet characters fails to display correctly. Other browsers and platforms which support Unicode don't seem to have this problem.
Some of us have cobbled together Template:IPA (documentation), which supplies MSIE with a font-family declaration to fix this. In other browsers it sets the font-family back to inherit, but this is hidden from MSIE 6 with a CSS filter.
This solution is a bit of a hack, and vulnerable to editing by well-meaning users who don't know the details. It would be best to hide it away from all browsers except MSIE in one of the IEFixes.css style sheets. I don't know which version is most appropriate; I don't have the facilities to test it in various versions (Mac user), but MSIE 6 users seem happy with it as it stands, and no one else has complained that it's exploded their browser.
The ideal declaration would be:
.IPA { font-family: Arial Unicode MS, Lucida Sans Unicode, Gentium, Code2000; }
Then I could reduce Template:IPA to:
<span class="IPA">...</span>
Could you help facilitate this addition to the style sheet, or point me in the right direction to make it happen? Thanks, Michael Z. 21:20, 2005 Jan 20 (UTC)
Monobook.css validation
Me again, Tom.
Yesterday, all of my edit form fields turned medium grey, making editing pages very annoying. I haven't been able to override it in my user style sheet. I've explained the details at Village Pump.
I've looked through everything, and can't find a CSS declaration that causes this, but I noticed that some of the experimental edits you added broke validation for the local monobook.css (http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fen.wikipedia.org%2Fw%2Findex.php%3Ftitle%3DMediaWiki%3AMonobook.css%26action%3Draw%26ctype%3Dtext%2Fcss%26smaxage%3D2678400&warning=1&profile=css2&usermedium=all), specifically, at least this line (is that a Microsoft property?):
filter: alpha(opacity=90);
The main monobook doesn't validate (http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fen.wikipedia.org%2Fskins%2Fmonobook%2Fmain.css&warning=1&profile=css2&usermedium=all), either. Any chance you could fix the errors, and remove the invalid declarations? Thanks. —Michael Z. 2005-01-21 17:59Z
- Hi Michael, nothing of what I've changed in Monobook.css could be affecting form fields, unless there's a really weird bug in Safari (it's a usability experiment, slightly fading out inactive tabs).
- I'll take a look into it, it could be recent changes to Monobook's primary CSS file is causing the problem. Hopefully it can be fixed soon, sorry for the problem in the meantime. Thanks, Tom- 20:30, 21 Jan 2005 (UTC)
- I couldn't find anything that could directly cause the fields' background colour to change, but another user has reported the same problem, so it sounds like it some recent change. The W3 validator got a parse error on that
filterdeclaration, so the results in other software are totally unpredictable. Even if that's not the cause, it's hard to trouble-shoot if the style sheets don't validate. Thanks for having a look.
- I couldn't find anything that could directly cause the fields' background colour to change, but another user has reported the same problem, so it sounds like it some recent change. The W3 validator got a parse error on that
- Ignore the parse error, the CSS is invalid but it won't cause problems. I do have developer access, and I've just booted up my mac to try and track the problem down. As of yet I can't even replicated the problem however :( Tom- 20:54, 21 Jan 2005 (UTC)
- Apparently fixed now, seems Safari has a nasty and very weird bug with opacity. I'll send a bug report to Apple. Tom- 23:31, 21 Jan 2005 (UTC)
- Thank you, thank you. I'm quite interested in this kind of thing. What's the nature of the bug? Regards, Michael Z.
- I'm not actually sure, as I only have Safari 1.0, which doesn't show this bug. I'm trying to get Panther installed so I can test it fully. On the face of it, Safari is incorrectly applying the opacity property (which it does support as of 1.2) to form elements, when it should only be applying it to inactive tabs. It's all rather strange... Tom- 10:08, 22 Jan 2005 (UTC)
Thanks again for fixing the background-color/transparency problem, Tom. Anyway, when you have a minute, could you fix some of the syntax errors, too? When the style sheets don't validate there's no way to predict how they'll break rendering in someone else's browser.
monobook/main.css (http://en.wikipedia.org/skins/monobook/main.css):
- Line 66: the validator doesn't seem to like mixed case in colour keywords, although I can't find anything about this in the W3C recommendations ("Orange" → "orange")
- Line 239: "none" is not a valid value for margin or padding, it should be "margin: 0; padding 0;"
- Line 930: missing semicolon
monobook.css (http://en.wikipedia.org/w/index.php?title=MediaWiki:Monobook.css&action=raw&ctype=text/css&smaxage=2678400):
- Lines 160, 164: why not put Microsoft things like "filter" into one of the IE-specific style sheets?
Sorry to bug you with this trivial stuff. I would do it myself if I had access, and I don't know any other way to get this fixed. Thanks, Michael Z.
MediaWiki:Monobook.css
Please revert this change (http://en.wikipedia.org/w/index.php?title=MediaWiki:Monobook.css&diff=next&oldid=10109434) ASAP. It is messing up the display of table of contents. -- Netoholic @ 06:14, 2005 Feb 10 (UTC)
WikiNorthampton
Hi Tom Brookie here from Grendon - good to see local skills on the Wiki! Brookie 13:43, 19 Mar 2005 (UTC)
system messages/ markup question
Hi Tom. I had a question and sannse on freenode/#wikipedia reccommended that I ask you. I am trying to make http://gu.wikipedia.org/wiki/Special:Userlogin look exactly like http://en.wikipedia.org/wiki/Special:Userlogin . But I am stuck... there are three differences which I cant seem to overcome.
- The yellow box in en.
- The text on en appears at right of the login text boxes and on gu: it appears at the bottom.
- There is an extra button on gu:
Can you tell me what am I missing?
You can reply to my talkpage here or preferably on my talkpage on Gujarati Wikipedia.
Thanks. --Spundun 07:28, 18 May 2005 (UTC)
Introduction templates
Just wondering if you could chime in on why the Introduction templates are designed the way the are, etc. User:Trödel/sig 17:11, 1 Jun 2005 (UTC)