You are viewing a plain text version of this content. The canonical link for it is here.
Posted to community@apache.org by "Adam R. B. Jack" <aj...@apache.org> on 2004/09/02 21:27:54 UTC
For those interested in building ASF/OSS code upon JDK 1.5...
I don't know where else to post this, but I could imagine there could be
general interest, so I'll try here.
We have a JDK 1.5 Gump running at:
http://brutus.apache.org/gump/jdk15/
http://brutus.apache.org/gump/jdk15/buildLog.html
... basically this attempts to build ASF and OSS projects using the JDK 1.5
compiler.
Some projects with issues (some JDK 1.5, some not) are listed here:
http://brutus.apache.org/gump/jdk15/project_todos.html
If you'd like a few simple pointers, see here:
http://neukadye.chalko.com/archive/000018.html
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: Non-ASCII chars in Java comments
Posted by Santiago Gala <sg...@apache.org>.
J.Pietschmann wrote:
> Adam R. B. Jack wrote:
>
>> Some projects with issues (some JDK 1.5, some not) are listed here:
>> http://brutus.apache.org/gump/jdk15/project_todos.html
>
>
> Neat!
>
> I did a quick check of the BCEL issues, and they are exclusively
> problems with non-ASCII characters. While the BCEL problems are
> easily fixed (bullet characters, probably cut&pasted from a HTML
> page, and a few german umlauts), we had a similar problem with
> a FOP source file some times ago, which was not as easily resolved,
> because it was an email address containing the characters causing
> the troubles. Ultimately, the originator allowed to pull the
> address and have his name respelled in a romanized form.
>
> Related questions:
> 1. Javac allows Java source file encodings with a greater range
> of characters, in particular UTF-8. Unfortunately, there is
> no standardized auto-detection mechanism (as for XML).
> Does anybody wants to discuss how projects/the whole ASF should
> deal with non-ASCII encodings for Java files?
Typically, IMO, the only way to deal with it involves adopting the
convention that all files in a project are UTF-8 (which can hold any
character). The Java books I read recommend using the \uXXXX convention
for high characters in source code, so that no character in a java
source is non-ASCII. I think that this convention should work in
javadocs, but never tested it.
I've just found a similar bug with OpenOffice.org java files, which
refused to compile in my es_ES.utf8 machine unless I prefixed the build
with LC_ALL=C or a similar non-utf encoding.
> 2. How should situations be handled where characters which can't
> be encoded are important, like in email addresses or IRLs
> (internationalized URLs)?
>
IMO, adopting the convention that each project tarball uses a given
encoding (UTF-8 ideally, since it minimizes breakage), and (for linux)
using LC_ALL=en_US.utf8 before building (this was the issue I found,
that some files in OpenOffice come encoded in iso-8859-1 but with no
meta-information saying so). For window I have no idea if the encoding
can be changed for a session or something.
> How do Perl developers with this issues?
>
> Regards
> J.Pietschmann
>
This issue is language independent, it is a problem that will exist
until a common encoding is used or meta information for all files is
available.
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Non-ASCII chars in Java comments
Posted by "J.Pietschmann" <pi...@apache.org>.
Adam R. B. Jack wrote:
> Some projects with issues (some JDK 1.5, some not) are listed here:
> http://brutus.apache.org/gump/jdk15/project_todos.html
Neat!
I did a quick check of the BCEL issues, and they are exclusively
problems with non-ASCII characters. While the BCEL problems are
easily fixed (bullet characters, probably cut&pasted from a HTML
page, and a few german umlauts), we had a similar problem with
a FOP source file some times ago, which was not as easily resolved,
because it was an email address containing the characters causing
the troubles. Ultimately, the originator allowed to pull the
address and have his name respelled in a romanized form.
Related questions:
1. Javac allows Java source file encodings with a greater range
of characters, in particular UTF-8. Unfortunately, there is
no standardized auto-detection mechanism (as for XML).
Does anybody wants to discuss how projects/the whole ASF should
deal with non-ASCII encodings for Java files?
2. How should situations be handled where characters which can't
be encoded are important, like in email addresses or IRLs
(internationalized URLs)?
How do Perl developers with this issues?
Regards
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org
Re: encoding weirdness on JDK 1.5 [WAS Re: For those interested in building ASF/OSS code upon JDK 1.5...]
Posted by Niclas Hedhman <ni...@hedhman.org>.
I think I saw something about the encoding of source files have changed (or
perhaps been specified), so I guess you are experiencing encoding problems
with french characters.
Cheers
Niclas
----- Original Message -----
From: "robert burrell donkin" <ro...@blueyonder.co.uk>
To: "Gump code and data" <ge...@gump.apache.org>
Sent: Thursday, September 02, 2004 10:56 PM
Subject: encoding weirdness on JDK 1.5 [WAS Re: For those interested in
building ASF/OSS code upon JDK 1.5...]
> looks cool :)
>
> what's a bit weird is that beanutils fails on an encoding issue: a
> french author tag. anyone have an clue as to whether this is likely to
> be a platform issue or whether 1.5 has tightened up the rules...?
>
> - robert
>
> On 2 Sep 2004, at 20:27, Adam R. B. Jack wrote:
>
> > I don't know where else to post this, but I could imagine there could
> > be
> > general interest, so I'll try here.
> >
> > We have a JDK 1.5 Gump running at:
> >
> > http://brutus.apache.org/gump/jdk15/
> > http://brutus.apache.org/gump/jdk15/buildLog.html
> >
> > ... basically this attempts to build ASF and OSS projects using the
> > JDK 1.5
> > compiler.
> >
> > Some projects with issues (some JDK 1.5, some not) are listed here:
> >
> > http://brutus.apache.org/gump/jdk15/project_todos.html
> >
> > If you'd like a few simple pointers, see here:
> >
> > http://neukadye.chalko.com/archive/000018.html
> >
> > regards,
> >
> > Adam
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: community-unsubscribe@apache.org
> > For additional commands, e-mail: community-help@apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
encoding weirdness on JDK 1.5 [WAS Re: For those interested in building ASF/OSS code upon JDK 1.5...]
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
looks cool :)
what's a bit weird is that beanutils fails on an encoding issue: a
french author tag. anyone have an clue as to whether this is likely to
be a platform issue or whether 1.5 has tightened up the rules...?
- robert
On 2 Sep 2004, at 20:27, Adam R. B. Jack wrote:
> I don't know where else to post this, but I could imagine there could
> be
> general interest, so I'll try here.
>
> We have a JDK 1.5 Gump running at:
>
> http://brutus.apache.org/gump/jdk15/
> http://brutus.apache.org/gump/jdk15/buildLog.html
>
> ... basically this attempts to build ASF and OSS projects using the
> JDK 1.5
> compiler.
>
> Some projects with issues (some JDK 1.5, some not) are listed here:
>
> http://brutus.apache.org/gump/jdk15/project_todos.html
>
> If you'd like a few simple pointers, see here:
>
> http://neukadye.chalko.com/archive/000018.html
>
> regards,
>
> Adam
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: community-unsubscribe@apache.org
> For additional commands, e-mail: community-help@apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org