public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Prateem Mandal <prateem@gmail.com>
To: Shawn Wagner <shawnw.mobile@gmail.com>
Cc: kawa@sourceware.org
Subject: Re: SXML support in Kawa Scheme
Date: Thu, 26 May 2022 13:46:08 +0100	[thread overview]
Message-ID: <CABj18TnWz8Sz-tpCw1N_25ky5CYoZJO-GHBCjHNWbuVb9HW9dg@mail.gmail.com> (raw)
In-Reply-To: <CAMHuZZ1oSsWLvwiibA0dBdjrGB34hKMt7V1xiLH5fhH-nVVGLA@mail.gmail.com>

Thank you Shawn for the clarifications. I will first try solving my
immediate problem using standard Java API first.

-P

On Fri, May 20, 2022 at 1:12 PM Shawn Wagner <shawnw.mobile@gmail.com>
wrote:

> My first inclination when it comes to doing XML processing in kawa beyond
> what it provides ( https://www.gnu.org/software/kawa/XML-tools.html )
> would be to use the standard Java API.
>
> But while I haven't used SSAX/SXML in kawa, experience with other scheme
> libraries is that unless it's doing fancy stuff with continuations, things
> generally work well enough out of the box.
>
>
> On Fri, May 20, 2022 at 5:02 AM Prateem Mandal via Kawa <
> kawa@sourceware.org> wrote:
>
>> Hi All,
>>
>> Is there is any library that I can use to deserialize XML file in SXML and
>> serialize SXML back to XML in Kawa. My search turned up some discussion
>> about it on SSAX mailing list and on Kawa mailing list but with no
>> definitive conclusion.
>>
>> Before I start looking into what it will take to port an existing library
>> to Kawa, I want to make sure that nothing exists.
>>
>> I would also like to know if Kawa recommends a different approach.
>>
>> Thanks
>> Prateem
>>
>

  reply	other threads:[~2022-05-26 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 12:00 Prateem Mandal
2022-05-20 12:11 ` Shawn Wagner
2022-05-26 12:46   ` Prateem Mandal [this message]
2022-06-15 19:58 ` Lassi Kortela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABj18TnWz8Sz-tpCw1N_25ky5CYoZJO-GHBCjHNWbuVb9HW9dg@mail.gmail.com \
    --to=prateem@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=shawnw.mobile@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).