Yep, I did change it in following commit, unfortunately I omitted to tell exactly which was the problem...
Name: Multilingual-nice.116 Author: nice Time: 27 March 2010, 11:22:00.573 pm UUID: 6339699b-51ec-fb41-a1e0- c8246b621919 Ancestors: Multilingual-ul.115
Don't let Unicode use #scanMultiCharactersCombiningFrom:to:in:rightX:stopConditions:kern: until problems are fixed. Anyway, combining diacritical was experimental and not really operational.
2013/9/9 Yoshiki Ohshima Yoshiki.Ohshima@acm.org
At Fri, 6 Sep 2013 16:51:56 -0700, tim Rowledge wrote:
On 06-09-2013, at 3:26 PM, Yoshiki Ohshima Yoshiki.Ohshima@acm.org
wrote:
At Fri, 6 Sep 2013 23:02:57 +0200, Nicolas Cellier wrote:
Hi Yoshiki, I also note that there is a presentation and presentationLine in MultiCharacterScanner, could you tell a word about theses inst. vars.?
That (IIRC) was also something to do with the mapping from the logical sequence of code points (that is what a Unicode string is) to the list of "characters" that can be used to fetch the glyphs. IOW, "presentation" is something created by looking at combinations in the logical sequence.
Again, we did not go too far; I think we supported a simple accented characters but not much more.
So far as I could tell from looking at senders and implementors, there wasn't really any use made of 'presentation' and not much of 'presentationLine'; certainly little enough that my *guess* would be they could go away without changing anything.
In the Etoys image, #addCharToPresentation: is called from #scanMultiCharactersCombiningFrom:...., and that is dispatched from Unicode class>>scanSelector. But I guess the mechanism was removed from the trunk at some point in the past.
-- Yoshiki