On 10 Apr 2014, at 07:03, itli...@schrievkrom.de wrote:
> Am 10.04.2014 03:09, schrieb Paul DeBruicker:
>> +1 to Sven's comment and Marten - you should post this on the GemStone list
>> as one of their guys will be able to help you with the encoding issues.
>
> Its ok for me. Due to Sven's softw
Am 10.04.2014 03:09, schrieb Paul DeBruicker:
> +1 to Sven's comment and Marten - you should post this on the GemStone list
> as one of their guys will be able to help you with the encoding issues.
Its ok for me. Due to Sven's software I actually start using Gemstone -
just to give the honor back
+1 to Sven's comment and Marten - you should post this on the GemStone list
as one of their guys will be able to help you with the encoding issues.
Paul
Sven Van Caekenberghe-2 wrote
> On 09 Apr 2014, at 20:54,
> itlists@
> wrote:
>
>> And now the additional information: I'm working under
On 09 Apr 2014, at 20:54, itli...@schrievkrom.de wrote:
> And now the additional information: I'm working under Gemstone and I
> noticed quite some differences between Pharo and its Gemstone port
> of Zinc in this area ... I have to take a closer look here.
>
> Marten
I already expected that mu
And now the additional information: I'm working under Gemstone and I
noticed quite some differences between Pharo and its Gemstone port
of Zinc in this area ... I have to take a closer look here.
Marten
--
Marten Feldtmann
On 09 Apr 2014, at 19:35, itli...@schrievkrom.de wrote:
> Ok, forget the JSON stuff - it has nothing to do with the "problem".
>
> Other way round:
>
> My whole database and internal processing is done in UTF8. This is the
> most important point here to mention.
Why ? This means you forgo almo
Ok, forget the JSON stuff - it has nothing to do with the "problem".
Other way round:
My whole database and internal processing is done in UTF8. This is the
most important point here to mention.
Now the request comes into Zinc as mentioned below (the content of the
request is a JSON string only
Marten,
On 09 Apr 2014, at 18:25, itli...@schrievkrom.de wrote:
> Ok, if the browser sends POST/PUT request with a JSON structure it also
> sends charset = utf8 (in my case). That's ok, because for JSON this is
> more or less the default charset.
>
> Zinc now seems to notice, that UTF8 charset i
Ok, if the browser sends POST/PUT request with a JSON structure it also
sends charset = utf8 (in my case). That's ok, because for JSON this is
more or less the default charset.
Zinc now seems to notice, that UTF8 charset is needed and creates a
ZnStringEntity with an UTF8Encoder.
Now when my appl
On 09 Apr 2014, at 17:29, itli...@schrievkrom.de wrote:
> The browser sends UTF8 data and in my application code I get instances
> of ZnStringEntity and the contained string is converted to (?) ISO8859-1
> (?) or CP-1252 (?). This seems to be due to the fact, that the entity
> instance always has
Am 09.04.2014 um 17:29 schrieb itli...@schrievkrom.de:
> Am 09.04.2014 15:29, schrieb Sven Van Caekenberghe:
>> Hi Marten,
>>
>> I will need (much) more detail, what are you trying to do that is not
>> working according to you ?
>>
>> As far as I know Zinc HTTP Components does the right thing
Am 09.04.2014 15:29, schrieb Sven Van Caekenberghe:
> Hi Marten,
>
> I will need (much) more detail, what are you trying to do that is not working
> according to you ?
>
> As far as I know Zinc HTTP Components does the right thing and can be used
> (configured) to do almost anything you want. I
Hi Marten,
I will need (much) more detail, what are you trying to do that is not working
according to you ?
As far as I know Zinc HTTP Components does the right thing and can be used
(configured) to do almost anything you want. It mostly depends on your mime
types and their charset options.
S
Hey,
it seems to me, that Zinc - out of the box - seems to convert from/to
UTF8. How can I tell Zinc to do NO conversion and that ZnStringEntity
should leave their strings as they are .. I am fighting here with German
Umlauts
Marten
--
Marten Feldtmann
14 matches
Mail list logo
