Re: [argouml-dev] Unmappable Characters in ArgoUML Source Files

Tom Morris <[email protected]> Fri, 12 Aug 2011 16:04:00 -0400
Newsgroups gmane.comp.db.axion.devel
Message-ID <CAE9vqEG3HBgFcr7Cwp9BHJh+zA7pcDEG3vGy6Q-1GmeJJxg51Q@mail.gmail.com>
On Fri, Aug 12, 2011 at 3:18 PM, Mark Fortner <[email protected]> wrote:
> I tried a little experiment on OS's and found the following default
> file encodings on each:
>
> Windows: Cp1252

Yes, I realized after I sent my note that it's much more likely that
most source modules were created as Windows-1252, but it's identical
to ISO 8859-1 except for the C1 controls.
http://en.wikipedia.org/wiki/Windows-1252

> MacOS X: MacRoman

Any time you see something implying a Mac was involved with ArgoUML,
you should double check your results because historically almost all
developers have used Windows.  I presume your previous experiments
where the source files appeared as MacRoman were conducted on a Mac
where this is the default character set.

> I've always heard that UTF-8 is a superset of 8859-1 (also known as Latin-1)

Not true.  It's a superset of 7-bit ASCII, but all non-ASCII
characters require multiple bytes to encode.

> I'm also curious as to what would happen when a user creates a zargo
> file with comments in one encoding and hands it to someone else.  Has
> anyone played around with this?

The native encoding for ArgoUML files is intended to be UTF-8.  If you
find a place where this isn't true, it's a bug.

Tom

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2817328

To unsubscribe from this discussion, e-mail: [[email protected]].
To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]