boen_robot
-
Posts
8,493 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by boen_robot
-
In order to show this info, you would also need some XSLT to transform it. Because I didn't had much to do, here's a simple XSLT I made few minutes ago specially for you(in other words: I used your feed for tests) . <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="http://www.shareasale.com/dealdatabase2.xml" --><!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> <!ENTITY copy "©"> <!ENTITY reg "®"> <!ENTITY trade "™"> <!ENTITY mdash "—"> <!ENTITY ldquo "“"> <!ENTITY rdquo "”"> <!ENTITY pound "£"> <!ENTITY yen "¥"> <!ENTITY euro "€">]><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="iso-8859-1"doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/><xsl:template match="/rss/channel"><xsl:variable name="link" select="//link" /><div><a href="{link}"><xsl:value-of select="title" /></a><br /><xsl:value-of select="description" /><br /><xsl:for-each select="image"><xsl:variable name="url" select="url" /><xsl:variable name="title" select="title" /><xsl:variable name="width" select="width" /><xsl:variable name="height" select="height" /><a href="{link}"><img src="{url}" alt="{title}" width="{width}" height="{height}" /></a><br /></xsl:for-each></div><div><xsl:for-each select="item"><span><a href="{link}"><xsl:value-of select="title" /></a><br /><xsl:value-of select="description" /><br /></span></xsl:for-each></div></xsl:template></xsl:stylesheet> A recently discovered(well...) JavaScript that would load the feed and the XSLT is this one: <!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"><head> <title>TEST</title> <script type="text/javascript"> var sourceXML = 'http://www.shareasale.com/dealdatabase2.xml'; var sourceXSL = 'rss.xsl'; var container = 'xmlData' ; function getIEXML() { var writeObj = document.getElementById(container); // Load XML var xml = new ActiveXObject("Microsoft.XMLDOM"); xml.async = false; xml.load(sourceXML); // Load the XSL var xsl = new ActiveXObject("Microsoft.XMLDOM"); xsl.async = false; xsl.validateOnParse = false; xsl.load(sourceXSL); // Transform writeObj.innerHTML = xml.transformNode(xsl); } function startMozXML() { //Load the XML xmlhttpXSL = new XMLHttpRequest(); xmlhttpXSL.open("GET", sourceXSL, false); xmlhttpXSL.setRequestHeader("Content-Type", "text/css") xmlhttpXSL.send(null); loadedStyle = xmlhttpXSL.responseXML; //Load the XSL xmlhttpXML = new XMLHttpRequest(); xmlhttpXML.open("GET", sourceXML, false); xmlhttpXML.setRequestHeader("Content-Type", "text/xml") xmlhttpXML.send(null); var xmlDoc = xmlhttpXML.responseXML; //Transform var writeObj = document.getElementById(container); var xsltProcessor = new XSLTProcessor(); var xmls = new XMLSerializer(); xsltProcessor.importStylesheet(loadedStyle); var xmlDoc = xsltProcessor.transformToDocument(xmlhttpXML.responseXML); writeObj.innerHTML = xmls.serializeToString(xmlDoc); } function init() { if(window.ActiveXObject) { getIEXML(); } else if(window.XMLHttpRequest && window.XSLTProcessor) { startMozXML(); } else { document.getElementById(container). innerHTML = 'No Support In This Browser..' } } window.onload = init; </script></head><body><div id="xmlData">In order to see this, you must turn on your JavaScript.<br />If yo have turned on your JavaScript, refresh the page and wait.</div></body></html> However, now that you mentioned it, I tested the above code and... khm... the only way it will run is if the XML and the XSLT are in one folder. It can't work with absolute paths.Perhaps if you or anyone else could adjust the code for absolute paths, this code will get all feeds out there(or atleast this one ).
-
To tell you the truth, at first I wanted to make ColdFusion's points equal to ASP.NET's but in the process of writing I decided to give 1 more point to ColdFusion when it came to extension.I know that ASP has many(if not all) of the abilities of C# but NOT using the language itself is what made my point. PHP can be extended using it's existing capabilities which are great. ASP.NET has greather capabilities, that's for sure. But as I said, I think creating custom tags and functions in ColdFusion using ColdFusion itself is most probably easier and it has the ability for C# extension.Hm...oh well... substracting 1 point from ColdFusion for that makes it equal to ASP.NET.The big issue is still the price though. If hosts must pay for it, this makes it more expensive to us you know.Note: Theese are all my opinions and I don't want to "force" them. I don't have any experience with ASP.NET and I barely know PHP and ColdFusion, so my opinions are not as trustworthy but they are neutral scince I'm not very experienced with any of those languages.[edit] Well, the thing we are tring to do here is point the newbies in the right direction, right? That's why I had to mention the thing above. [/edit]
-
<xsl:include hfer="something.xsl" /> example
boen_robot replied to boen_robot's topic in XSLT/XSL-FO
That thing was not helpful, but it was kind'a inspiring for which I was able to find a solution on my own. I saw that topic about templates and I realized I used 2 template with a match of "/". Scince they are both included, they are considered to be one and a same template. Therefore XSLT select and renders only the last one with a template match="/". To avoid this problem I had to adjust my XPath expressions to fit with different matches. The chages were in the fragment codes:image.xsl <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="test.xml" --><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="windows-1251"/><xsl:template match="/site/images"> <xsl:for-each select="image"> <xsl:variable name="location" select="location" /> <xsl:variable name="description" select="description" /> <img src="{$location}" alt="{$description}" /><br /></xsl:for-each></xsl:template></xsl:stylesheet> links.xsl <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="test.xml" --><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="windows-1251"/><xsl:template match="/site/links"><xsl:for-each select="menu/item"> <xsl:variable name="link" select="link" /> <xsl:variable name="logo" select="logo" /> <xsl:variable name="title" select="title" /> <a href="{$link}"><img src="{$logo}" alt="{$title}" /></a><br /></xsl:for-each></xsl:template></xsl:stylesheet> I'm posting this for 2 reasons.1. If I ever forget it.2. If anyone ever has the same issue. -
May I please ask the moderator who made the Poll to get rid of the MX after Dreamwaver? As said above, the latest version is 8. If there are people who use older versions, then just saying "Dreamwaver" might be the best thing to do.
-
Cold Fusion is a great language indeed. I tasted a bit of it's power and it's truly delicious .However, the fact that hosts must pay for it makes it very unatractive to them. That's actually the reason for the top popularity of php. It runs on both Linux and Windows and it's free.ASP.NET is free but it needs Windows which is payed.ColdFusion runs on Windows and Linux. Hosts can get Linux for free but they must still pay for ColdFusion itselfPHP can run on the free linux and PHP itself is also free.Conclusion: Hosts look for "invest less, win more" plans, and PHP requres less investment, yet it holds great enough power for people to use the host's plan.As for which is the best development tool. Let's make a comparrison:If you are not sure about your host or you want to enable yourself to move to a host that would support your language, you would need a language that is most widely supported. In this caseColdFusion-1ASP.NET-2PHP-3In order to publish your stuff you would have to create it first, right? So The ease of use in my opinion is this:ColdFusion-3ASP.NET-2PHP-1(I don't know more about PHP then I do about ASP.NET and yet I place ASP.NET above PHP, can you believe it?)Looking until now makes the languages all equal. Each gets 4 points. So let's continue.All languages have great support of many technologies. However, there are some for which a lot of lines are requred to get the thing you want. The best way to compare languages in terms of support is by comparing the number of commands needed to perform one task. Of what I have seen I may say this:ColdFusion-2ASP.NET-2PHP-1ColdFusion shares 2 points with ASP.NET because each supports things that the other doesn't support as well as the other. ASP has support for Microsoft kind'a things, and ColdFusion has a support for Macromedia kind'a things. PHP only has support for common things, not related to both parties.What if the language doesn't have ANY support of what you're looking after? You would need a way to extend the language with your own scripts using other languages. For this criteria I would say:ColdFusion-3ASP.NET-2PHP-1ColdFusion Supports creating custom tags and functions as well as extend the language with C++, JAVA, etc.ASP could be extended with with C++ and others as well but something tells me creating tags and functions linke in ColdFusion is easier then C++ extending.PHP can't be extended. The only way to extend it would be to use it's existing functions in a great combinations to create a new application for this particular action. In other words: a lot of lines of code.One last thing. Documentation. It's not about if there is some. Of course there is. the question is how easily understoodable and easy to find is. I think this:ColdFusion-2ASP.NET-2PHP-3Because of it's popularity, PHP is documented in many books and the manual in the official site is really huge and complete, though I admit it's hard to find anything in it as a learning source.The tutorials at w3schools about ASP(.NET) are more than complete I think so this alone makes it well documented. I bet other solutions there are also pretty full.ColdFusion is documented in dreamwaver as well as it's own documentation. I think due to Macromedia's attempts to make their language popular they inlude some info everywhere they get the chance which makes the language kind'a well documented but there isn't any place I would call "the source of knowedge" which is the reason I don't give 3 points to ColdFusion.The results are not very complete here by the way. But the total is this:ColdFusion-11ASP.NET-10PHP-8But the price is a big issue you know.
-
<xsl:include hfer="something.xsl" /> example
boen_robot replied to boen_robot's topic in XSLT/XSL-FO
Sorry for being kind of inpatient, but could anyone help me? Please... -
To center something you use "margin: 0 auto; ". If you want to center only all images(the center point is considered to be the center of their containg element, not the center of the page)you would do img {margin: 0 auto;} and for absolutely everything body {margin: 0 auto;}
-
Thanks to a PM from hacknsack I was able to solve my problem. By the way, I made some small improvements to the code. I don't know much JavaScript but the code describes itself I guess. Notice that the function and usabillity is still the same. But if you are going to use a DOCTYPE(that was the reason for my problem) you must use this code: <!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"><head> <title>First XML Data Import</title><script type="text/javascript">var sourceXML = 'test.xml';var sourceXSL = 'test.xsl';var container = 'xmlData' ;function getIEXML(){ var writeObj = document.getElementById(container); // Load XML var xml = new ActiveXObject("Microsoft.XMLDOM"); xml.async = false; xml.load(sourceXML); // Load the XSL var xsl = new ActiveXObject("Microsoft.XMLDOM"); xsl.async = false xsl.validateOnParse = false; xsl.load(sourceXSL); // Transform writeObj.innerHTML = xml.transformNode(xsl);}function startMozXML(){ //Load the XML xmlhttpXSL = new XMLHttpRequest(); xmlhttpXSL.open("GET", sourceXSL, false); xmlhttpXSL.setRequestHeader("Content-Type", "text/css") xmlhttpXSL.send(null); loadedStyle = xmlhttpXSL.responseXML; //Load the XSL xmlhttpXML = new XMLHttpRequest(); xmlhttpXML.open("GET", sourceXML, false); xmlhttpXML.setRequestHeader("Content-Type", "text/xml") xmlhttpXML.send(null); var xmlDoc = xmlhttpXML.responseXML; //Transform var writeObj = document.getElementById(container); var xsltProcessor = new XSLTProcessor(); var xmls = new XMLSerializer(); xsltProcessor.importStylesheet(loadedStyle); var xmlDoc = xsltProcessor.transformToDocument(xmlhttpXML.responseXML); writeObj.innerHTML = xmls.serializeToString(xmlDoc);}function init(){ if(window.ActiveXObject) { getIEXML(); } else if(window.XMLHttpRequest && window.XSLTProcessor) { startMozXML(); } else { document.getElementById(container). innerHTML = 'No Support In This Browser..' }}window.onload = init;</script></head><body><div id="xmlData">In order to see this, you must turn on your JavaScript.<br />If yo have turned on your JavaScript, refresh the page and wait.</div></body></html> The big change was the line xsl.validateOnParse = false; Thanks again hacknsack.The other small change I made was that I exported xmlData as a separate variable called "container". That way, If you use multiple copies of this script for different XMLs and/or XSLTs in tags with different IDs you can change the name of the container ID instantly instead of looking for it in the middle of the document.
-
I don't think CSS has changed much scince 2002 but... why buy a book on the first place? w3schools has a full CSS reference. Well, ok... almost full. But atleast it has everything that the W3C standarts requre.
-
In order to fully understand PHP(and any other language on this matter) you should know(X)HTML first. The way I see it- you don't.The <tr> is an HTML tag for a Table RowThe <td> is an HTML tag for a Table Data(a cell on a row).The <br /> is an XHTML tag for a single line break (as when you press the Enter key in MS Word for example).For more information about HTML go to the HTML tutorial and to see all (X)HTML tags go to the (X)HTML tag reference.
-
Ok, so am I the only one who can't see the XSL in IE at all?The code works with FireFox but not with IE. The XSL files themselves work everywhere, so the problem must be somewhere in the JavaScript code, but where?!?!
-
You can always do that by typing the out-to-in order the element's style should be applyed. Like this:td.SectionBlueTitle{background-image: url( "Images/HeaderBlue.jpg" );color: #FFFFFF;}td.SectionBlueTitle a, a:link, a:visited, a:hover, a:active{color: #00FFFF;text-decoration: underline;} As you can clearly see the second style is applyed to every link only if it's inside the element on it's left(in this case: a table from class SectionBlueTitle).
-
There is an error in your code... the closing bracket of SectionBlueTitle is closed at the end of the document, not the selector.Try this: td.SectionBlueTitle{background-image: url( "Images/HeaderBlue.jpg" );color: #FFFFFF;}a, a:link, a:visited, a:hover, a:active{ color: #00FFFF; text-decoration: underline;}
-
Scince XHTML is almost the same as HTML, you should study HTML first. XHTML has only few differences which you could learn in minutes. Besides- w3schools only explains the differences between HTML 4.01 and XHTML in the XHTML tutorial. However, don't get used to HTML as it has very few things that you need to know. Especially the advanced secion of the site... the only useful thing there is probably the "meta" tag.So the best order to learn things "might" be the one which is on the site:HTMLXHTMLCSS---------Then you may specialize yourself in some other language if you see things you can't do with this trio. Like JavaScript, PHP, ASP or (my favourites) XML, XSLT, etc.
-
I looked into the XPath tutorial and the XPath referance and there wasn't anything mentioned about variables. So having a "variable" may be the problem. Exactly what are you trying to achieve?In the meantime, let's analize, shall we? This XPath expression of yours should return the "BATCHALLOCATIONS.LIST" in every "ALLINVENTORYENTRIES.LIST" inside the document who have a GODOWNNAME different from... what's that? There should be a value or a string there I think... How do you define a variable in XML?You should show the XML(a shortened version that is) and point the thing you expect the XPath to select.
-
Generally, attributes shouldn't contain data that should be extracted. If you are the creator of the XML (or have a connection with the one), you should (tell him to) place the attributes in other elements.The way to get an attribute is the same as an element but the XPath expression is different.Try this: <?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:template match="/"> <xsl:value-of select="/INVENTORY/Book/@Isbn"/></xsl:template></xsl:stylesheet>
-
I think the best thing might be to transform this data with XSLT and then use PHP to execute the XML and the XSLT.However, I don't know a code that would execute the XML and XSLT. Hope someone else does...
-
@hacknsackI have no idea how Mozilla browsers or servers work. The ones I test my pages with are only IE6, FireFox 1.5, Opera 8 and from today Netscape Navigator 8. Mozilla probably don't have XML and/or XSLT support. I don't know.I also don't know much JavaScript(I haven't read any of the "Advanced" section of the site and I don't remember much of the basics) so I can't even start to think what could be the reason for that error(if it's in the script that is).By the way, for some unknown reason IE doesn't return a thing now(it did earlyer today thogh ). I copyed the same code again, just to ensure there wasn't anything altered accedently and still...nothing.I saw Opera 9(10x Jonas), and it returned nothing, just like IE . Hm... let's look this on the bright side. I could atleast preview the full XSLTs in Opera and they will work later in the process if I make XSLT only pages.
-
@hacknsack thank you! This script is something I was looking for as well. This will allow me(and not only me of ofcourse ) to insert XSLTs in fragments of my XHTMLs instead of having a whole page in XSLT only. I mean... the example at w3schools didn't worked properly with IE nor Firefox with me. But this one works with both of them.There's only one thing bugging me. Opera doesn't support XSLT. So, isn't there a way for the JavaScript to process the XSLT and return the raw XHTML that will be resulted? Or is this only possible through server side scripting?
-
as far as i know "name" is being deprecated to be replaced by "id". That's right. The ID tag is the "new" thing. However old browsers don't recognize the ID attribute, so it's not a bad thing to place both ID and NAME in elements if you're aiming for maximum accessibility.
-
Opera doesn't have XML support as far as I know. As for FireFox- it's a standart compilant browser. the <xml> tag in HTML is unofficial and FF doesn't use unofficial tags. IE6 has a full support for XML which is why it's the only browser showing this.Forget this method. XSLT is the one true way of transorming XML documents.
-
A lot more easier solution might be XAMPP. It's a all-in-one server pack that includes Apache, PHP, MySQL, FireZillaFTP server, Zend Optimizer and more. Once you install it and start the services, all you need to do is to check your security setting by typing http://localhost in your browser and go to the apropriate menues. After that you may move/delete everything in XAMPP's "htdocs" folder and place all of your PHP files there. They will be accesable by typing http://localhost/*the-name-of-the-file* or http://*yor-IP*/*the-name-of-the-file* in the browser window.Notice: If someone knows your IP they will also be able to see your pages.
-
Well, you may use PHP or other server side scripting language to translate the data. Here's a sample PHP parser I found on a site: class RSS_Parser{// {{{ part-variables (all private)var $Counter; // counts each resource of informationvar $Current; // contains the name of the current elementvar $Parent; // contains the name of the parent of the current elementvar $Parser; // the XML parservar $Result; // the array containg all neccesary information// }}} // {{{ constructor/**Prepares the object*@access public*/function RSS_Parser(){$this->Counter = 0;$this->Current = '';$this->Parent = '';if(!($this->Parser = xml_parser_create()))die('Could not create XML parser!');xml_set_element_handler($this->Parser, 'start', 'end');xml_set_character_data_handler($this->Parser, 'data');}// }}} // {{{ start()/**Controls the opening tags*@access private@param resource $Parser XML parser@param string $Element name of the element@param array $Att array containg the attributes of the element*/function start($Parser, $Element, $Att){if(ereg(':', $Element))list($prefix, $this->Current) = explode(':', $Element);else$this->Current = $Element;if(($this->Current == 'CHANNEL') || ($this->Current == 'IMAGE') || ($this->Current == 'ITEM'))$this->Parent = $this->Current;if($this->Current == 'ITEM')$this->Counter++;}// }}} // {{{ end()/**Controls the closing tags*@access private@param resource $Parser XML parser@param string $Element name of the element*/function end($Parser, $Element){$this->Current = '';}// }}} // {{{ data()/**Controls the data*@access private@param resource $Parser XML parser@param string $Data simbolic data of the element*/function data($Parser, $Data){if(($this->Current == '') || (trim($Data) == ''))return;if($this->Parent == 'ITEM')$this->Result['items'][$this->Counter][strtolower($this->Current)] .= stripslashes(htmlspecialchars($Data, ENT_NOQUOTES));if(($this->Parent == 'CHANNEL') || ($this->Parent == 'IMAGE'))$this->Result[strtolower($this->Parent)][strtolower($this->Current)] .= stripslashes(htmlspecialchars($Data, ENT_NOQUOTES));}// }}} // {{{ parse()/**Parses the current document*@access public@param string $file name of the file or URL@return array Array containg the neccesary info*/function parse($file){$this->Result = array();$fp = @fopen($file, 'r');xml_set_object($this->Parser, &$this);while($Data = fread($fp, 4096)){if(!xml_parse($this->Parser, $Data, feof($fp)))break;}xml_parser_free($this->Parser);$this->RSS_Parser();return $this->Result;}// }}}} The page wich would include the feed must include this: <?php// Include the parserinclude('parser.php');$p = new RSS_Parser();// The array containg the information from the feed$channel = array();$channel = $p->parse(news.rss');// Visualize the name of the site...echo '<b><a href="'.$channel['channel']['link'].'" ';echo 'target="_blank" ';echo 'title="'.$channel['channel']['description'].'">';echo $channel['channel']['title'].'</a></b><br />';// ... as well as the individual names of every newsforeach($channel['items'] as $item){echo ' » <a href="'.$item['link'].'" target="_blank" title="'.$item['description'].'">'.$item['title'].'</a><br />';}?> Notice that this code is made from a Bulgarian and that I have (atleast tryed to) translate all the comments inside. I have not tested the code, so I don't know if it will work at all.Also notice that you must change "news.rss" to the actual name of your feed.
-
<xsl:include hfer="something.xsl" /> example
boen_robot replied to boen_robot's topic in XSLT/XSL-FO
Thank you for not giving any reply on my question(that's sarcasm).I somehow managed to solve my issue. It's something that for some reason is ot mentioned in the XSLT referance nor Dreamwaver's:An include element can't exist inside a template. It could be before a template, after a template, and between two templates but never inside a template.I also discovered something really odd for the template<->include relationships which I would like someone to explain me in detail please... If you place include element BEFORE a template, the template will be executed but not the include element. If you place the include element AFTER the template you'll get the opposite effect- the template is not executed but the include element is.The "output" element from the main XSLT had to be removed as well. OK. I have an absolutely clean code. But here comes the weirdest part of it all.When I include more that one file one after another, only the latest one is displayed. Why?Here are the new versions of the codes:test.xsl <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="test.xml" --><!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> <!ENTITY copy "©"> <!ENTITY reg "®"> <!ENTITY trade "™"> <!ENTITY mdash "—"> <!ENTITY ldquo "“"> <!ENTITY rdquo "”"> <!ENTITY pound "£"> <!ENTITY yen "¥"> <!ENTITY euro "€">]><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:include href="links.xsl" /><xsl:include href="image.xsl" /></xsl:stylesheet> links.xsl <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="test.xml" --><!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> <!ENTITY copy "©"> <!ENTITY reg "®"> <!ENTITY trade "™"> <!ENTITY mdash "—"> <!ENTITY ldquo "“"> <!ENTITY rdquo "”"> <!ENTITY pound "£"> <!ENTITY yen "¥"> <!ENTITY euro "€">]><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="windows-1251"/><xsl:template match="/"><xsl:for-each select="/site/links/menu/item"><xsl:variable name="link" select="link" /><xsl:variable name="logo" select="logo" /><xsl:variable name="title" select="title" /><a href="{$link}"><img src="{$logo}" alt="{$title}" /></a><br /></xsl:for-each></xsl:template></xsl:stylesheet> image.xsl <?xml version="1.0" encoding="windows-1251"?><!-- DWXMLSource="test.xml" --><!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> <!ENTITY copy "©"> <!ENTITY reg "®"> <!ENTITY trade "™"> <!ENTITY mdash "—"> <!ENTITY ldquo "“"> <!ENTITY rdquo "”"> <!ENTITY pound "£"> <!ENTITY yen "¥"> <!ENTITY euro "€">]><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output method="html" encoding="windows-1251"/><xsl:template match="/"><xsl:for-each select="/site/images/image"><xsl:variable name="location" select="location" /><xsl:variable name="description" select="description" /><img src="{$location}" alt="{$description}" /><br /></xsl:for-each></xsl:template></xsl:stylesheet> Any ideas why is it like that and what should I do to include more than one file in a single document? -
No. This message means that the data is not encrypted... that is... not encoded. In other words- If the site's administrator decides that he would like to view your data, he can do it. BEWARE! This MAY also includes passwords. Anyway- this doesn't always mean that the admin is a froad. If you trust the site and the admin(s) there's no reason why not to post your data.
