From: "Anthony Green" <green@redhat.com>
To: <tromey@redhat.com>
Cc: <java@gcc.gnu.org>, <rhug-rhats@sources.redhat.com>
Subject: Re: property files and character encodings
Date: Mon, 10 Sep 2001 21:55:00 -0000 [thread overview]
Message-ID: <00c501c13a7e$80f03240$5be6b4cd@cygnus.com> (raw)
In-Reply-To: <87zo82csof.fsf@creche.redhat.com>
Tom wrote:
> I just checked in my patch, which is a superset of this one.
> There's another case lower down with the same problem.
Great! Thanks!
With this change I am able to perform xsl translations with Xalan. I've
compiled org.apache.xalan.xslt.Process into a program, xsltp, which reads XML
and XSL files to generate appropriate output (like HTML).
xsltc is another program which compiles XSL files into .class files which may
be compiled with gcj and linked with the Xalan runtime to perform similar
translations.
Xalan is huge - so the fact that we can build and run it is an important
milestone in gcj's development.
Thanks!
AG
next prev parent reply other threads:[~2001-09-10 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 20:03 Anthony Green
2001-09-10 20:15 ` Tom Tromey
2001-09-10 21:55 ` Anthony Green [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-09 22:09 Anthony Green
2001-09-10 19:27 ` Tom Tromey
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='00c501c13a7e$80f03240$5be6b4cd@cygnus.com' \
--to=green@redhat.com \
--cc=java@gcc.gnu.org \
--cc=rhug-rhats@sources.redhat.com \
--cc=tromey@redhat.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).