December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Fwd: problem while parsing xml

by Sven Van Caekenberghe

And it would be good if monty talked directly on the list ;-) On 28 Dec 2013, at 11:37, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks for forwarding the message, Stef. > > Good to know. But, it would still be good to have the error message point to the root cause :) > > Cheers, > Doru > > > > > On Sat, Dec 28, 2013 at 10:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > Begin forwarded message: > >> From: "monty" <monty.os(a)engineer.com> >> Subject: Re: [Pharo-dev] problem while parsing xml >> Date: 28 Dec 2013 01:41:36 GMT+1 >> To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> >> Thanks for the CCs. I've identified the sources of the problem(s) and am working on it now and should have it fixed soon (though its not entirely confined to XMLParser, but the fixes outside are minimal). >> >> NOTE: You can always just disable resolvesExternalEntities: and isValidating: (or use parse:usingNamespaces:validation:externalEntities: with the last two args false) if they are causing problems. >> >>> ----- Original Message ----- >>> From: StÃ©phane Ducasse >>> Sent: 12/27/13 04:42 AM >>> To: Pharo Development List >>> Subject: Re: [Pharo-dev] problem while parsing xml >>> >>> ok I missed the example in the mail of satoshi I will try to have a look or at leat write a test. >>> >>> On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> Hi Hernan >>>> >>>> how did you reproduce the bug? >>>> Because it would be nice to fix it. >>>> >>>> Stef >>>> >>>> On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>>> >>>>> I have tried in Pharo 2.0 configurations from Config Browser (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main (ConfigurationOfXMLParser-monty.37) and both have this bug. >>>>> HernÃ¡n >>>>> >>>>> 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> Hi Satoshi >>>>> >>>>> Did you try with the latest configuration of XMLParser? >>>>> Because I do not know what it is in Moose. >>>>> Stef >>>>> >>>>> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>>> >>>>> > Hello >>>>> > >>>>> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >>>>> > Pharo2.0 Latest update: #20628) >>>>> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >>>>> > >>>>> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >>>>> > 2. select and inspect it below: >>>>> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >>>>> >>>>> > <!DOCTYPE score-partwise PUBLIC >>>>> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >>>>> > "http://www.musicxml.org/dtds/partwise.dtd"> >>>>> > <score-partwise version="3.0"> >>>>> > <part-list> >>>>> > <score-part id="P1"> >>>>> > <part-name>Music</part-name> >>>>> > </score-part> >>>>> > </part-list> >>>>> > <part id="P1"> >>>>> > <measure number="1"> >>>>> > <attributes> >>>>> > <divisions>1</divisions> >>>>> > <key> >>>>> > <fifths>0</fifths> >>>>> > </key> >>>>> > <time> >>>>> > <beats>4</beats> >>>>> > <beat-type>4</beat-type> >>>>> > </time> >>>>> > <clef> >>>>> > <sign>G</sign> >>>>> > <line>2</line> >>>>> > </clef> >>>>> > </attributes> >>>>> > <note> >>>>> > <pitch> >>>>> > <step>C</step> >>>>> > <octave>4</octave> >>>>> > </pitch> >>>>> > <duration>4</duration> >>>>> > <type>whole</type> >>>>> > </note> >>>>> > </measure> >>>>> > </part> >>>>> > </score-partwise> >>>>> > ' readStream. >>>>> > >>>>> > 3. and get DNU: SmallInteger>>asciiValue >>>>> > >>>>> > 'case of XMLZincClient>>#get: >>>>> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >>>>> > returns binaryStream? >>>>> > >>>>> > >>>>> > -- >>>>> > -- >>>>> > "NISHIHARA Satoshi" >>>>> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >>>>> > <PharoDebug.log> >>>>> >>>>> >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 28, 2013

Re: [Pharo-dev] Fwd: problem while parsing xml

by Tudor Girba

Thanks for forwarding the message, Stef. Good to know. But, it would still be good to have the error message point to the root cause :) Cheers, Doru On Sat, Dec 28, 2013 at 10:51 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > > Begin forwarded message: > > *From: *"monty" <monty.os(a)engineer.com> > *Subject: **Re: [Pharo-dev] problem while parsing xml* > *Date: *28 Dec 2013 01:41:36 GMT+1 > *To: *"StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > > Thanks for the CCs. I've identified the sources of the problem(s) and am > working on it now and should have it fixed soon (though its not entirely > confined to XMLParser, but the fixes outside are minimal). > > NOTE: You can always just disable resolvesExternalEntities: and > isValidating: (or use parse:usingNamespaces:validation:externalEntities: > with the last two args false) if they are causing problems. > > > > ----- Original Message ----- > From: StÃ©phane Ducasse > Sent: 12/27/13 04:42 AM > To: Pharo Development List > Subject: Re: [Pharo-dev] problem while parsing xml > > ok I missed the example in the mail of satoshi I will try to have a look > or at leat write a test. > > On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > Hi Hernan > > how did you reproduce the bug? > Because it would be nice to fix it. > > Stef > > On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > > I have tried in Pharo 2.0 configurations from Config Browser > (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from > http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main(ConfigurationOfXM… and both have this bug. > HernÃ¡n > > 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> Hi Satoshi >> >> Did you try with the latest configuration of XMLParser? >> Because I do not know what it is in Moose. >> Stef >> >> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >> >> > Hello >> > >> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >> > Pharo2.0 Latest update: #20628) >> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >> > >> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >> > 2. select and inspect it below: >> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" >> standalone="no"?> >> >> > <!DOCTYPE score-partwise PUBLIC >> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >> > "http://www.musicxml.org/dtds/partwise.dtd"> >> > <score-partwise version="3.0"> >> > <part-list> >> > <score-part id="P1"> >> > <part-name>Music</part-name> >> > </score-part> >> > </part-list> >> > <part id="P1"> >> > <measure number="1"> >> > <attributes> >> > <divisions>1</divisions> >> > <key> >> > <fifths>0</fifths> >> > </key> >> > <time> >> > <beats>4</beats> >> > <beat-type>4</beat-type> >> > </time> >> > <clef> >> > <sign>G</sign> >> > <line>2</line> >> > </clef> >> > </attributes> >> > <note> >> > <pitch> >> > <step>C</step> >> > <octave>4</octave> >> > </pitch> >> > <duration>4</duration> >> > <type>whole</type> >> > </note> >> > </measure> >> > </part> >> > </score-partwise> >> > ' readStream. >> > >> > 3. and get DNU: SmallInteger>>asciiValue >> > >> > 'case of XMLZincClient>>#get: >> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >> > returns binaryStream? >> > >> > >> > -- >> > -- >> > "NISHIHARA Satoshi" >> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >> > <PharoDebug.log> >> >> > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 28, 2013

[ANN] Ephestos

by kilon alios

Still long way to go until its really useful but following your advice I decided to release it to public and announce it instead of having it hidden. Ladies , gentleman and hybrids I present to you Ephestos, my visual coding project for graphics and sound. This is my very first project with Pharo and Smalltalk and my second coding project. Just released a version 0.1 so as you can imagine you wont see anything impressive yet but none the less it included my first Ephestos tool, Hyperion a vector graphics editor. Right now it can only edit a single vector straight line and add new lines. I am working now on version 0.2 that will allow you to edit other lines , moving them around with mouse and add support for bezier curves. So its moving .... slowly .... very slowly... but moving none the less :D You can find Ephestos here along with installation instructions and how to use Hyperion. Suffice to say you will need Pharo 3 to run it http://www.smalltalkhub.com/#!/~kilon/Ephestos I hope I will have Version 1 in January 2015 that will set out the base functionality of Hyperion which will be a complete very basic vector editor with features you will expect to find in a vector editor like moving lines around, editing them, adding new control points to them, making gradients and basic layer support. Will also introduce Prometheas a new documentation system . I would like to thank all people who make Pharo so amazing and cool, my problems with this project have more to do with my understanding on how to code this thing properly than pharo and its libraries. So I definitely did not expected it to be such a smooth ride.

Dec. 28, 2013

Error in loading libreries

by Lorenzo Schiavina

Hi, every time I try to load a package from Monticello, I receive the message: ERROR: MCHttpRepository expected. Can anybody tell me why and suggest me a workeround? Many thanks and season's greetings Lorenzo

Dec. 28, 2013

Fwd: problem while parsing xml

by StÃ©phane Ducasse

Begin forwarded message: > From: "monty" <monty.os(a)engineer.com> > Subject: Re: [Pharo-dev] problem while parsing xml > Date: 28 Dec 2013 01:41:36 GMT+1 > To: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > > Thanks for the CCs. I've identified the sources of the problem(s) and am working on it now and should have it fixed soon (though its not entirely confined to XMLParser, but the fixes outside are minimal). > > NOTE: You can always just disable resolvesExternalEntities: and isValidating: (or use parse:usingNamespaces:validation:externalEntities: with the last two args false) if they are causing problems. > >> ----- Original Message ----- >> From: StÃ©phane Ducasse >> Sent: 12/27/13 04:42 AM >> To: Pharo Development List >> Subject: Re: [Pharo-dev] problem while parsing xml >> >> ok I missed the example in the mail of satoshi I will try to have a look or at leat write a test. >> >> On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> >>> Hi Hernan >>> >>> how did you reproduce the bug? >>> Because it would be nice to fix it. >>> >>> Stef >>> >>> On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>>> >>>> I have tried in Pharo 2.0 configurations from Config Browser (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main (ConfigurationOfXMLParser-monty.37) and both have this bug. >>>> HernÃ¡n >>>> >>>> 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> Hi Satoshi >>>> >>>> Did you try with the latest configuration of XMLParser? >>>> Because I do not know what it is in Moose. >>>> Stef >>>> >>>> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>> >>>> > Hello >>>> > >>>> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >>>> > Pharo2.0 Latest update: #20628) >>>> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >>>> > >>>> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >>>> > 2. select and inspect it below: >>>> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >>>> > <!DOCTYPE score-partwise PUBLIC >>>> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >>>> > "http://www.musicxml.org/dtds/partwise.dtd"> >>>> > <score-partwise version="3.0"> >>>> > <part-list> >>>> > <score-part id="P1"> >>>> > <part-name>Music</part-name> >>>> > </score-part> >>>> > </part-list> >>>> > <part id="P1"> >>>> > <measure number="1"> >>>> > <attributes> >>>> > <divisions>1</divisions> >>>> > <key> >>>> > <fifths>0</fifths> >>>> > </key> >>>> > <time> >>>> > <beats>4</beats> >>>> > <beat-type>4</beat-type> >>>> > </time> >>>> > <clef> >>>> > <sign>G</sign> >>>> > <line>2</line> >>>> > </clef> >>>> > </attributes> >>>> > <note> >>>> > <pitch> >>>> > <step>C</step> >>>> > <octave>4</octave> >>>> > </pitch> >>>> > <duration>4</duration> >>>> > <type>whole</type> >>>> > </note> >>>> > </measure> >>>> > </part> >>>> > </score-partwise> >>>> > ' readStream. >>>> > >>>> > 3. and get DNU: SmallInteger>>asciiValue >>>> > >>>> > 'case of XMLZincClient>>#get: >>>> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >>>> > returns binaryStream? >>>> > >>>> > >>>> > -- >>>> > -- >>>> > "NISHIHARA Satoshi" >>>> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >>>> > <PharoDebug.log> >>>> >>>> >

Dec. 28, 2013

Re: [Pharo-dev] Nautilus: tab key change focus

by GOUBIER Thierry

Hi Jura, I had a short look (kind of hard at the moment) and I noticed that Ctrl+tab was working to switch the focus around correctly, but maybe in an incorrect order. This could be fixed by adding the morphs at creation time in a different order. However, Ctrl+Shift+Tab wasn't working :( And tab has no effect in the filter (neither focus change nor text input). Your solution is a bit heavy handed for me, I was thinking of something more like: searchWidget onKeyCombination: Character tab asKeyCombination do: [self giveFocusToPackage]. Don't forget that, as you're touching the focus tab order, you have a duty to make it complete (i.e. all widgets can be tabbed to starting from any widget). Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Juraj Kubelka [juraj.kubelka(a)gmail.com] Date d'envoi : vendredi 27 dÃ©cembre 2013 18:49 Ã : Pharo Development List Objet : Re: [Pharo-dev] Nautilus: tab key change focus Thanks for the advice. I have just tried to add my own key stroke handling and I face interesting issue. The first time I enter the package filter input field, everything works. When I press down-key, it change focus to package list. But since then whenever I enter again the filter, any key stroke change the focus back to package list. I do not see any glue right now. The code is like this: buildPackageSearch "It is an search dialog which filters package list" searchWidget := SearchMorph new model: self; updateSelector: #packageSearchUpdate:; ghostText: 'Type: Pkg1|^Pkg2|Pk.*Core$'; list: SharedValueHolder instance; useSelectionIndex: false; setIndexSelector: #packageSearchUpdate:; keystrokeSelector: #packageSearchKeyStroke:; yourself. ^ searchWidget packageSearchKeyStroke: anEvent (anEvent keyCharacter = Character arrowDown) ifTrue: [ self giveFocusToPackage. ^ true ]. ^ false Thanks. Jura

Dec. 28, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by Nicolai Hess

On problem with the current solution (from 12144) is that TextModels readSelectionHolder is not updated when setSelection: is called. So, if you read the selection from the PluggableTextMorph it has always the same value (from its initialization) and not the actual selection (if you use the mouse to set a new selection). Compare TextModel>>setSelection: in Pharo3 and Pharo2 ( keep in mind that Pharo3 uses a MorphicTextAdapter between the model (TextModel) and the view (PluggableTextMorph). But I don't like this version (12144 with correct readSelectionHolder updating). I find it pretty confusing how textselection is handled in TextModel, MorphicTextAdapter, PluggableTextMorph and TextEditor. And look at issue 12487 <https://pharo.fogbugz.com/default.asp?12487> and my last comment in 12389 <https://pharo.fogbugz.com/default.asp?12389>(this is about textselection initializating from building the TextMorph with spec, TextModels spec does not handle the current selection. And I couldn't find a way to tell SpecInterpreter how to use the actual selection (if it is of kind Interval)) Nicolai 2013/12/27 Andrei Chis <chisvasileandrei(a)gmail.com> > PluggableTextMorph maintains its own selectionInterval. > > When the PluggableTextMorph >>selectionInterval: it is called it sets the > selection in the model. > This will trigger MorphicTextAdapter>>setSelectionFromModel: that should > adapt the selection in the morph: > MorphicTextAdapter >>setSelectionFromModel: aSelection > self widget ifNotNil: [:w | > w selectionInterval ~= aSelection ifTrue: [ > w setSelection: aSelection ]]. > > However, the second test (w selectionInterval ~= aSelection) will always > return false. This is because > PluggableTextMorph>>selectionInterval has the following implementation > '^ textMorph editor selectionInterval' > > And in the editor the selection is already correct (even > before PluggableTextMorph >>selectionInterval: is called). > > Actually most of the methods from PluggableTextMorph that change the > selection also explicitly update the > selectionInterval instance variable. > > So the previous solution should work. > > @Doru this is related with Spec, so we should not have it in Glamour. > > > > On Fri, Dec 27, 2013 at 5:07 PM, Benjamin < > Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> I think that when the model is notified, it will set it in the morph >> So it will happen twice >> >> Ben >> >> On 27 Dec 2013, at 15:52, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Wouldn't then explicitly setting the selection of the morph before >> setting it in the model be ok? >> >> PluggableTextMorph>>selectionInterval: sel >> selectionInterval := sel. >> setSelectionSelector >> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >> >> >> On Fri, Dec 27, 2013 at 4:28 PM, Benjamin < >> Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >>> ok :( >>> Then I run out of brilliant idea :P >>> >>> >>> Ben >>> >>> On 27 Dec 2013, at 15:25, Andrei Chis <chisvasileandrei(a)gmail.com> >>> wrote: >>> >>> Adding 'self changed' at the end of the current PluggableTextMorph>>selectionInterval: >>> doesn't solve the problem. >>> >>> >>> On Fri, Dec 27, 2013 at 4:15 PM, Benjamin < >>> Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>> >>>> Because when the focus changes, the morph is proposed to redraw itself >>>> Try with a >>>> >>>> self changed >>>> >>>> at the end >>>> >>>> Ben >>>> >>>> On 27 Dec 2013, at 14:44, Andrei Chis <chisvasileandrei(a)gmail.com> >>>> wrote: >>>> >>>> >>>> The change that seems to have caused this problem is in >>>> PluggableTextMorph>>selectionInterval: The selectionInterval instance >>>> variable of the morph is not set any more; only the model is updated, which >>>> doesn't seem to update the morph. >>>> >>>> PluggableTextMorph>>selectionInterval: sel >>>> setSelectionSelector >>>> ifNil: [ selectionInterval := sel ] >>>> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >>>> >>>> This could be solved like bellow, though I'm not sure it is the best >>>> solution. >>>> If I put a halt in PluggableTextMorph >>inspectIt and hit proceed the >>>> the selection is inspected correctly, without this modification. >>>> >>>> PluggableTextMorph>>selectionInterval: sel >>>> selectionInterval := sel. >>>> setSelectionSelector >>>> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >>>> >>>> >>>> >>>> >>>> >>>> On Fri, Dec 27, 2013 at 3:11 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>>> >>>>> >>>>> On 27 Dec 2013, at 13:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> wrote: >>>>> >>>>> > Hi guys >>>>> > >>>>> > we should not let the system in such state. We cannot inspect print >>>>> expression in the debugger. >>>>> > Does anybody have an idea of the change that broke it? >>>>> > >>>>> Yes: >>>>> >>>>> https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection >>>>> >>>>> it was added in 655, so for reverting the easiest is to dl 654, do a >>>>> merge and look at all the changes >>>>> (there are just 4-5 that are not re-catorizations). >>>>> >>>>> This is on my TODO nextâ¦ >>>>> >>>>> Marcus >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >

Dec. 27, 2013

Re: [Pharo-dev] Thank you for Pharo

by Alexis Parseghian

VB>> Thank you for Pharo â¦. I'd like to add my voice to this. I've been away from Pharo for several months, although I kept reading the lists. The amount of stuff happening since before 2.0 was finalized is just amazing. VB>> - 64 Bit VM and MultiCore Support SD> first we will really integrate all the work of eliot. This too is important to me. I've found multi-arch in debian sid (amd64) to be broken at best, which leaves me with just an old notebook (sid i386) to run Pharo on. Or full-blown i386 virtual machines, which is also far from ideal. Beyond that, considering its history I like to think of Smalltalk as inherently multi-platform, and expect (long-term) Pharo to follow in those steps and be able to run on any system, any arch. (Yes, I'm aware of the limited resources of the team :) ) On a personal level, beyond debian/amd64 I'd love to be able to run it on (debian, openbsd) SPARC64... I'm afraid hacking the VM is beyond me at this point, but I'd like to help.

Dec. 27, 2013

Compiling chapter of "Pharo for the Enterprise"

by Natalia Tymchuk

Hello. Merry Christmas. I write a chapter to "Pharo for the Enterprise". And I want to compile it, but when I executing ./compile.sh DSL/DSL.pier, like it is writen here: https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english/bl… , I get No yet implemented. I just start this chapter and it isn't ready to be added to the PFTE.tex. Should I add it to PFTE.tex or there are another way? What can you recomend me? Thanks. Best regards, Natalia

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by StÃ©phane Ducasse

> In any case, it is strange that the items in the CharacterSet cannot be printed by the EyeInspector. GTInspector shows them properly (see attached). > > It gets even worse. Try doing this in a fresh Pharo 3.0 image: > > CharacterSet allCharacters explore probably because the explorer is using at: something. but CharacterSet allCharacters inspect works with the problems I mentioned. > > and you will get a DNU that 'Instances of CharacterSet are not indexable'. > > Cheers, > Doru > > <MessageNotUnderstood: SmallInteger>>asciiValue.png> > > > On Fri, Dec 27, 2013 at 6:47 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I read a bit about internal public and other dtd and it looks like this is ok > > Ahhh. > > The bug was showing a parser problemâ¦. so I could not get that it was related to the network :) > >> Because monty's code downloads the DTD for validation from >> >> http://www.musicxml.org/dtds/partwise.dtd >> >> I should check if is the "right thing to do" because it would increase parsing time significantly. At least it should be an option. >> >> Cheers, >> >> Hernan >> >> >> 2013/12/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <!DOCTYPE score-partwise PUBLIC >> "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >> "http://www.musicxml.org/dtds/partwise.dtd"> >> <score-partwise version="3.0"> >> <part-list> >> <score-part id="P1"> >> <part-name>Music</part-name> >> </score-part> >> </part-list> >> </score-partwise> >> ' readStream. >> >> produces the error >> while >> >> XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <score-partwise version="3.0"> >> <part-list> >> <score-part id="P1"> >> <part-name>Music</part-name> >> </score-part> >> </part-list> >> </score-partwise> >> ' readStream. >> >> does not. >> >> Stef >> >> > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 27, 2013