Ok this is strange the ISO 8857-7 is available with Chrome as an encoding , I tried it and it turns Greek to weird signs. Actually I tried also several others available for Greek by Chrome and none works apart from the default which is UTF-8 ....

Also you can ignore my request as I tried Pharo with True Type fonts with Arial and it can display Greeks just fine. Well done Pharoers , once again Pharo surprises me in a good way :)��

On Fri, Sep 12, 2014 at 5:16 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:

On 12 Sep 2014, at 16:05, kilon alios <kilon.alios@gmail.com> wrote:

> I am not in any urgent need as I rarely use (like almost never) my native language in reading or writing�� when it comes to anything related to computers, apart from facebook friends. But I would like to see it added to pharo , its ���������������� or as you know it "Greek".

So that would be ISO 8857-9 (http://en.wikipedia.org/wiki/ISO/IEC_8859-7 - http://unicode.org/Public/MAPPINGS/ISO8859/8859-7.TXT) then, right ?

Is this nice to have or really necessary (as in used by everybody using the Greek language) ?

> I assume the most popular encondings to have would be Chinese and Hindu ?

I think this something that (native) speakers should help with ;-)

Remember we have full Unicode Character/String capable classes, as well as good UTF-8. Those cover all languages, in theory.

The question comes down to which older encodings are still really used/necessary today.

> On Fri, Sep 12, 2014 at 4:10 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
> Hi,
>
> ZnCharacterEncoder and its subclasses in the package Zinc-Character-Encoding-Core (a standard part of Pharo) have the following features:
>
> - proper Unicode Character/String to/from byte(s) encoding/decoding
> - calculation of encoding size per Character/String
> - proper handling of holes in tables with exceptions (strict/lenient)
> - properly backing up one character on a binary stream
> - simple, efficient, documented
> - convenience API
> - optimisations for some encodings
>
> Together, they support the following encodings:
>
> - utf-8
> - utf-16 (big/little endian, bom detection)
> - null
> - iso-8859-1 (latin-1)
> - iso-8859-2 (latin-2)
> - mac-roman
> - cp1250
> - cp1252
> - cp1253
> - koi8r
> - iso-8859-7
> - iso-8859-15
>
> The question is, what other encodings do you want/need ?
>
> There is already a request to add CP1251.
>
> New byte encoders are easy to add, based on the official Unicode mappings that can be found here: http://unicode.org/Public/MAPPINGS (these are automagically parsed).
>
> Please help us make Pharo more international friendly.
>
> Sven
>
>
>
>