Re: Re: issue with Devanagari rendering

[Parth Kanungo <parth k samsung com>]

Title: Samsung Enterprise Portal mySingle

Hi Steve,

 

Thanks for the reply.

By "rendering", I meant the FT_Bitmap that is created after using pango_ft2_render_layout() API.

I had flushed the bitmap into an image file for viewing the output.

 

Yes, I am using Unicode character encoding to render the text.  And, you are again correct that this is related to the "input method".

So, a user can type halant, 0x094D, which is invalid without a preceding consonant, but shall nevertheless be rendered.

 

The output I expect with the string

{0x094D, 0x0930}

is a halant below a dotted circle and a ra, र

 

On further investigation, I found that even this string

{0x094D, 0x0930,0x094D, 0x0930,0x094D, 0x0930}

shows wrong output.

 

Can you suggest what could possibly be wrong here?

I feel that some change is required in hb-ot-shape-complex-indic.cc.

 

Thanks and regards,

Parth Kanungo

 

 

 

 

 

------- Original Message -------

Sender : Steve White<stevan white gmail com>

Date : Jan 08, 2014 20:14 (GMT+05:30)

Title : Re: issue with Devanagari rendering

 

Hi, Parth,

There is some confusion here, so that it isn't clear even what you're asking.

Usually in these contexts, the term "rendering" refers to the graphical output of a complex process.

You have provided a list of numbers ending in a null character. This could be interpreted many ways.

The order in which characters from a given character encoding are arranged, is again called the "encoding".

It appears that you are using the Unicode character encoding. The null has nothing to do with the encoding--it's not a valid character in Unicode.

In the Unicode standard, valid orders for Devanagari characters are specified.

You may want to look at
      The Unicode Book, Chapter 9.

All modern systems use this encoding to interpret Devanagari text.

Furthermore, a separate issue is the "input method", which is the way in which a user types or inputs the text.

So... it isn't clear what you intend to happen with this string.

As you see, the halant u+094D has very special behavior in the Unicode encoding.

Just what did you expect to see? 
How were you viewing this string?

Cheers!

On Wed, Jan 8, 2014 at 2:24 PM, Parth Kanungo <parth k samsung com> wrote:

Hello,

 

I was trying to render the string

{0x094D, 0x0930, 0x0000}

The rendered output is incorrect.

 

It might be grammatically inaccurate to place 0x094D (halant) as the first character.

However, my application requires such an independent rendering.

 

Can you tell me how I can go about rendering the given Unicode?

 

Thanks and regards,

Parth Kanungo

 

 

 

_______________________________________________
gtk-i18n-list mailing list
gtk-i18n-list gnome org
https://mail.gnome.org/mailman/listinfo/gtk-i18n-list