<p dir="ltr">I'm wondering how much some of the detail is language based and may be handled using language systems?</p>
<div class="gmail_quote">On 21/05/2013 5:31 PM, "Theppitak Karoonboonyanan" <<a href="mailto:thep@linux.thai.net">thep@linux.thai.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, May 21, 2013 at 4:39 AM, Richard Wordingham<br>
<<a href="mailto:richard.wordingham@ntlworld.com">richard.wordingham@ntlworld.com</a>> wrote:<br>
> On Mon, 20 May 2013 15:08:19 +0700<br>
> Theppitak Karoonboonyanan <<a href="mailto:thep@linux.thai.net">thep@linux.thai.net</a>> wrote:<br>
><br>
> For the recoding solution, you wrote:<br>
><br>
> "A possible workaround is to exclude LA from the above rule. This is<br>
> quite safe because NGA and LA are never conjoined in Pali grammar."<br>
><br>
> While Pali doesn't have -ṅl- or -ṃl-, we do have Sanskrit influence<br>
> to contend with. Thus, although Pali for 'masculine' is _pullinga_, the<br>
> MFL lists <BA, U, MAI KANG, LA, I, NGA, SAKOT, LOW KA> ปุงลิงคะ with<br>
> this meaning. Given the dictionary's spelling habits, I half expected to<br>
> see MAI KANG LAI sitting on the BA. I don't think we can rely on MAI<br>
> KANG LAI never sliding forward onto a LA.<br>
<br>
OK. The example implies that งฺล conjunct is still possible even in Pali.<br>
So, I've removed the workaround from the text.<br>
<br>
The Unicode amendment may not help, either, as the use of MEDIAL LA<br>
and side-subjoined LA is somewhat arbitrary.<br>
<br>
> If we're going to go for a coding solution, I'd rather go for a new<br>
> character. However, out of ignorance, I have to ask - are non-shifted<br>
> MAI KANG LAI and CONSONANT SIGN NGA different? Lao Tham suggests they<br>
> might be the same thing.<br>
<br>
Yes, they are the same for Lao Tham. When used to write Pali, it's MAI<br>
KANG LAI. When used to write Lao/Thai, it's FINAL NGA. But I heard<br>
that the two are of different shapes in Khuen. So, they can't be used to<br>
encode the same entity, I suppose.<br>
<br>
> Another conceivable solution you mention is, "Fonts for Lao Tham and<br>
> the shifting school of Lanna may provide GSUB rule to reorder Mai Kang<br>
> Lai themselves."<br>
><br>
> This goes against what I first learnt about GSUB. I suppose it is<br>
> tied up with how one handles editing of clusters of characters.<br>
> Perhaps I'm just a semi-literate foreigner, but I frequently find<br>
> myself having to edit 'legacy grapheme clusters'. It's helpful when<br>
> the cursor actually shows me where I am within the cluster - but that<br>
> can only be done if the connection between characters and glyphs is<br>
> maintained. Using GSUB to change the order of characters destroys that<br>
> information, which is why reordering is supposed to done by the<br>
> script-specific shaping logic.<br>
<br>
Understood. I've added some text describing the problem.<br>
<br>
> I still haven't equipped myself to experiment with GPOS as a way of<br>
> correcting the minor deficiencies of shaping. I'm about two weeks away<br>
> at my current rate of progress.<br>
<br>
Let's add that to the page when you find some way out.<br>
<br>
> However, I think we are at a point where Behdad can say what he thinks<br>
> of the 'rphf' option.<br>
<br>
Agreed.<br>
<br>
Regards,<br>
--<br>
Theppitak Karoonboonyanan<br>
<a href="http://linux.thai.net/~thep/" target="_blank">http://linux.thai.net/~thep/</a><br>
_______________________________________________<br>
HarfBuzz mailing list<br>
<a href="mailto:HarfBuzz@lists.freedesktop.org">HarfBuzz@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/harfbuzz" target="_blank">http://lists.freedesktop.org/mailman/listinfo/harfbuzz</a><br>
</blockquote></div>