On Tuesday, June 23, 2015 at 2:35:50 AM UTC-4, Denis McMahon wrote:
> On Sun, 21 Jun 2015 16:56:27 -0700, Sahlusar wrote:
>
> > Here is an example XML document that I am working with:
>
> > You are welcome to contribute and provide me with feedback. Thank you
> > for your continued feedback and g
On Sun, 21 Jun 2015 16:56:27 -0700, Sahlusar wrote:
> Here is an example XML document that I am working with:
> You are welcome to contribute and provide me with feedback. Thank you
> for your continued feedback and guidance.
Your XML is invalid! You have a closing MO tag with no opening tag.
>
On Mon, Jun 22, 2015 at 9:33 AM, Denis McMahon wrote:
> This is the sort of data conversion code I generally turn out in a day or
> so, it's hardly rocket science as long as you have a clear description of
> what is required. If you don't have a clear description of what is
> required, you have to
On Sunday, June 21, 2015 at 7:34:47 PM UTC-4, Denis McMahon wrote:
> On Mon, 22 Jun 2015 00:55:11 +0300, Joonas Liik wrote:
>
> > In xml for instance this is valid:
>
> >
> > 1
> >
> > .. and so is this:
> >
> > 1 2
> >
>
> What the OP needs to do is sit down with the XML and work out how
On Sunday, June 21, 2015 at 5:56:00 PM UTC-4, Waffle wrote:
> On 21 June 2015 at 17:38, Sahlusar wrote:
> >
> > [snip]
> > I do agree with you Denis that this is an unconventional approach. I was
> > wondering then that perhaps I should add additional functionality at the
> > XML to JSON step? S
On Mon, 22 Jun 2015 00:55:11 +0300, Joonas Liik wrote:
> In xml for instance this is valid:
>
> 1
>
> .. and so is this:
>
> 1 2
>
What the OP needs to do is sit down with the XML and work out how it
needs to be represented in CSV terms, and then code that transformation,
but it appears
On 21 June 2015 at 17:38, Sahlusar wrote:
>
> [snip]
> I do agree with you Denis that this is an unconventional approach. I was
> wondering then that perhaps I should add additional functionality at the XML
> to JSON step? So far, with JSON objects without nested lists (as values) I
> have been
On Sun, 21 Jun 2015 07:38:13 -0700, Sahlusar wrote:
> It is difficult to explain this to someone asynchronously and without an
> in person meeting. Moreover, the strict guidelines for disclosing
> information make it difficult for me to explain the client's
> requirements and the problems that the
It is difficult to explain this to someone asynchronously and without an in
person meeting. Moreover, the strict guidelines for disclosing information make
it difficult for me to explain the client's requirements and the problems that
they face.
I do agree with you Denis that this is an uncon
On Sunday, 21 June 2015 02:54:48 UTC-4, Denis McMahon wrote:
> On Thu, 18 Jun 2015 18:47:30 -0700, Sahlusar wrote:
>
> > I have a conundrum regarding JSON objects and converting them to CSV:
>
> I think your conundrum is that you've taken on a coding task beyond your
> abilities to comprehend,
On Thu, 18 Jun 2015 18:47:30 -0700, Sahlusar wrote:
> I have a conundrum regarding JSON objects and converting them to CSV:
I think your conundrum is that you've taken on a coding task beyond your
abilities to comprehend, and as a result not only can you not code it,
you can't even adequately d
On Thu, 18 Jun 2015 18:47:30 -0700, Sahlusar wrote:
> I have a conundrum regarding JSON objects and converting them to CSV:
>
> Context
>
> I am converting XML files to a JSON object (please see snippet below)
> and then finally producing a CSV file. Here is a an example JSON object:
This is wh
On Thu, 18 Jun 2015 18:47:30 -0700 (PDT), Sahlusar
wrote:
>Good Evening,
>
>I have a conundrum regarding JSON objects and converting them to CSV:
That's the THIRD time you've asked this, in three separate threads.
Why don't you read the answers you were given the first time?
[follow-ups set]
13 matches
Mail list logo
