Peter B. West wrote:
> Ok, so how do we drive this thing? Is it zoomable? I couldn't find
> pietsch on there either.
Sorry, I meant to show the path (it took a while to figure out):
Joerg gave us:
http://cvs.apache.org/~sgala/nightmap.html
Then (hoping to find something instructive) look at:
h
J.Pietschmann wrote:
> BTW, I notice the absence of you and Peter from
> http://cvs.apache.org/~sgala/nightmap.html
OK, I should be on there the next time the map is regenerated. Now that you
guys know how to get here, come on over!
Victor Mote
---
J.Pietschmann wrote:
Victor Mote wrote:
BTW, I notice the absence of you and Peter from
http://cvs.apache.org/~sgala/nightmap.html
Ok, so how do we drive this thing? Is it zoomable? I couldn't find
pietsch on there either.
Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Victor Mote wrote:
I never bit the emacs bullet, and don't directly know the impact there.
GNU emacs 21 knows about UTF-8. Unfortunately, the NT port seems to
be less rock solid than usual, I got the first emacs crashes since
I abandoned Solaris 2.1 in, well, lets say an epoch or two ago.
BTW, I no
Victor Mote wrote:
Peter B. West wrote:
(I wouldn't say it was heated.) I am curious about the impact of
someone working without any formal IDE, and just using (X)Emacs and JDEE
for development. As far as I know, XEmacs does not support Unicode, but
if the non-ASCII characters were restricted t
Peter B. West wrote:
> (I wouldn't say it was heated.) I am curious about the impact of
> someone working without any formal IDE, and just using (X)Emacs and JDEE
> for development. As far as I know, XEmacs does not support Unicode, but
> if the non-ASCII characters were restricted to comments,
Victor Mote wrote:
J.Pietschmann wrote:
OOps, I didn't think about that. We could
a) Force ISO-8859-1 for all Java source files in the build file.
Is this a discrimination of, ummm, non-western contributors
who might want to have their names in their native script
in the files?
b) Keep a
J.Pietschmann wrote:
> OOps, I didn't think about that. We could
> a) Force ISO-8859-1 for all Java source files in the build file.
> Is this a discrimination of, ummm, non-western contributors
> who might want to have their names in their native script
> in the files?
> b) Keep a list
Le Vendredi, 4 juil 2003, à 21:12 Europe/Zurich, J.Pietschmann a écrit :
Bertrand Delacretaz wrote:
Sure - it is by accident that comments in the jfor source code
contains non-ASCII chars (in people's names IIRC).
OOps, I didn't think about that. We could
What I meant is that I think (or rath
Bertrand Delacretaz wrote:
Sure - it is by accident that comments in the jfor source code contains
non-ASCII chars (in people's names IIRC).
OOps, I didn't think about that. We could
a) Force ISO-8859-1 for all Java source files in the build file.
Is this a discrimination of, ummm, non-western
Le Jeudi, 3 juil 2003, à 21:16 Europe/Zurich, J.Pietschmann a écrit :
...And, uh, comment language is *english*, guys :-)
Sure - it is by accident that comments in the jfor source code contains
non-ASCII chars (in people's names IIRC).
No problem in removing the accents!
-Bertrand
--
Christian Geisert wrote:
> > Java source is Unicode, and I don't think the encoding would matter, but
>
> Java source is whatever the platform encoding is (see file.encoding
> system property) so the best thing is to avoid chars > 127 at all
> (use \u instead) ... uh this won't work in this ca
Christian Geisert wrote:
Java source is whatever the platform encoding is (see file.encoding
system property) so the best thing is to avoid chars > 127 at all
(use \u instead) ... uh this won't work in this case as
these are comments. Maybe there's a workaround for special french
characters (l
13 matches
Mail list logo
