ISO-8859 is dead, long live ISO-8859

The Trade-offs of Unicode

Whilst Unicode has given us the wonderful gift of complete coverage of just about every written language in a single application, it has not come without a price. That price is the greatly increased amount of memory required to store 32 bit characters.

blog My three Eiffelwishes, part 2: Unicode

dlebansais's picture

If English is your primary language, you've probably never used characters from a foreign language in Eiffel source files.

blog Working on UTF-8 Eiffel parser

ted_eiffel's picture

I am so excited that I can really push ISE Eiffel compiler to support full Unicode. 6.6 should be the first version to support it.

The first thing I do is parsing UTF-8 source code.

blog Mixing Unicode and Latin-1 class texts

colin-adams's picture

Since ECMA allows class texts to be written as either sequences of CHARACTER_8 of CHARACTER_32 (which although not properly specified yet, we can assume means Latin-1 or Unicode), there arises the question of to what extent the two can be mixed.

blog UTF-8 Unicode in Eiffel for .NET

peter_gummer's picture

We have an Eiffel for .NET dll which is called by a VB.NET application. We need to internationalize this application. "That should be easy", I thought, "because Eiffel's   is basically just a wrapper for the .NET String." So we fed our Eiffel dll some UTF-8 data, which it dutifully manipulated; but the VB.NET client application received garbage. Instead of displaying beautiful Farsi characters, it spat out wingding-dingbat-like droppings. What was wrong?

Syndicate content