Hello Sergei,
Tuesday, August 26, 2008, 4:16:00 PM, you wrote:
SG> Graeme Geldenhuys wrote:
>>
>> I couldn't find a single program or editor that could display that
>> file correctly. Pretty amazing that one file can defeat all programs.
>> :-)
>>
>> Programs I tried:
>> Kate (kde editor)
>>
On 8/26/08, Sergei Gorelkin <[EMAIL PROTECTED]> wrote:
> >
> I viewed that file with Opera 9.21 and it looked fine for me (all
> out-of-range chars replaced by a triangle symbol), although the question how
> it *should* look remains open.
You are right. :-) Just tried Opera 9.5 (after setting my
Hello Graeme,
Tuesday, August 26, 2008, 3:48:39 PM, you wrote:
GG> That doesn't say much... :-)
It's the usual status :) most ones are focused in speed instead given
a bit of security, special against overlong sequences which can bypass
security barriers... check the attached file and decode it
Graeme Geldenhuys wrote:
I couldn't find a single program or editor that could display that
file correctly. Pretty amazing that one file can defeat all programs.
:-)
Programs I tried:
Kate (kde editor)
gEdit (Gnome editor)
Firefox 3 (did the best out of the lot)
vi (disastrous)
OpenO
On 8/26/08, JoshyFun <[EMAIL PROTECTED]> wrote:
>
> http://bugs.freepascal.org/view.php?id=11791
>
> The LCL implementation of UTF8ToUTF16 (default one) does not pass the
> UTF8 stress test.
That doesn't say much... :-)
I couldn't find a single program or editor that could display that
file co
Hello Felipe,
Tuesday, August 26, 2008, 12:28:45 PM, you wrote:
FMdC> I read the code for UTF8Encode and UTF8Decode routines and they seam
FMdC> to suppose that the widestring encoding is UCS-2! Instead of UTF-16
FMdC> Is this the expected behavior or is it only partially implemented?
FMdC> Someo
Op Tue, 26 Aug 2008, schreef Felipe Monteiro de Carvalho:
Hello,
I read the code for UTF8Encode and UTF8Decode routines and they seam
to suppose that the widestring encoding is UCS-2! Instead of UTF-16
Is this the expected behavior or is it only partially implemented?
It is a broken implem
Hello,
I read the code for UTF8Encode and UTF8Decode routines and they seam
to suppose that the widestring encoding is UCS-2! Instead of UTF-16
Is this the expected behavior or is it only partially implemented?
Someone added UTF8 <-> UTF16 conversion routines in the LCL, so they
could be used to
