<br><br><div class="gmail_quote">On Tue, Apr 22, 2008 at 7:35 PM, Patrik Fältström <<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
On 22 apr 2008, at 22.40, Mark Davis wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
But as above, their program just won't let them access labels<br>
that incorporate any changes in the tables, not just exceptional changes<br>
from DISALLOWED to PVALID.<br>
</blockquote>
<br></div>
Just three short things that I think capture the difference between your and mine view.<br>
<br>
Yes, it will capture changes based on assignment of earlier unassigned codepoints as the algorithm is based on an algorithm based on the Unicode Properties, and not a table. </blockquote><div><br>I didn't say that the table algorithm wouldn't catch them. I said that *non-updated applications* wouldn't update them.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">No, it will not capture later additions of unassigned codepoints to the exception table. What is needed is "only" that the Unicode versions are updated, and that happens when the operating system is updated. Much more likely than software / application updated.</blockquote>
<div><br>I do not forsee many applications actually generating the tables from Unicode properties; that's not the way most OSs deal with derived Unicode properties. Instead, they load in pre-built data associated with the release. And if we do this the right way, the exception data would be staged concurrent with each Unicode release. So I don't see this as making any practical difference.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
My statement on interest from application creators to include filters in their applications are coming from, well, application creators. They want to do implement these filters.</blockquote><div><br>For us to assess the importance of this, versus the many other competing requirements, we have to actually hear from those application creators; there has to be a dialog where we hear what their problems are, and why they think that this is the way to solve those problems.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Last issue, noone want software to "never be updated". But applications are much more seldom updated than what anyone wants. Unfortunately.</blockquote>
<div><br>Agreed. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><font color="#888888">
<br>
Patrik<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mark