Re: Add scripts to XForms input-mode script list in Appendix E (PR#106)

Hi Martin,

Could you let us know if you have any update on when you might be able to 
work on this appendix?

Please note that the working group did observe one error in our 
specification.  We had intended for this appendix to be informative, but 
it was not marked so.  The latest editor's draft now has the correct 
marking. With the understanding that it is informative content, would you 
have any objection to our proceeding to CR in advance of having the 
updated appendix?  This would produce a bit more time for you to update 
the appendix...

Please let us know because this is the only outstanding LC issue, and we 
are waiting on its resolution to request the CR transition.

Thank you,
John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer





Martin Duerst <duerst@it.aoyama.ac.jp> 
10/31/2007 08:36 PM

To
"Steven Pemberton" <steven.pemberton@cwi.nl>
cc
John Boyer/CanWest/IBM@IBMCA
Subject
Re: Add scripts to XForms input-mode script list in Appendix E (PR#106)






Hello Steven,

I have a few other urgent things going on here, and I didn't
know (or oversaw?) that you wanted something back for a meeting
next week. I'll see what I can do.

Regards,    Martin.

At 01:07 07/11/01, Steven Pemberton wrote:
>Hi Martin,
>
>I wonder if you have managed to make progress on this. We are in a time 
>crunch at the moment, with a FtF due next Monday. Any chance of having 
>this ready by this Friday?
>
>Thanks!
>
>Steven
>
>On Thu, 25 Oct 2007 11:30:40 +0200, John Boyer <boyerj@ca.ibm.com> wrote:
>
>> Hi Martin,
>>
>> Thank you very much for agreeing to help us with this issue.  Your
>> expertise is really vital here.
>>
>> The attached file is the spec XML for the appendix containing the input
>> modes material.  This means that the usual attributes (diff="add",
>> diff="chg and diff="del") are used to mark the changes.
>>
>>
>>
>> Best regards,
>> John M. Boyer, Ph.D.
>> STSM: Lotus Forms Architect and Researcher
>> Chair, W3C Forms Working Group
>> Workplace, Portal and Collaboration Software
>> IBM Victoria Software Lab
>> E-Mail: boyerj@ca.ibm.com
>>
>> Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
>>
>>
>>
>>
>>
>> Martin Duerst <duerst@it.aoyama.ac.jp>
>> Sent by: www-forms-editor-request@w3.org
>> 10/24/2007 11:43 PM
>>
>> To
>> "Steven Pemberton" <steven.pemberton@cwi.nl>
>> cc
>> public-i18n-core@w3.org, www-forms-editor@w3.org
>> Subject
>> Re: Add scripts to XForms input-mode script list in Appendix E (PR#106)
>>
>>
>>
>>
>>
>>
>>
>> Hello Steven,
>>
>> At 00:45 07/10/25, Steven Pemberton wrote:
>>>
>>> Martin,
>>>
>>> I think then that I understand your answer to be: the list should be 
in
>>> the spec.
>>
>> Yes indeed.
>>
>>> Since you produced the list in the original case, I wonder if you 
would
>> be
>>> so kind to refresh it for us, since there is no one currently in the 
WG
>>> that has the expertise to do that.
>>
>> No problem. What exact form do you prefer? I can send you a HTML
>> table based on the one currently at
>> http://www.w3.org/TR/xforms11/#mode-scripts, with the additions
>> (as listed below). If you are editing from some XML form, I'll
>> try to handle that, too. Also, please tell me what kind of change
>> markup you are using, if any.
>>
>> I have no problem doing the work, but I'd like somebody else
>> (could be XForms WG or I18N Core WG) to crosscheck.
>>
>> Regards,   Martin.
>>
>>> Best wishes,
>>>
>>> Steven
>>>
>>> On Sun, 17 Jun 2007 10:24:04 +0200, Martin Duerst
>> <duerst@it.aoyama.ac.jp>
>>> wrote:
>>>
>>>>
>>>> Hello Steven,
>>>>
>>>> At 04:33 07/06/14, Steven Pemberton wrote:
>>>>> Martin,
>>>>>
>>>>> I wonder if it woudn't be more efficient to have this list by
>> reference
>>>>> rather
>>>>> than by inclusion.
>>>>>
>>>>> Since you are the author of this section, would you be willing to
>>>>> suggest the
>>>>> text to replace the list with references to the normative specs?
>>>>
>>>> This may make sense to some extent, but it's not totally clear that
>>>> all future additions to the Unicode list of scripts can be just added
>>>> to the list of input mode tags in XForms. It is certainly not the 
case
>>>> that the current list of scripts in Unicode is identical with the
>>>> (currently proposed, incl. below) list of tags in XForms.
>>>>
>>>> Also, because there are changes in spelling, I think it's much
>>>> more useful for implementers and users to have a full list.
>>>> What I could immagine is that we add a sentence saying something
>>>> like "it is expected that future versions of this specification
>>>> will include tokens for scripts added to Unicode wherever that
>>>> makes sense".
>>>>
>>>> Regards,    Martin.
>>>>
>>>>> Best wishes,
>>>>>
>>>>> Steven Pemberton
>>>>>
>>>>>> Appendix E of this specification (
http://www.w3.org/TR/xforms11/#mode
>> ),
>>>>>> entitled "Input Modes", should be updated to be in sync with the 
most
>>>>>> recent list of scripts from Unicode/ISO 10646.
>>>>>>
>>>>>> A rough count (using the Unix 'wc' utilty) showed that about 15
>>>>>> scripts are missing from the list of tokens at
>>>>>> http://www.w3.org/TR/xforms11/#mode-values.
>>>>>>
>>>>>> A point-by-point comparison with
>>>>>> http://www.unicode.org/Public/5.0.0/ucd/PropertyValueAliases.txt
>>>>>> (look below the line "# Script (sc)") gave the following list
>>>>>> (more than 15 because E.3.1 contains quite a few special values):
>>>>>> (starting with lowercase and converting spaces to camelcase in
>>>>>> line with the currently available tokens (e.g. 
canaidianAboriginal)).
>>>>>>
>>>>>> balinese
>>>>>> buginese
>>>>>> coptic
>>>>>> cypriot
>>>>>> glagolitic
>>>>>> kharoshthi
>>>>>> limbu
>>>>>> linearB
>>>>>> nko
>>>>>> osmanya
>>>>>> phagsPa
>>>>>> phoenician
>>>>>> shavian
>>>>>> sylotiNagri
>>>>>> taiLe
>>>>>> newTaiLue
>>>>>> tifinagh
>>>>>> ugaritic
>>>>>> oldPersian
>>>>>> cuneiform
>>>>>>
>>>>>> This list of tokens can be included as is (with "Unicode script 
name"
>>>>>> in the Comments column), but should be cross-checked to make sure
>>>>>> I didn't miss anything. The text above the table can then be 
updated
>>>>>> to say "The version of the Unicode Standard that these script name
>>>>>> are taken from is 5.0." instead of "The version of the Unicode
>> Standard
>>>>>> that these script names are taken from is 3.2.".
>>>>>>
>>>>>> Many of the scripts (e.g. Cunieform) are not necessarily what you
>>>>>> would expect as your typical XForms input, but some of the tokens
>>>>>> already available in XForms 1.0 also don't have a high probability
>>>>>> of usage, and it's better to be complete than to leave something 
out
>>>>>> that later may be needed.
>>>>>>
>>>>>> Some people may raise the concern that adding these script tokens
>>>>>> will force the spec to go to Last Call again. While this would be
>>>>>> true for any genuinely new feature being added after Last Call,
>>>>>> it is difficult to see why a new Last Call would be needed just
>>>>>> because the list of scripts is being completed. No XForms
>>>>>> implementation
>>>>>> is forced to support all of these values anyway, but not including
>>>>>> a value that's currently not supported would create a weird
>>>>>> chicken-and-egg problem.
>>>>>>
>>>>>> Regards,      Martin.
>>>>>>
>>>>>>
>>>>>> #-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
>>>>>> #-#-#  http://www.sw.it.aoyama.ac.jp
>> mailto:duerst@it.aoyama.ac.jp
>>>>>>
>>>>>>
>>>>
>>>>
>>>> #-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
>>>> #-#-#  http://www.sw.it.aoyama.ac.jp
>> mailto:duerst@it.aoyama.ac.jp
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> #-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
>> #-#-#  http://www.sw.it.aoyama.ac.jp       
mailto:duerst@it.aoyama.ac.jp
>>
>>
>>
>
>


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp