boen_robot

The only way around this which I can think about this is the following:1. Make an image of the whole header at one.2. Make a single table cell for it.3. Size that cell so it fits the full image.4. Place the image as a "background-image: url(background_or_whatever.jpg)".5. Place a div, span or whatever inside the table cell and write the "contact us" link there.6. Give the div,span or whatever a "float: right".

The float property is exactly what comes great uder different resolutions scince it's putting the stuff on the top left/right corner of the container of the element .As for the picture problem... I'll look for it now, but I you should check if the code in the html and xsl is exactly the same. Any difference might be the cause for this.[edit=1]Hint: I also saw that only FF makes this problem. It all works fine in IE. Strange...[/edit][edit=2]Another hint: it only makes it with the XML file. When I preview the XSLT, there's no problem in both IE and FF.[/edit][edit=3]Could it be the tabular design itself?[/edit]

There are two ways of achieving this. Either store it in XML and XSLT and execute it with JavaScript or (the better solution in this matter)- use server side includes. The server side language will import the code for the header in every page and that's it. And as far as I know... frames are not allowed in strict XHTML.

The code is the same as with the links(exept for the selector of course). The only problem is that IE doesn't support :hover on anything else besides links. Sorry.

You forgot to post the code for the XSLT. After all, that's what caused the problem. Nevermind. It was in the zip anyway .This works, I tested it. The changes are in the XPath expressions selecting the news themselves: <xsl:for-each select="/news/entry"><table width="700" border="0" cellspacing="0" cellpadding="0"> <tr> <td> <!-- Reading from news.xml //--> <div class="white12pxTahoma" align="left"><strong><xsl:value-of select="title" /></strong></div><br /> <div class="grey10pxVerdana" align="left"><xsl:value-of select="post" /></div><br /> <div class="grey8pxVerdana" align="right"><xsl:value-of select="author" /> ranted on <xsl:value-of select="/news/entry/date" /></div> <br /> </td> </tr></table></xsl:for-each> By the way... table designs s.u.c.k. . When you have some time to spare on redesign, try getting rid of the tables and replace them with CSS float, positions, demensions, etc.

"mimetype" refers to the type="text/xsl" stuff. They are also specified in the server's configuration. I don't know exactly why they are needed and what's the difference but I know they are requred and IE doesn't care for them and that's why it shows them. By the way, is it me, or the XSL stylesheet doesn't have an XML prolog? I mean... <?xml version="1.0" encoding="ISO-8859-1"?>

Apache is a server setup.Server Side Script refers to all languages that are performed on the server using Apache. This include PHP, ASP(.NET), ColdFusion, JSP, etc.

The only way you may edit XML based files (XML, XSLT, XSL-FO, SVG, etc.) is with server side scripting. The server side itself could actually connect with a database and fill some variable(s) which would affect the overall look of the whole thing.You can do XML only file and use XSLT to transform it to make it look like an XHTML page, but it won't have that WOW efefct. At least I can't imagine it without server side scripting though. If you could make such a thing only on the client side, you would definetly impress the whole web design community .There's also a way any XML based language could be embbed inside an XML document. By adding a namespace in the beggining. Imagine if you add and all of them .In short: the possibilities of all XML technologies combined are virtually limitless. You need to know what are you looking after and then see what you need for it.

fn:name() is a function which returns the name of the current node. Or atleast that's what it says. fn:current() is suppose to return the value of the current node... hm... maybe fn:current(fn:name())? Anyway... the main point is that you need to use XPath's functions which makes the things a lot harder when they could be so simpler... can't you make the XML look more... normal?

Too true. Most people here are best at web design languages and Flash is not among them.The site still sounds cool though. The only concept I can't graps is wouldn't there be something free? Would authors be allowed not to requre a licence for them? If so, would that mean that their games will be completely free?

<xsl:template match="/pets"><table width="200" border="1"><xsl:for-each select="//"> <tr> <td><xsl:value-of select="fn:name()" /></td> <td><xsl:value-of select="fn:current()" /></td> </tr></xsl:for-each></table></xsl:template> I'm not sure, but I think if the functions were working this template would had returned what you want.

I'm not sure, but I think you may integrate portions of XML files into a database, retrieve them and transform them into several forms to show the flixibility of XML. Another thing would be to make the interface by XML and XSLT and execute the transformations.By the way, I'm not even sure what exactly you are asking for. Ideas for the usage of XML and related technologies, XML only? Idea for a theme (movie, music, game, etc.) for a site build with XML and/or related tehnologies?

Isn't that exactly what I said ?

IE supports :hover only on links(<a> tags).

If you want to make your site look like something, you should forget about GeoCities. There are hosts which give better offers and don't have ads or if they do, they are much more conviniently placed then in GeoCities.No. Adding another ad won't create problems with the site itself. It will however cause problems with the downloading speed and the "space" you have on the page. If you use GeoCities, it's most certain that you'll eventually get too "Advertisy" which increases the annoyance factor, which means less traffic, which means less profit.In short: the way you have it planed currectly will backfire.

You aren't obligated to write if you don't have anything useful to say Dale . dvm knows CSS or atleast knows what he/she needs to know, so it's pointless to show him/her the link. The issue he/she has is infact really hard to figure out. I don't have a solution to it, so I'll stop here.

Does the whole start of your document look EXACTLY like this: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"> I mean that it's just that this is how XHTML transitional should be correctly accesed. Otherwise, all browser go into quirksmode where it's completely normal to have such diferences.

Maybe it's just that the server you are on sucks . Try it elswhere. IE doesn't care for MIME types and FF does. In general, what IE does is bad but in this case- better .Also, I see you haven't changed the referance in the XML...?

"semantic" basically means something with a meaning. Look at it like this:You need to set a specific ID on an element so you can apply CSS styles on it. You must think of the name for yourself. Normally a person would call an element the way it's suppose to look. This is wrong. Appearances changes over time. Instead, think of WHY you want to set this ID to that element.Example of bad name:<div id="red_background"><p id="ddd">"ddd" implies no meaning. If you name every element with differend number of "d"s it might eventually get confusing. "red_background"? What if you change the background to blue? You would go and change "red" to "blue"? There's no point of it all.Example of good names<div id="wrapper"><p id="description">Whatever happens, the wrapper will remain a wrapper and the description is going to remain a description. Their look may change, but their purpose won't.

It's possible by replacing the node name with "fn:name". However, for some reason, I seem to be unable to allocate the namespace where the XPath functions are and because of that, every document in which I use a function returns an error... I'll keep looking.

Try changing the "xslt" extension of the file to "xsl". This is the standart extension of such files. Some servers accept xslt but others (apparantly) don't. Don't forget to change the referance in the xml file too .

Actually what I meant was one feed for all languages. It won't be in a very good favor of w3schools if there are different feeds, because all people would constantly need to come up with something. If all the languages are in one place, everyone could write when they have found something or when there's just something to say. Otherwise, they would be obligated to all of us. I don't know about you, but my conscience doesn't allow me to expect everyone at w3schools to write regularly for each language's feed. Having one feed would allow each expert to write when he/she has time about it without making the feed look outdated .

I also thought about this... Not everyone could actually understand the tip itself so quickly and they should scince this is school, not a script gallery. Not to mention it would be hard for anyone, even a JavaScript "guru" to think of a new usefull script every day. Maybe a weekly tip would be better?Also, why only JavaScript? Wouldn't it be much better if those tips covered all other languages as well?

http://www.w3.org/TR/2004/REC-voicexml20-20040316/It seems VXML 2.0 is a reccomendation scince 2004 . The small addition 2.1 is still a candidate reccomendation though .

W3Shools' XSLT on the server example demonstrates how XSLT transformations could be executed with ASP, so the user could see the final XHTML output. Could anyone offer me that same equivalent in PHP please? What I need is only to execute it. No funny business within the file (in other words... I'm not asking for anything special)... just that. Do I need something special on the server (I hope not)? Are there differences between PHP4 and PHP5 in this matter?