On Fri, Oct 5, 2012 at 8:28 PM, Takahiro Kambe wrote:
> In message <34500886.p...@talk.nabble.com>
> on Mon, 1 Oct 2012 08:50:55 -0700 (PDT),
> Tomas Kuliavas wrote:
Instead of copying syntax from PHP manual, code should ignore idiocy
written
there and use only ENT_
In message <34500886.p...@talk.nabble.com>
on Mon, 1 Oct 2012 08:50:55 -0700 (PDT),
Tomas Kuliavas wrote:
>>> Instead of copying syntax from PHP manual, code should ignore idiocy
>>> written
>>> there and use only ENT_COMPAT. ENT_HTML401 introduces backwards
>>> compatibility break
taca wrote:
>
> Hi, it is late reply.
>
> In message <34433472.p...@talk.nabble.com>
> on Fri, 14 Sep 2012 09:35:30 -0700 (PDT),
> Tomas Kuliavas wrote:
>> taca wrote:
>>> Someone created wrapper function to htmlspecialchars() to fix this
>>> problem. This patch contains "jaJP" in
Hi, it is late reply.
In message <34433472.p...@talk.nabble.com>
on Fri, 14 Sep 2012 09:35:30 -0700 (PDT),
Tomas Kuliavas wrote:
> taca wrote:
>> Someone created wrapper function to htmlspecialchars() to fix this
>> problem. This patch contains "jaJP" in its filename but it isn't
taca wrote:
>
> Hi,
>
> Someone created wrapper function to htmlspecialchars() to fix this
> problem. This patch contains "jaJP" in its filename but it isn't
> Japanese specific fix at all.
>
> http://doga.jp/~taka2/archive/squirrelmail-webmail-1.4.22-PHP54jaJP_20120705taka2.diff
>
Instead
Hi,
Someone created wrapper function to htmlspecialchars() to fix this
problem. This patch contains "jaJP" in its filename but it isn't
Japanese specific fix at all.
http://doga.jp/~taka2/archive/squirrelmail-webmail-1.4.22-PHP54jaJP_20120705taka2.diff
Best regards.
--
Takahiro Kambe
--
Queued Queuedington wrote:
>
>
>
> Tomas Kuliavas wrote:
>>
>>
>> Queued Queuedington wrote:
>>>
>>> Is the "correct" thing to do, perhaps, converting everything to utf8
>>> that's received in a different character set?
>>>
>> Charset conversions are costly. Some converters have special fu
Tomas Kuliavas wrote:
>
>
> Queued Queuedington wrote:
>>
>> Is the "correct" thing to do, perhaps, converting everything to utf8
>> that's received in a different character set?
>>
> Charset conversions are costly. Some converters have special function
> dependencies or very large mapping t
Queued Queuedington wrote:
>
> Is the "correct" thing to do, perhaps, converting everything to utf8
> that's received in a different character set?
>
Charset conversions are costly. Some converters have special function
dependencies or very large mapping tables. In this case application only
ne
Tomas Kuliavas wrote:
>
>
> Queued Queuedington wrote:
>>
>> Message details is able to read/save the message (and of course, I can
>> read the original.)
>>
>> What's the best way to get it to you? (I'm uncomfortable posting the
>> entire message publicly.)
>>
> Problem is caused by PHP 5
Queued Queuedington wrote:
>
> Message details is able to read/save the message (and of course, I can
> read the original.)
>
> What's the best way to get it to you? (I'm uncomfortable posting the
> entire message publicly.)
>
Problem is caused by PHP 5.4 change in htmlspecialchars defaults.
Queued Queuedington wrote:
>
>
> Tomas Kuliavas wrote:
>>
>>
>> Queued Queuedington wrote:
>>> I have a "test case" where the message has only a plain text component.
>>
>> Is it possible to get a copy of that test case. You can save all required
>> message information with message_details
Tomas Kuliavas wrote:
>
> 2012.08.30 23:47 Queued Queuedington rašė:
>> Tomas Kuliavas wrote:
>>> Queued Queuedington wrote:
In a nutshell, when I reply to some messages, instead of getting quoted
text in the message body, I get nothing at all.
There are no errors, ther
2012.08.30 23:47 Queued Queuedington rašė:
> Tomas Kuliavas wrote:
>> Queued Queuedington wrote:
>>>
>>> In a nutshell, when I reply to some messages, instead of getting quoted
>>> text in the message body, I get nothing at all.
>>>
>>> There are no errors, there are no indications in the logs that
Tomas Kuliavas wrote:
>
>
> Queued Queuedington wrote:
>>
>>
>>
>> Tomas Kuliavas wrote:
>>>
>>>
>>> Queued Queuedington wrote:
Tomas Kuliavas wrote:
>
>
> Queued Queuedington wrote:
>>
>> In a nutshell, when I reply to some messages, instead of get
Queued Queuedington wrote:
>
>
>
> Tomas Kuliavas wrote:
>>
>>
>> Queued Queuedington wrote:
>>>
>>>
>>> Tomas Kuliavas wrote:
Queued Queuedington wrote:
>
> In a nutshell, when I reply to some messages, instead of getting
> quoted text in the message body, I
Tomas Kuliavas wrote:
>
>
> Queued Queuedington wrote:
>>
>>
>> Tomas Kuliavas wrote:
>>>
>>>
>>> Queued Queuedington wrote:
In a nutshell, when I reply to some messages, instead of getting quoted
text in the message body, I get nothing at all.
There are no error
Queued Queuedington wrote:
>
>
> Tomas Kuliavas wrote:
>>
>>
>> Queued Queuedington wrote:
>>>
>>> In a nutshell, when I reply to some messages, instead of getting quoted
>>> text in the message body, I get nothing at all.
>>>
>>> There are no errors, there are no indications in the logs th
Tomas Kuliavas wrote:
>
>
> Queued Queuedington wrote:
>>
>> In a nutshell, when I reply to some messages, instead of getting quoted
>> text in the message body, I get nothing at all.
>>
>> There are no errors, there are no indications in the logs that anything
>> is amiss; the body is simply
Queued Queuedington wrote:
>
> In a nutshell, when I reply to some messages, instead of getting quoted
> text in the message body, I get nothing at all.
>
> There are no errors, there are no indications in the logs that anything is
> amiss; the body is simply blank.
>
> One clue is that the fe
In a nutshell, when I reply to some messages, instead of getting quoted text
in the message body, I get nothing at all.
There are no errors, there are no indications in the logs that anything is
amiss; the body is simply blank.
One clue is that the few affected messages appear to be larger, but
21 matches
Mail list logo
