parsers

Can someone please explain this section of this tutorial me?The relevant text I do not understand is:"Internet Explorer when using node childNodes[] will NOT containthese white-space nodes. In Mozilla those nodes will be in thearray."and"Internet Explorer will skip the white-space text nodes that aregenerated between nodes (e g new line characters) while Mozilla willnot. So in the example above. Mozilla browsers will alert 9 childnodes while Internet Explorer will alert 4."I checked the said file: In both. Firefox 2.0 as well as IE 6.0 it had only 4 <book> elements.. .. "Internet Explorer when using node childNodes will NOT contain.. these white-space nodes. ... In Mozilla those nodes will be in the... So with Mozilla and with IE/MSXML with preserveWhiteSpace set to true the object model contains white space text nodes between the book element nodes. ... (comp text xml) .. > Internet Explorer because of severe security problems. ... > They recommend Mozilla or Firebird. ... When testing MSIE on that site. I got an Internet Explorer prompt... (microsoft public security) .. If IE didn't take the associations back when you told it to. ... Check the box "Internet Explorer should check to see whether it is the.. where one specifies which browser is the default for everything at one go. .. changed everything mozilla like to IE. I still find most of my links are... (microsoft public windows inetexplorer ie6 browser) .. > arbitrary code (and opera and Mozilla too) ... > browser nothing perticularly serious about that. ... Mozilla does tend to be more strict than Internet Explorer. ... Having worked as QA Lead and created quite a number of applications myself. ... (Full-Disclosure)

Forex Groups - Tips on Trading

Related article:
http://newsgroups.derkeiler.com/Archive/Comp/comp.text.xml/2007-11/msg00010.html

comments | Add comment | Report as Spam

Hello. I desire to use Slickedit for editing XML - especially when a schema is available for context tagging. Recently. I undergo been authoring MSBuild project files which use Microsoft. create xsd. Unfortunately. Xerces generates several errors on this schema which do not appear if the MSXML parser is used (verified with Oxygen XML editor 9.0). It is probably wishful thinking but is it possible to make some "simple" mods to my configuration to change the XML parser from Xerces to MSXML? If not is that something that might be considered for a future release?Thanks,Stan MitchellSourceQuest. Inc. What version of SlickEdit are you using? There undergo been some improvements in the 12.0 x (SE 2007) versions. What I sight helps most for editing MSBuild proj files is to make sure you undergo an updated URL mapping for the namespace. Since there is no "real" xsd file at that URL location. SlickEdit can't download and reference it. Go to Tools > Options > URL Mappings and map the following:From: To: C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas\1033\MSBuild\Microsoft. Build. Commontypes xsd(Or whatever path your Visual Studio is installed to)You may need to change state and reopen the files for the mapping to take hold. Also sometimes Visual Studio gets all "Unicode GungHo" and starts saving project files in Unicode or UTF-8 change including the signature. Sometimes when SE loads an XML file (like a csproj file) that has this attach it gets confused and displays the leading EFBBBF signature as the literal characters . I just delete the characters and do a "Save As..." and pick "UTF-8. No Signature" in the encoding. Hi Mathew. Thanks for your reply. My version of Slickedit (for Windows) is 12.0.3.0My URL Mappings entry for MSBuild is as follows: -->D:\SourceUSB-2_10_01\SourceUSB\Build\MSBuild-Xml\Microsoft. create xsdMicrosoft. Build xsd includes two additional schema files in the MSBuild subdirectory. The errors that I see come from Microsoft. Build. CommonTypes xsd and are as follows:File D:\SourceUSB-2_10_01\SourceUSB/Build/MSBuild-Xml/MSBuild\Microsoft. Build. CommonTypes xsd 16 57: Error Attribute 'Include' already defined in base and should not appear in derivation by extension. 67 57: Error Attribute 'Include' already defined in base and should not be in derivation by extension. 136 57: Error Attribute 'Include' already defined in base and should not appear in derivation by extension. 167 57: Error Attribute 'consider' already defined in base and should not be in derivation by extension. 199 57: Error Attribute 'Include' already defined in locate and should not appear in derivation by extension. 240 57: Error Attribute 'consider' already defined in base and should not be in derivation by extension. 290 57: Error Attribute 'Include' already defined in base and should not be in derivation by extension. 398 61: Error Attribute 'consider' already defined in base and should not appear in derivation by extension. Oxygen XML editor 9.0 allows the use of different XML parsers for validation. If I use Xerces. I see the same errors with it as with Slickedit but if I change the parser to MSXML or MSXML. NET validation succeeds. Perhaps there is a Xerces setting that could be changed to allow it to accept this schema. To answer your original challenge we don't have a pluggable architecture for swapping out XML parsers. Xerces is "baked in" since we have to support multiple platforms. I'm not seeing the errors you describe but our MSBuild XML sources may be different. Under the Visual Studio 2005 XML directory. I have the following:Schemas\1033\Microsoft. Build xsdSchemas\1033\MSBuild\Microsoft. Build. Commontypes xsdSchemas\1033\MSBuild\Microsoft. Build. core out xsdThe top-level Microsoft. Build xsd simply includes the M. B. Commontypes xsd and Commontypes includes M. B. Core xsd. If I map to the top-level file. I don't get any validation errors but I somehow suffer the document root collection node definitions (desire ItemGroup and PropertyGroup). If I map (desire I showed earlier) to Commontypes then I get all the definitions and no validation errors. If I copy all three files to the same directory map to Microsoft. Build xsd (and edit Microsoft. Build xsd to not use the MSBuild\ relative path for the include) then all of the definitions are open correctly and no validation errors. Maybe Xerces doesn't like that double-include with a relative path thrown in the mix. We are using the same MSBuild schema - mine also comes from the directories you listed for Visual Studio 2005. However my MSBuild project files have more verbose namespace information like this:<Project xmlns:xsi="" xsi:schemaLocation=" ../../Build/MSBuild-Xml/Microsoft. create xsd" xmlns="" DefaultTargets="build" InitialTargets="ValidateCommandLine">I undergo been using this format because other XML editors use the schemaLocation to perform the equivalent of URL Mappings. If I decrease this to the short form:<Project xmlns="" DefaultTargets="build" InitialTargets="ValidateCommandLine">then the errors go away. However that may break my other XML editor - I'll need to investigate. Regarding which schema to map to. M. B xsd vs M. B. Commontypes xsd is more clear cut in my case. I need to map to the top level M. B xsd because I have defined custom tasks item groups and property groups in this file. But your suggestion to place all of the xsd files in the same directory seems to work around this issue. Thanks for your back up,-Stan Just a quick follow up after making the changes discussed previously. The short create XML header will also work with Oxygen XML 9.0 editor by using enter write association i e associating file extension with a schema in a project. Now. I am seeing a different problem. Slickedit's XML Validation comes back with "Document is Valid" although I know it has invalid child elements under PropertyGroup and ItemGroup elements. However the context tagging is working ok. Is there a way to display schema annotations/documention for a tag? In the preview window the Comments area is always keep. Thanks,-Stan

Forex Groups - Tips on Trading

Related article:
http://community.slickedit.com/index.php?topic=2321.msg9756#msg9756

comments | Add comment | Report as Spam

Hello. I like to use Slickedit for editing XML - especially when a schema is available for context tagging. Recently. I have been authoring MSBuild project files which use Microsoft. Build xsd. Unfortunately. Xerces generates several errors on this schema which do not appear if the MSXML parser is used (verified with Oxygen XML editor 9.0). It is probably wishful thinking but is it possible to make some "simple" mods to my configuration to change the XML parser from Xerces to MSXML? If not is that something that might be considered for a future release?Thanks,Stan MitchellSourceQuest. Inc. What version of SlickEdit are you using? There undergo been some improvements in the 12.0 x (SE 2007) versions. What I find helps most for editing MSBuild proj files is to make sure you have an updated URL mapping for the namespace. Since there is no "real" xsd file at that URL location. SlickEdit can't download and reference it. Go to Tools > Options > URL Mappings and map the following:From: To: C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas\1033\MSBuild\Microsoft. create. Commontypes xsd(Or whatever path your Visual Studio is installed to)You may need to close and reopen the files for the mapping to act direct. Also sometimes Visual Studio gets all "Unicode GungHo" and starts saving project files in Unicode or UTF-8 format including the signature. Sometimes when SE loads an XML register (like a csproj file) that has this attach it gets confused and displays the leading EFBBBF signature as the literal characters . I just delete the characters and do a "Save As..." and choose "UTF-8. No Signature" in the encoding. Hi Mathew. Thanks for your say. My version of Slickedit (for Windows) is 12.0.3.0My URL Mappings entry for MSBuild is as follows: -->D:\SourceUSB-2_10_01\SourceUSB\Build\MSBuild-Xml\Microsoft. Build xsdMicrosoft. Build xsd includes two additional schema files in the MSBuild subdirectory. The errors that I see come from Microsoft. Build. CommonTypes xsd and are as follows:File D:\SourceUSB-2_10_01\SourceUSB/Build/MSBuild-Xml/MSBuild\Microsoft. Build. CommonTypes xsd 16 57: Error evaluate 'consider' already defined in base and should not appear in derivation by extension. 67 57: Error Attribute 'consider' already defined in base and should not appear in derivation by extension. 136 57: Error Attribute 'Include' already defined in base and should not appear in derivation by extension. 167 57: Error Attribute 'Include' already defined in base and should not appear in derivation by extension. 199 57: Error Attribute 'consider' already defined in locate and should not appear in derivation by extension. 240 57: Error evaluate 'Include' already defined in locate and should not appear in derivation by extension. 290 57: Error evaluate 'Include' already defined in base and should not appear in derivation by extension. 398 61: Error evaluate 'Include' already defined in base and should not appear in derivation by extension. Oxygen XML editor 9.0 allows the use of different XML parsers for validation. If I use Xerces. I see the same errors with it as with Slickedit but if I dress the parser to MSXML or MSXML. NET validation succeeds. Perhaps there is a Xerces setting that could be changed to accept it to accept this schema. To answer your original question we don't undergo a pluggable architecture for swapping out XML parsers. Xerces is "baked in" since we have to support multiple platforms. I'm not seeing the errors you describe but our MSBuild XML sources may be different. Under the Visual Studio 2005 XML directory. I have the following:Schemas\1033\Microsoft. Build xsdSchemas\1033\MSBuild\Microsoft. Build. Commontypes xsdSchemas\1033\MSBuild\Microsoft. Build. Core xsdThe top-level Microsoft. Build xsd simply includes the M. B. Commontypes xsd and Commontypes includes M. B. Core xsd. If I map to the top-level register. I don't get any validation errors but I somehow lose the enter root collection node definitions (like ItemGroup and PropertyGroup). If I map (desire I showed earlier) to Commontypes then I get all the definitions and no validation errors. If I copy all three files to the same directory map to Microsoft. Build xsd (and edit Microsoft. Build xsd to not use the MSBuild\ relative path for the consider) then all of the definitions are open correctly and no validation errors. Maybe Xerces doesn't like that double-include with a relative path thrown in the mix. We are using the same MSBuild schema - mine also comes from the directories you listed for Visual Studio 2005. However my MSBuild communicate files have more verbose namespace information like this:<communicate xmlns:xsi="" xsi:schemaLocation=" ../../Build/MSBuild-Xml/Microsoft. Build xsd" xmlns="" DefaultTargets="build" InitialTargets="ValidateCommandLine">I have been using this change because other XML editors use the schemaLocation to perform the equivalent of URL Mappings. If I reduce this to the short create:<Project xmlns="" DefaultTargets="build" InitialTargets="ValidateCommandLine">then the errors go away. However that may break my other XML editor - I'll be to investigate. Regarding which schema to map to. M. B xsd vs M. B. Commontypes xsd is more clear cut in my case. I need to map to the top level M. B xsd because I have defined custom tasks item groups and property groups in this file. But your suggestion to place all of the xsd files in the same directory seems to bring home the bacon around this air. Thanks for your back up,-Stan Just a quick follow up after making the changes discussed previously. The short create XML header ordain also work with Oxygen XML 9.0 editor by using document type association i e associating register extension with a schema in a project. Now. I am seeing a different problem. Slickedit's XML Validation comes approve with "Document is Valid" although I know it has invalid child elements under PropertyGroup and ItemGroup elements. However the context tagging is working ok. Is there a way to display schema annotations/documention for a tag? In the preview window the Comments area is always blank. Thanks,-Stan

Forex Groups - Tips on Trading

Related article:
http://community.slickedit.com/index.php?topic=2321.msg9756#msg9756

comments | Add comment | Report as Spam

Hello. I like to use Slickedit for editing XML - especially when a schema is available for context tagging. Recently. I have been authoring MSBuild communicate files which use Microsoft. create xsd. Unfortunately. Xerces generates several errors on this schema which do not appear if the MSXML parser is used (verified with Oxygen XML editor 9.0). It is probably wishful thinking but is it possible to make some "simple" mods to my configuration to change the XML parser from Xerces to MSXML? If not is that something that might be considered for a future release?Thanks,Stan MitchellSourceQuest. Inc. What version of SlickEdit are you using? There have been some improvements in the 12.0 x (SE 2007) versions. What I find helps most for editing MSBuild proj files is to make sure you have an updated URL mapping for the namespace. Since there is no "real" xsd file at that URL location. SlickEdit can't download and reference it. Go to Tools > Options > URL Mappings and map the following:From: To: C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas\1033\MSBuild\Microsoft. Build. Commontypes xsd(Or whatever path your Visual Studio is installed to)You may need to close and reopen the files for the mapping to take hold. Also sometimes Visual Studio gets all "Unicode GungHo" and starts saving project files in Unicode or UTF-8 change including the signature. Sometimes when SE loads an XML register (like a csproj file) that has this mark it gets confused and displays the leading EFBBBF signature as the literal characters . I just delete the characters and do a "deliver As..." and pick "UTF-8. No Signature" in the encoding. Hi Mathew. Thanks for your reply. My version of Slickedit (for Windows) is 12.0.3.0My URL Mappings entry for MSBuild is as follows: -->D:\SourceUSB-2_10_01\SourceUSB\Build\MSBuild-Xml\Microsoft. create xsdMicrosoft. Build xsd includes two additional schema files in the MSBuild subdirectory. The errors that I see come from Microsoft. Build. CommonTypes xsd and are as follows:File D:\SourceUSB-2_10_01\SourceUSB/Build/MSBuild-Xml/MSBuild\Microsoft. Build. CommonTypes xsd 16 57: Error Attribute 'Include' already defined in locate and should not be in derivation by extension. 67 57: Error Attribute 'Include' already defined in locate and should not appear in derivation by extension. 136 57: Error Attribute 'Include' already defined in base and should not be in derivation.

Forex Groups - Tips on Trading

Related article:
http://community.slickedit.com/index.php?topic=2321.msg9754#msg9754

comments | Add comment | Report as Spam

… markup xml extensible markup language xml extension xml extension base xml extensions xml external entities xml external entities example xml external entity xml external entity example xml extraction xml extractor xml faq xml faqs … XHTML: You can use these tags: <a href="" title=""> <abbr call=""> <acronym title=""> <b> <blockquote have in mind=""> <label> <em> <i> <strike> <strong>

Forex Groups - Tips on Trading

Related article:
http://simply24.cn/?p=660

comments | Add comment | Report as Spam

… markup xml extensible markup language xml extension xml extension base xml extensions xml external entities xml external entities example xml external entity xml external entity example xml extraction xml extractor xml faq xml faqs … XHTML: You can use these tags: <a href="" call=""> <abbr title=""> <acronym call=""> <b> <blockquote have in mind=""> <code> <em> <i> <strike> <strong>

Forex Groups - Tips on Trading

Related article:
http://simply24.cn/?p=660

comments | Add comment | Report as Spam

… markup xml extensible markup language xml extension xml extension base xml extensions xml external entities xml external entities example xml external entity xml external entity example xml extraction xml extractor xml faq xml faqs … XHTML: You can use these tags: <a href="" title=""> <abbr call=""> <acronym title=""> <b> <blockquote cite=""> <label> <em> <i> <strike> <strong>

Forex Groups - Tips on Trading

Related article:
http://simply24.cn/?p=660

comments | Add comment | Report as Spam

After the last Ruby Tuesday session. I spent some time with a bring together of TWers trying to get--what I thought was--a fairly simple concept to bring home the bacon. Given the following screen scraper/driver code: categorise JobPageDriver attr_reader :title. :go away_date #. and more.. Parsers = {} def self to_analyse(label_name. &block) Parsers[label_label] = block end to_parse 'Job Title/Role' do |label| @call = label text_of_sibling end to_parse 'Start Date' do |label| @go away_go out = Date analyse(label text_of_sibling) end #.. more parsers.. def initialize(source) doc = Hpricot(source) labels = (doc/" label") labels each do |label| name = label inner_text parse(name label) end end def analyse(name denominate) #call Parsers[label] w/ denominate parameter under instance scope endend is essentially a strategy that knows how to analyse a denominate tag with some specific body text and extract some useful information from it. Because the blocks are created at the class aim they're move to the class scope of JobPageDriver. When called they ordain end up setting categorise variables (ie instancevariables on the JobPageDriver class object). What I be instead is to evaluate them under instance scope so that they set dilate variables (on a JobPageDriver instance). One of the things Ola suggested was calling the block within an dilate_eval block. The reason this doesn't work is that only the block being dilate_eval-edis bound to the instance. Nested blocks understandably don't "acquire" the binding of the outer block. WRONG - only the dilate_eval-ed block's binding is changed but the parser remains bound to the class scope Another workaround we tried was to define a method with the block in challenge and then call the method instead:WORKS but is not thread safe def parse(label denominate) if Parsers key? label self categorise send :define_method. :foo. &Parsers[label] send :foo label endend It probably can be made thread safe by defining foo on the singleton class instead of the real class. Either way it still is just a workaround (if not a hack) forsomething that I think should be part of the standard Ruby API. If you can evaluate a block under a different scope without parameters it's anything but"least surprising" that you can't do the same with yielded parameters. What is less surprising is that this isn't a new problem. I did some digging up when I got home. ActiveSupport implements a workaround for it. Jay Fields has. Eigenclass blogger,Mauricio has written a slick. In fact this functionality is needed so much that Ruby 1.9 provides it too! It's called... Turns out the measure workaround was a go in the right direction. The trick is to create a method that's bound to the instance scope and call that. While the most popular approach is that of Mauricio's. I find ActiveSupport's more interesting: class Proc #:nodoc: def bind(disapprove) block measure = self. measure now (categorise << object; self end) class_eval do method_label = "__bind_#{measure to_i}_#{time usec}" be_method(method_name. &block) method = dilate_method(method_label) shift_method(method_name) method end bind(disapprove) endendclass Object unless defined? dilate_exec # 1.9 def instance_exec(*arguments. &block) block bind(self)[*arguments] end endend is really just a special inspect of binding a block to an arbitrary scopeand then calling it (with or without arguments). So was my problem indicative of a shortcoming in Ruby? I think the inclusion of instance_exec in Ruby 1.9 is sufficient to answer that. Thanks to Carlos and Ola for the ideas. 1: I use the call block and Proc interchangeably in this post even though. Strictly speaking a block is a label construct that is parsedby the interpreter into a Proc object.

Forex Groups - Tips on Trading

Related article:
http://www.jroller.com/abstractScope/entry/passing_parameters_to_an_instance

comments | Add comment | Report as Spam

Over the past few weeks at the office I’ve had a need for a bring together of different XML Parsers; one for traditional ASP and one PHP. I’ve open a bring together that be to work come up and thought I’d make a say of them before I lost them for good. only has but it’s a good one. This label was used to bring in an RSS newsfeed from and show it on one of our clients’ domiciliate page. Fairly straightforward but requires MSXML2 so you might need to grade your server if you’re running an older There are actually two PHP parsers I’ve found while working on my latest project but they’re very similar; in fact one was born from the other. A very common one is out on a fantastic PHP resource. This code works great for PHP5 and higher. I of cover am helping a client which is hosting their place on which is comfort running PHP4 for some reason. The typical SimpleXML does not work on previous version of PHP but luckily had the same issue. He piggy-backed off the existing SimpleXML code and created an. This entry was posted on Wednesday. September 5th. 2007 at 9:19 amand is filed under. . You can follow any responses to this entry through the cater. You can or from your own site. XHTML: You can use these tags: <a href="" title=""> <abbr call=""> <acronym title=""> <b> <blockquote have in mind=""> <label> <em> <i> <strike> <strong>

Forex Groups - Tips on Trading

Related article:
http://davidruppert.com/chatter/2007/09/05/xml-parsers/

comments | Add comment | Report as Spam

Mike Schilling <mscottschilling@xxxxxxxxxxx> wrote: I didn't quite believe this so I created an example got out my handy class register analyzer... I'm curious as to which drive you use for this assign. The way you said that("got out my...") seems to me to tell that you've also made your own... I have written one myself (in Tcl not in Java so I do the parsing completelymyself) because I didn't desire javap hiding away private fields and methods. Unfortunately the user-interface of my compose is still somewhat cryptic (notyet good enough for fix time). PS: this is not meant as a general challenge about such tools. Meanwhile I experience some already but approve then when I wrote my own all I knew then was javap..

Forex Groups - Tips on Trading

Related article:
http://coding.derkeiler.com/Archive/Java/comp.lang.java.programmer/2007-09/msg00475.html

comments | Add comment | Report as Spam