Re: about P1 part of BIDI alogrithm

2011-10-13 Thread Philippe Verdy
2011/10/11 Eli Zaretskii e...@gnu.org: From: Philippe Verdy verd...@wanadoo.fr This means that you need to break lines in two separate steps: first between paragraphs or forced line breaks, then a second after determining the the direction of all characters and then remplacing their possible

Re: about P1 part of BIDI alogrithm

2011-10-13 Thread Eli Zaretskii
From: Philippe Verdy verd...@wanadoo.fr Date: Thu, 13 Oct 2011 15:56:06 +0200 Cc: due...@it.aoyama.ac.jp, libo@gmail.com, unicode@unicode.org This would mean to run the reordering twice, since you don't know where to wrap a line until you lay out all of its grapheme clusters, and

Re: Noticed improvement in the Code chart link http://www.unicode.org/charts/

2011-10-13 Thread Philippe Verdy
2011/9/28 Ken Whistler k...@sybase.com: It might be most productive for people concerned with this issue to be reviewing the charts currently in preparation for Version 6.1.0 of the Unicode Standard, rather than the already published charts from last year. Please see, for example:

Re: Noticed improvement in the Code chart link http://www.unicode.org/charts/

2011-10-13 Thread Shriramana Sharma
On 10/13/2011 09:47 PM, Philippe Verdy wrote: I'd like to have an opinion about why this chart (for example) describes two code points 09E4 and 09E5 asreserved, without assigning any glyph, but still associating them with other punctuation signs in another script. Are these positions permanently

Re: Noticed improvement in the Code chart link http://www.unicode.org/charts/

2011-10-13 Thread Asmus Freytag
On 10/13/2011 10:23 AM, Shriramana Sharma wrote: On 10/13/2011 09:47 PM, Philippe Verdy wrote: I'd like to have an opinion about why this chart (for example) describes two code points 09E4 and 09E5 asreserved, without assigning any glyph, but still associating them with other punctuation signs