On 23.05.2013 03:59, Yoshiki Ohshima wrote:
For Pharo, I'd guess so, too.
(I heard that the Japanese support is pretty much dropped in Pharo.)
--
If you mean using leadingChar to indicate WideStrings using non-unicode
encoding, and Bitmapped fonts with multiple sets for non-latin1 ranges
ta
>>
>
> For Pharo, I'd guess so, too.
>
> (I heard that the Japanese support is pretty much dropped in Pharo.)
Probably because none of us has the knowledge to understand how it works and
see the problems.
>
> --
> -- Yoshiki
>
On Wed, May 22, 2013 at 3:57 PM, Nicolas Cellier
wrote:
> MC never wrote a BOM, so we don't have to be compatible with BOM.
>
> If we can simplify the process, let's simplify, because maintaining useless
> compatibility costs, the code is really crooked by now, and this leads to
> mis-understandin
On Wed, May 22, 2013 at 2:16 PM, Nicolas Cellier
wrote:
> First thing would be to simplify #setConverterForCode and
> #selectTextConverterForCode.
> Do we still want to use a MacRomanTextConverter, seriously? I'm not even
> sure I've got that many files with that encoding on my Mac-OSX...
> Do we
MC never wrote a BOM, so we don't have to be compatible with BOM.
If we can simplify the process, let's simplify, because maintaining useless
compatibility costs, the code is really crooked by now, and this leads to
mis-understanding, and soon to broken features and noise. Currently,
snapshot/sour
