RE: [Jython-users] jythonc not working -- solved, but strange

[Humbel O. <Otm...@bi...>]

[ Arno.Schmidmeier / dman ]

> | The problem is simply:
> | You write some lines of code with your favourite editor, on=20
> plattform A, the
> | file gets stored as ascii + some local code enhancements.
> | Then you transfer the files to a different plattform/mashine with a
> | different codeset.
> | In the best case the names of variables, etc. changed quite=20
> dramatically in
> | the rest, just forget the result.

That's exactly my experience.=20
Please also consider file names with special characters - shudder.
Only a small example: How many times has a blank in a windows file name
broken up a *nix shell command of yours ?

And there is another point: readability/maintainability. We have here a
development team of people with various mother languages (in
alphabetical order and hopefully spelled correctly): Dutch, English,
French, German, Italian, Slavish, Swiss German, Turkish, and maybe even
more.
If we would allow localized characters in source code, the chance would
be high that poeple choose variable names in their mother language. The
rest you can imagine.
 =20
> Certainly if two processes try and use different encodings for the
> same file, it won't work.  That's what happened to me with jythonc --
> it was encoded in latin1 (though only a single character in a comment
> was affect) but jython (java) was trying to read it as utf-8.
>=20
> The developer's editors and environment must all be set to the correct
> encoding.  PEP 263 addresses that as far as the interpreter is
> concerned.  It is up to the developers to configure their editor
> appropriately.

Beside the fact that there are systems where you simply cannot configure
your editor, I think it is a matter of lowest common denominator, for
the reasons above.

Best wishes,
Oti.