boen_robot

There isn't an option, but somehow I managed to see a site which uses it to translate it's content into English. Their original language was German btw. The site was about GTA SA and I'm not sure how they achieved it. Server side script perhaps? Unfortunately I can't try look for it now... I forget the adress, and I don't think it's worth it to look for it again .

Hey, don't insult me . XSLT and XML are also languages that could go there. And I'm willing to take responsiblity at least for the first month of usefull tips. There are a lot of frequently asked questions which I (and w3schools staff of course) may give answers to .

I think maqromedia explained the reason for which XHTML is not allowed to be used inside posts .

I'm not sure I understand what you want. What XSLT does is to transform the XML into XHTML. It's considered a stylesheet of the XML which is the reason you open the XML file to see the site itself. If you want the user to see the XHTML code instead, you must execute the XSLT and XML with a server side script, which will make the transformations and return the XHTML code to the client. This is especially usefull for XSLT unaware browsers. The XSLT tutorial explains how to execute the code with ASP(see XSLT on the server), but I'm still searching for a way to execute it with PHP. I think that if you ask Skemcin, he would be able to tell you a code for ColdFusion .There is also another way- make XHTMLs and use the JavaScript code here. This executes the code inside the XHTML and it's practically a way to bind XSLT with XHTML. However, it doesn't have the advantages of server side executed XSLT.

Try adding "display: block;".

As web developers, we all want our pages to work in all browsers, right? Newbies (a.k.a. lamers) won't get firefox. There's no way that this will change scince IE comes with Windows. If IE doesn't become better, we would still have to take it in consideration. Considering the above two- It's better to suggest even if Microsoft is not going to listen. If you DO say something, there's a better chance then if you don't say anything. It's like voting on political elections. If you don't give your opinion (a.k.a. vote) for the goverment you prefer, then you don't have the right to critisize it.

When writing XSLTs, the DOCTYPE is declared at the <xsl:output> element. As you can see, I have suggested transitional. The reason for this is that you use tables for layout. Also, If you have accidently added some deprecated HTML tag, this would make your stylesheet invalid.For your next project, use strict. For this one, it may be best not to risk with strict.

Get a more usefull editor. Most (all?) of them automatically convert the character into it's entity when it's typed/pasted into their design(NOT CODE!) box.One more thing... entities begin with &. For example returns space. The same way, a number equivalent would return that character.

first stop: the attribute element is applyed on it's container element. Therefore, it's recommender that you include it in something which you are fammiliar with.Instead of IFs or templates I would go for "for-each"s. <xsl:for-each select="following-sibling::title"><p><xsl:attribute name="paragraphformat">bold</xsl:attribute></p> The following-sibling::title should select all sublings to title, which are bold and italic. If you want only the italic, you may always go to it "manually" like: /title/bold The paragraphformat with it's value "bold" is going to be applyed onto the <p> element.Sorry for replying after all theese months, but it's just that I see this post now.

Try using this namespace: xmlns:xsl="http://www.w3.org/1999/XSL/Transform" Also, when you select the variable, I think there must be a $ right after the {. Like: 'You are in the '{$Dept}' Department!)

DataIslands and XML with CSS are two completely separated ways of styling XML data.Embeding XML data with DataIslands(the <xml> tag) means to "bind" the ata inside the XHTML. It doesn't refer to styling it. The CSS file for the XHTML has "the honor" of styling the displayed data inside the XHTML page. Of course, this works only with IE but that's another subject.To style an XML with CSS means to style the XML file itself. This means that it will all be effective when the XML file is ran in the browser. Different transformations of the same document will apply their own respective styles.The fact that CSS styling in XML can't be carried to the XHTML page is the reason why CSS styling was never the future of XML styling. The best method is an XSLT page that would have a reference to external stylesheet that would style the transformed document.

This is probably an indication that your server doesn't support PHP. Or... I'm not sure actually. When I was failing trying PHP scripts I saw nothing everywhere a PHP script was used. For example: Hello. You are <?php echo "welcome"; ?> Would return "Hello. You are ".Just to ensure: ask your host if he has PHP support. It's really important that we know.You should also try this: <?php require("header.htm"); ?> All this SSI does is copy&paste the code from the specified page into the page it's used. Therefore, you must strip your included pages of their heads and bodies (excuse the pun ). I'm not sure if PHP scripts are allowed within the imported files.I'll wait a bit before making your header thing (though I could finish it in a few hours or a day mostly). As said above: SSIs are the better method in this matter.

The reason for this lack of quality is the file format of the picture itself. It can only look good if you specify the original size. If you want a thumbnail of it, you should get some kind of image editor (PhotoShop, Fireworks, SnagIt, GIMP, etc.), resize the image with it, put the smaller version on the server. The img tag would call the smaller version. If this image is suppose to link to the full version of the image, the <a> tag would point to the full version. The only way around this would be a server side script that would do the resizing.

Does anyone have ANY idea on this?

For the sake of trying to solve this challenge, I was able to use few XPath functions. The only one which didn't worked was node-name() which is actually the ctutual one here. Both IE and FF say it's not a valid XPath function. Even adding the fn: prefix before it didn't work. It said that the namespace I provided(from the XPath referance) doesn't contain any XPath functions . <xsl:stylesheet version="1.0"xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fn="http://www.w3.org/2005/02/xpath-functions"><xsl:template match="/"><html><head></head><body><table><xsl:for-each select="/Pets/node()"> <tr> <td><xsl:value-of select="node-name(node())" /></td> <td><xsl:value-of select="current()" /></td> </tr></xsl:for-each></table></body></html></xsl:template></xsl:stylesheet>

Normally, when people learn, they know that to use and manipulate a database, they need server side scripting. When they get in to the point of the tutorial, where there is SQL manipulation, they realize that SQL is a whole another language and start learning it THEN. This basically means they are aware on how should they set up a database to use with the particular server side script (scince it's explained in the server side script tutorial). It almost never goes the other way around.

In addition to DarkElf's post I must say that if you place all of your lyrics on one page, you practically force the user to download them all before he/she is able to see anything. If you aren't "fighting" for maximum accesability and standart compilance, you could use frames with removed borders(so it doesn't get ugly). One for the menu, and one for the main content. Perhaps a third for the header.

You should forget that method. It's only shown in the tutorial for learning purposes, not for usability ones.Use XSLT instead. It's the best (only?) way to transform XML data appropriately. Otherwise, as you said it yourself, it's just a plain text. Of course, XSLT is not exactly embbed into pages, so I must warn you that the you are entering a whole new world. Welcome to the light side of the force .

The xmlns defines an XML NameSpace. In other words: defines that what you are using is that particularly pointed XHTML. the xml:lang attribute is the new equivalent to the lang attribute. Some (most?) developers use both to ensure compatability. the lang attribute specifies a language that is used in that element. This information could be used by screen reader to adjust their voice and/or vocablulary specifically for the pointed language. It could also be used by CSS for language specific stylings and perhaps there are few more uses as well.If there are portions of different languages in the same document, you must add the appropriate lang attribute to each portion.No. This attribute is NOT equivalent to the meta charset thingy. What the meta tag describes is this case is the Character set that is used. Each language may have few charsets used. Think of it like this: you may speak (for example) Italian or English, but you still use latin letters. You may speak Bulgarian or Russian but you still use cyrilic letters, etc. etc. etc.In short: a language's Alphabet is not the same as the language itself.

Here is one of the many topics in which this has been discussed.

If he is really to blame, don't forget to tell that. There are other people here who have the same problem. Like this one for starters. There also might be more...[edit] By the way, I made more posts today, then the whole week combined I think. All in the XSLT forum. This part of the forum is starting to get bussy. I feel warm inside when I think about it [/edit]

What language you choose is up to you. When you learn it's basics and some of it's more frequently used functions, you'll also see how to add accounts into that database, so when the user has his account and password correctly, he would acces the content. One thing though. A tatabase does NOT cotain images. It can however, contain referances to them which the server side can use to find them. Read the ASP, ASP.NET and ADO tutorials and come here again if you don't grasp something. I would had recommended the PHP tutorial as well, scince PHP is THE most popular server side scripting language, but the tutorial is not as complete as the ASP ones.

You already said it yourself(well...kind of): use a consistant naming scheme and their respective values, so XSLT could fill the whole thing without the need of XPath functions: <pets> <pet> <kind>cats</kind> <quantity>3</quantity> </pet> <pet> <kind>dogs</kind> <quantity>2</quantity> </pet> <pet> <kind>parrots</kind> <quantity>2</quantity> </pet> <pet> <kind>turtles</kind> <quantity>5</quantity> </pet></pets>

There's no way to manipulate a database without the usage of a server side script(PHP, ASP(.NET), ColdFusion, etc.), so... yes... you need to know theese things well.

Honestly, I'm out of ideas. This is not a code problem scince everything is working locally. Therefore, it's getting out of my competencse. Try asking the host if he knows anything about this. If he could register the mime type of xml and xslt or whatever...