Re: [Pharo-users] Writing XML

> Sent: Friday, September 15, 2017 at 4:30 PM > From: "Jimmie Houchin" > To: "Any question about pharo is welcome" > Subject: Re: [Pharo-users] Writing XML > > I didn't pay attention to this previously. But I just noticed that using >

[Pharo-users] Pharo 7 license question

Hello, Pharo 7 to my understanding fundamentally changes Pharo. It is my understanding that Pharo 7 starts with a core Pharo kernel and like many languages out there, imports or adds code from a variety of external sources to the image being built. With that understanding, I am curious if

Re: [Pharo-users] Writing XML

I didn't pay attention to this previously. But I just noticed that using #printToFileNamed: preserved the DOM tree's original line ending where as previously I had to insure the the XMLWriter #lineEnding was changed from defaultLineEnding to canonicalLineEnding. The original document used LF

Re: [Pharo-users] Writing XML

Thanks for the reply. I appreciate the education the people on this list provide. I was already doing the XMLDOMParser #onFileNamed: to open the file. It was showing the correct #encoding for the parsed file. It was just the writing of the nearly identical file which was different. I tried as

Re: [Pharo-users] Usability issues with Calypso

You say The current behaviour is trying to be close to single source pane behaviour of old browsers. I think that's a bit of the problem. For me, nautilus is a single source pane browser and it looks like a single source pane browser. Calypso looks like something else - it looks like a typical

Re: [Pharo-users] Writing XML

If you want to write a DOM tree to a file, send #printToFileNamed: (or a related message like #canonicallyPrintToFileNamed: or #printToFileNamed:beforeWritingDo:) to the root. See the XMLNode "printing" category for more. This will automatically encode the file with the encoding the