[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [orbit-dev] ISO-8829-1 encoding for Orbit ???
|
Thanks Dave.
Are there any bundles you're maintaining that already have
the
encoding set on project level (in a .settings directory, I
assume)
such that I can verify my setting against yours in a
compare viewer?
Thanks,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Yes, definitely a typo, 8859 was
intended.
The reason "we"
recommend 8859 is that it is a single byte, commonly used encoding and from
what I can tell "matches" the encoding in the Eclipse repository server (this
latter might differ from logon, to logon, though .... not sure it matters ...
the single byte part is the important part).
Being single byte pretty much ensures any transfers
(such as from a workspace to the server's repository) do not harm anything. In
a multibyte representation (such as UTF-8) there is some chance of corruption,
even if small. This is mostly related to the fact that "end of lines" are
sometimes changed as source is checked in and out of the repository ...
depending on various settings).
And, remember, this is just recommended to be the default if not
otherwise specified. If you had a particular file that needed something else,
it's perfectly fine to use what ever it needs. The main thing is to have a
default set per project, so no matter who checks it out, the same assumptions
are being made about the default case.
I'll fix the typo.
Hope
that helps,
From:
| "Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx>
|
To:
| "Orbit Developer discussion"
<orbit-dev@xxxxxxxxxxx>
|
Date:
| 03/04/2008 04:17 PM
|
Subject:
| [orbit-dev] ISO-8829-1 encoding for
Orbit ??? |
Hi all,
On the Wiki I just found
this:
http://wiki.eclipse.org/Adding_Bundles_to_Orbit#National_Language_Considerations
"... it is recommend you set the project's default
encoding preference to ISO-8829-1.."
Is this a typo and meant to be ISO-8859-1 (which
would be more familiar to me)?
How do we
treat chracters not available in ISO-8859-1 e.g. foreign names of
contributors in copyright comments, with accents
and other odd characters?
Shouldn't we re-use the encoding used by the original
library provider, if they
need special
characters and chose to adopt a particular encoding?
I think the real point here
is that most sources out there in the wild use
ISO-8859-1 and that's the real reason for adopting it by default.
However,
Java does support Unicode (UTF-8)
and HTML can even specify encoding
in the
source file so I'm a little confused...
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
_______________________________________________
orbit-dev mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev