jython-dev

[Jython-dev] copyright characters in source files

[Ben B. <be...@ac...>]

Hi.. a note on a different subject.

I'm using jikes to build jython.  Some time ago I got an error regarding the 
use of the copyright character in a quoted string (in sha.java).  Which was 
fine, I just edited the file and replaced the character with (c) and all was 
well.

Now, since my last upgrade, jikes gets upset when the file contains 
non-standard characters.  Even in comments.

So suddenly I find myself having to manually edit some 114 files to replace 
copyright characters with (c) in the comment headers, eg.:
// Copyright (c) Corporation for National Research Initiatives

The error jikes gives me is:

jikes +E +D -g -classpath 
"../../..:/usr/share/java/libgcj.jar:/usr/share/kaffe/rmi.jar:/usr/share/java/servlet-2.2.jar" 
ArgListCompiler.java
Charset conversion error at offset 13: Invalid or incomplete multibyte or 
wide character

You could say "just don't use jikes", but jikes is explicitly designed to 
adhere precisely to language and VM specifications; no more, no less.  So I 
would claim we *want* jython to compile with jikes because this should mean 
it will compile with any sane and compliant java compiler.

So basically what I'm going to ask is for all the copyright characters to be 
replaced with (c). :)  I realise this is an onerous task (although one that 
only took me a few minutes with a for loop in bash and a lot of repetitive 
keystrokes in vi).

If people don't have the time to do it, I will happily do this myself if 
you're willing (I have a sourceforge account, username bab).

Thanks,
	Ben.

-- 

Ben Burton
be...@ac...  |  ba...@de...
http://baasil.humbug.org.au/bab/
Public Key: finger ba...@de...

Art is the most intense mode of individualism that the world has known.
	- Oscar Wilde

Re: [Jython-dev] copyright characters in source files

[Bill K. <bi...@ct...>]

From: "Ben Burton" <be...@ac...>
> 
[...]
> So basically what I'm going to ask is for all the copyright characters to be 
> replaced with (c). :)  I realise this is an onerous task (although one that 
> only took me a few minutes with a for loop in bash and a lot of repetitive 
> keystrokes in vi).

Hi, I'm still a Python newbie (so don't know of an optimal Python
solution for this yet) but Perl is phenomenal for this sorta thing:

find somedir -type f -name "*.java" | perl -i -npe 's/\123/(c)/g'

where \123 could be the octal representation of the highbit char
to be replaced with (c).

(Note: under Windows the -i would have to be changed to something
like -i.bak because win perl can't edit files in-place.)

Hope this helps,

Bill

Re: [Jython-dev] copyright characters in source files

[Mats W. <ma...@la...>]

 >You could say "just don't use jikes", but jikes is explicitly designed to
 >adhere precisely to language and VM specifications; no more, no less.  So I
 >would claim we *want* jython to compile with jikes because this should mean
 >it will compile with any sane and compliant java compiler.

Agree.

 >So basically what I'm going to ask is for all the copyright characters to be
 >replaced with (c). :)  I realise this is an onerous task (although one that
 >only took me a few minutes with a for loop in bash and a lot of repetitive
 >keystrokes in vi).

It should be noted that the sequence (c) has no legal force, where the
copyright symbol does.  

Re: [Jython-dev] copyright characters in source files

[<bc...@wo...>]

[Mats Wichmann]

> >So basically what I'm going to ask is for all the copyright characters to be
> >replaced with (c). :)  I realise this is an onerous task (although one that
> >only took me a few minutes with a for loop in bash and a lot of repetitive
> >keystrokes in vi).
>
>It should be noted that the sequence (c) has no legal force, where the
>copyright symbol does.  

Does the string \u00A9 have more legal force? As I see it, that is the
alternativ to using "(c)".

I think I would go with using "(c)". That seemed to be good enough for
CNRI in their license and they cared far more about this topic than I
even will.

regards,
finn

Re: [Jython-dev] copyright characters in source files

[<bc...@wo...>]

[Ben Burton]

>Hi.. a note on a different subject.
>
>I'm using jikes to build jython. 

So am I.

>Some time ago I got an error regarding the 
>use of the copyright character in a quoted string (in sha.java).  Which was 
>fine, I just edited the file and replaced the character with (c) and all was 
>well.
>
>Now, since my last upgrade, jikes gets upset when the file contains 
>non-standard characters.  Even in comments.

I don't get any warnings about this at all. Maybe it is because I'm
using Windows where jikes (quite correctly) assume that the source files
is written using a windows codepage.

>So suddenly I find myself having to manually edit some 114 files to replace 
>copyright characters with (c) in the comment headers, eg.:
>// Copyright (c) Corporation for National Research Initiatives
>
>The error jikes gives me is:
>
>jikes +E +D -g -classpath 
>"../../..:/usr/share/java/libgcj.jar:/usr/share/kaffe/rmi.jar:/usr/share/java/servlet-2.2.jar" 
>ArgListCompiler.java
>Charset conversion error at offset 13: Invalid or incomplete multibyte or 
>wide character
>
>You could say "just don't use jikes", 

I would never say that.

>but jikes is explicitly designed to 
>adhere precisely to language and VM specifications; no more, no less.

Maybe it does, but I'm not entirely sure that the java language dictate
the use of ASCII-only in comments and strings. It is more of a tool
issue and there is few garanties on the tools. Javac have en -encoding
option but jikes doesn't.

>So I 
>would claim we *want* jython to compile with jikes because this should mean 
>it will compile with any sane and compliant java compiler.

I agree completely.

>So basically what I'm going to ask is for all the copyright characters to be 
>replaced with (c). :)  I realise this is an onerous task (although one that 
>only took me a few minutes with a for loop in bash and a lot of repetitive 
>keystrokes in vi).

Could you add a bug report so we don't forget about it.

[When making a release, the bug tracker gives me a list of all bugs that
was fixed in the release for free. That is another very good reason for
why I want all bugs to be entered in the tracker]

regards,
finn

Re: [Jython-dev] copyright characters in source files

[Ben B. <be...@ac...>]

> Could you add a bug report so we don't forget about it.

Done (#457614).

> >You could say "just don't use jikes",
>
> I would never say that.

*grin*..  Not suggesting you would; I've just had similar responses from 
(other projects') mailing list contributers in the past so I figured I'd 
mention it for reference.

Grazie,
	Ben. :)

-- 

Ben Burton
be...@ac...  |  ba...@de...
http://baasil.humbug.org.au/bab/
Public Key: finger ba...@de...

One should never trust a woman who tells one her age. A woman who would
tell one that, would tell one anything.
	- Oscar Wilde