On Sat, 2010-08-07 at 16:04 +0800, Brian Wang wrote:
> Hello Tom,
>
> I can confirm this commit breaks evas text handling for Chinese characters.
> Please find the attached file for reproducing the problem.
>
> I reverted evas to r50594 and elm_entry_cursor_content_get() works properly.
> Then I
On Mon, 2010-08-09 at 09:19 +0800, Brian Wang wrote:
> OK. Is Edje handling strings in UTF-8 or Eina_Unicode/Unicode? It
> seems to be using utf8 seems the use of Eina_Unicode does not exit in
> Edje code. However, it passes the cursor position (CHARACTER index)
> to evas_string_char_next_get().
On Sun, Aug 8, 2010 at 7:33 PM, Tom Hacohen
wrote:
> On Sun, 2010-08-08 at 18:00 +0800, Brian Wang wrote:
>> Please use the test source code I previously attached.
>> ** Within the elm_entry object (three chinese characters in the front,
>> followed by some english letters), click with your mouse
On Sun, 2010-08-08 at 18:00 +0800, Brian Wang wrote:
> Please use the test source code I previously attached.
> ** Within the elm_entry object (three chinese characters in the front,
> followed by some english letters), click with your mouse on any of the
> chinese characters at the start of the st
On Sun, Aug 8, 2010 at 2:37 PM, Tom Hacohen
wrote:
> On Sun, 2010-08-08 at 09:33 +0800, Brian Wang wrote:
>> Hello Tom,
>>
>> Thanks for looking into this problem.
>>
>> Is r50887 fresh enough? r50887 is what I first tried and failed.
>> I reverted evas to r50594 and r50595 (while all other EFL l
On Sat, Aug 7, 2010 at 9:32 PM, Tom Hacohen wrote:
> On Sat, Aug 7, 2010 at 11:04 AM, Brian Wang
> wrote:
>>
>> I can confirm this commit breaks evas text handling for Chinese
>> characters.
>> Please find the attached file for reproducing the problem.
>>
>> I reverted evas to r50594 and elm_entr
On Sat, Aug 7, 2010 at 11:04 AM, Brian Wang wrote:
>
> I can confirm this commit breaks evas text handling for Chinese characters.
> Please find the attached file for reproducing the problem.
>
> I reverted evas to r50594 and elm_entry_cursor_content_get() works
> properly.
> Then I tried r50595 e
On Sat, Aug 7, 2010 at 11:04 AM, Brian Wang wrote:
> Hello Tom,
>
> I can confirm this commit breaks evas text handling for Chinese characters.
> Please find the attached file for reproducing the problem.
>
> I reverted evas to r50594 and elm_entry_cursor_content_get() works
> properly.
> Then I t
On Wed, Jul 28, 2010 at 7:59 PM, Tom Hacohen
wrote:
> Hi all,
>
> Although the commit (and log) gives enough information by itself, I
> decided to write this post to further clarify the subject.
>
> This commit changed the font engine, textblock object and text object to
> use Eina_Unicode instead
Hi all,
Although the commit (and log) gives enough information by itself, I
decided to write this post to further clarify the subject.
This commit changed the font engine, textblock object and text object to
use Eina_Unicode instead of utf8 internally. This commit does not affect
API in any way (
10 matches
Mail list logo
