Thread Subject: Re: I Thought ASCII was a character set?
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
Return to this mailing list's archives
From: Taylor Tom E
Date: Tue, Sep 18 2007 6:45 AM
Subject: Re: I Thought ASCII was a character set?
Isn't ASCII a character set? At least it was the last time I looked a
character up, but it's been awhile. You should be able to write in
multiple languages in ASCII, some of the special characters might be
missing.
Thanks
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
= EMAIL ADDRESS REMOVED =
Sent: Monday, September 17, 2007 11:51 PM
To: = EMAIL ADDRESS REMOVED =
Subject: teitac-websoftware Digest, Vol 12, Issue 29
Send teitac-websoftware mailing list submissions to
= EMAIL ADDRESS REMOVED =
To subscribe or unsubscribe via the World Wide Web, visit
http://list.teitac.org/mailman/listinfo/teitac-websoftware
or, via email, send a message with subject or body 'help' to
= EMAIL ADDRESS REMOVED =
You can reach the person managing the list at
= EMAIL ADDRESS REMOVED =
When replying, please edit your Subject line so it is more specific than
"Re: Contents of teitac-websoftware digest..."
Today's Topics:
1. Re: 3d/3e for content format (Peter Korn)
2. Re: 3d/3e for content format (Hoffman, Allen)
3. Re: note for focus cursor (Andi Snow-Weaver)
4. Re: note for focus cursor (Gregg Vanderheiden)
----------------------------------------------------------------------
Message: 1
Date: Mon, 17 Sep 2007 12:30:40 -0700
From: Peter Korn < = EMAIL ADDRESS REMOVED = >
Subject: Re: [teitac-websoftware] 3d/3e for content format
To: TEITAC Web/Software Subcommittee
< = EMAIL ADDRESS REMOVED = >
Message-ID: < = EMAIL ADDRESS REMOVED = >
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Hi Allen,
I understand your logic, and I agree with your conclusions. But I
remain concerned that we are essentially saying that governments shall
not use ASCII for documents. We have not yet settled the question of
where these provisions should be applied - just to published web
documents? to formal memos in e-mail from management? to all documents
exchanged within the government on any topic? - but when we do, I think
we will find a lot of opposition to saying that ASCII cannot be used for
that purpose.
Regards,
Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
> Peter:
>
> My take is, ASCII would not allow language identification, so
> application of that standard for a product sing that format while
> feasible will yield a noncompliant result.
>
> So lets say I'm comparing three products for selection:
>
> 1. product delivering information in ASCII in multiple languages.
> 2. Product delivering information in multiple languages in HTML.
> 3. Product delivering information in one language in ASCII.
>
> Product 1 would fail 3d and 3e.
> Product 2 would be able to pass both if coded by the vendor correctly.
> Product 3 would fail both.
>
>
> We might just write that the natural language of each portion of
> content must be programmatically determinable from mark up. wouldn't
> that encapsulate this better?
>
>
>
> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
> Korn
> Sent: Friday, September 14, 2007 2:46 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] 3d/3e for content format
>
> Hi Allen,
>
> I think your test is too simplistic. Do we truly intend to say that
> an ASCII document (or e-mail or...) fails? Or should we find language
> to make it clear we are talking about a rich text document format.
>
> Certainly it should be understood that switching languages in ASCII,
> there is no way for an assistive technology to know what is going on.
>
> Maybe this is more of a communication issue than a procurement
issue...
>
>
> Regards,
>
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.
>
>
>> Andrew:
>>
>> It would be work to verify to a very high degree, but I don't think
>> this is an overwhelming requirement to test to a reasonable degree
>> via
>>
>
>
>> automated means.
>>
>> General test logic:
>> if content has no language identifier, it fails.
>> if it has (1) language identifier, it passes unless:
>> by character, or word analysis, it can be determined that
>>
> content
>
>> contains more than the initial language identifier.
>>
>> nailing down a specific list of failures is more difficult, but spell
>> check can probably address such a requirement by including language
>> identification as part of that function. I'd expect language
>> identification would have to be part of any multi-lingual authoring
>> tool anyway at some point.
>>
>>
>>
>>
>>
>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>> Andrew Kirkpatrick
>> Sent: Thursday, September 13, 2007 9:15 AM
>> To: TEITAC Web/Software Subcommittee
>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>
>> Just for the record, my objection is more to the "changes in
language"
>> section. Seems like a lot of extra work to verify this...
>> AWK
>>
>>
>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Hoffman, Allen
>>> Sent: Wednesday, September 12, 2007 2:34 PM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> is there synthetic speech for Creole? Just curious!
>>>
>>>
>>>
>>>
>>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Smith, Jamie
>>> Sent: Wednesday, September 12, 2007 2:29 PM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> I definitely feel we must have this as a provision. In Florida,
>>> public information is often in Spanish and Creole as well as
English.
>>>
>>>
>>
>>
>>> Some documents are the "Florida Comprehensive Assessment Test" test
>>> materials and while the document is in Spanish or Creole the test
>>> examples are always in English. The lack of coding for the language
>>> did cause speech to select a language and attempt to read the Creole
>>> with that language.
>>> >From the point of the first change to Creole on (even when text was
>>>
>>>
>>>> back
>>>>
>>>>
>>> to English), speech messed up. Adding the language code in the
>>> doctype and then to the specific sections which had a different
>>> language fixed the problem. The reason the language code wasn't
>>> done,
>>>
>>>
>>
>>
>>> simply because it wasn't required.
>>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Andrew Kirkpatrick
>>> Sent: Thursday, September 06, 2007 9:32 AM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> In the spirit of trying to reduce the extra weight of the new
>>> standards, I'll raise my question again -- why is language support
>>> in
>>>
>
>
>>> 508? We do have other WCAG standards that we have not included, and
>>> this seems like it is not needed in the U.S. standard.
>>>
>>> What is our rationale for requiring the language support in content
>>> formats and web and software provisions?
>>>
>>> AWK
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: = EMAIL ADDRESS REMOVED =
>>>> [mailto: = EMAIL ADDRESS REMOVED = ] On
>>>>
>>>>
>>> Behalf Of Peter
>>>
>>>
>>>
>>>> Korn
>>>> Sent: Tuesday, September 04, 2007 3:56 PM
>>>> To: TEITAC Web/Software Subcommittee
>>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>>
>>>> Hi Allen,
>>>>
>>>> We need to be careful with this one. Simple text editors (think
>>>> Notepad) won't be able to do this.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Peter Korn
>>>> Accessibility Architect,
>>>> Sun Microsystems, Inc.
>>>>
>>>>
>>>>
>>>>> Action item from Tuesday, 09/04.
>>>>>
>>>>> Content formats which support multiple languages MUST provide a
>>>>> programmatically determinable mechanism to identify the primary
>>>>> language, and the language of any sections which are in
>>>>>
>>>>>
>>>> another language
>>>>
>>>>
>>>>> from the primary language.
>>>>>
>>>>>
>>>>>
>>>>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>>>>
From: Hoffman, Allen
Date: Tue, Sep 18 2007 7:05 AM
Subject: Re: I Thought ASCII was a character set?
You are correct, there is a difference between character sets and format
specifications.
Unicode would be a character set that would include ability to do
multilingual characters and would also be a format if used in certain
ways.
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Taylor
Tom E
Sent: Tuesday, September 18, 2007 8:41 AM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-websoftware] I Thought ASCII was a character set?
Isn't ASCII a character set? At least it was the last time I looked a
character up, but it's been awhile. You should be able to write in
multiple languages in ASCII, some of the special characters might be
missing.
Thanks
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
= EMAIL ADDRESS REMOVED =
Sent: Monday, September 17, 2007 11:51 PM
To: = EMAIL ADDRESS REMOVED =
Subject: teitac-websoftware Digest, Vol 12, Issue 29
Send teitac-websoftware mailing list submissions to
= EMAIL ADDRESS REMOVED =
To subscribe or unsubscribe via the World Wide Web, visit
http://list.teitac.org/mailman/listinfo/teitac-websoftware
or, via email, send a message with subject or body 'help' to
= EMAIL ADDRESS REMOVED =
You can reach the person managing the list at
= EMAIL ADDRESS REMOVED =
When replying, please edit your Subject line so it is more specific than
"Re: Contents of teitac-websoftware digest..."
Today's Topics:
1. Re: 3d/3e for content format (Peter Korn)
2. Re: 3d/3e for content format (Hoffman, Allen)
3. Re: note for focus cursor (Andi Snow-Weaver)
4. Re: note for focus cursor (Gregg Vanderheiden)
----------------------------------------------------------------------
Message: 1
Date: Mon, 17 Sep 2007 12:30:40 -0700
From: Peter Korn < = EMAIL ADDRESS REMOVED = >
Subject: Re: [teitac-websoftware] 3d/3e for content format
To: TEITAC Web/Software Subcommittee
< = EMAIL ADDRESS REMOVED = >
Message-ID: < = EMAIL ADDRESS REMOVED = >
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Hi Allen,
I understand your logic, and I agree with your conclusions. But I
remain concerned that we are essentially saying that governments shall
not use ASCII for documents. We have not yet settled the question of
where these provisions should be applied - just to published web
documents? to formal memos in e-mail from management? to all documents
exchanged within the government on any topic? - but when we do, I think
we will find a lot of opposition to saying that ASCII cannot be used for
that purpose.
Regards,
Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
> Peter:
>
> My take is, ASCII would not allow language identification, so
> application of that standard for a product sing that format while
> feasible will yield a noncompliant result.
>
> So lets say I'm comparing three products for selection:
>
> 1. product delivering information in ASCII in multiple languages.
> 2. Product delivering information in multiple languages in HTML.
> 3. Product delivering information in one language in ASCII.
>
> Product 1 would fail 3d and 3e.
> Product 2 would be able to pass both if coded by the vendor correctly.
> Product 3 would fail both.
>
>
> We might just write that the natural language of each portion of
> content must be programmatically determinable from mark up. wouldn't
> that encapsulate this better?
>
>
>
> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
> Korn
> Sent: Friday, September 14, 2007 2:46 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] 3d/3e for content format
>
> Hi Allen,
>
> I think your test is too simplistic. Do we truly intend to say that
> an ASCII document (or e-mail or...) fails? Or should we find language
> to make it clear we are talking about a rich text document format.
>
> Certainly it should be understood that switching languages in ASCII,
> there is no way for an assistive technology to know what is going on.
>
> Maybe this is more of a communication issue than a procurement
issue...
>
>
> Regards,
>
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.
>
>
>> Andrew:
>>
>> It would be work to verify to a very high degree, but I don't think
>> this is an overwhelming requirement to test to a reasonable degree
>> via
>>
>
>
>> automated means.
>>
>> General test logic:
>> if content has no language identifier, it fails.
>> if it has (1) language identifier, it passes unless:
>> by character, or word analysis, it can be determined that
>>
> content
>
>> contains more than the initial language identifier.
>>
>> nailing down a specific list of failures is more difficult, but spell
>> check can probably address such a requirement by including language
>> identification as part of that function. I'd expect language
>> identification would have to be part of any multi-lingual authoring
>> tool anyway at some point.
>>
>>
>>
>>
>>
>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>> Andrew Kirkpatrick
>> Sent: Thursday, September 13, 2007 9:15 AM
>> To: TEITAC Web/Software Subcommittee
>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>
>> Just for the record, my objection is more to the "changes in
language"
>> section. Seems like a lot of extra work to verify this...
>> AWK
>>
>>
>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Hoffman, Allen
>>> Sent: Wednesday, September 12, 2007 2:34 PM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> is there synthetic speech for Creole? Just curious!
>>>
>>>
>>>
>>>
>>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Smith, Jamie
>>> Sent: Wednesday, September 12, 2007 2:29 PM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> I definitely feel we must have this as a provision. In Florida,
>>> public information is often in Spanish and Creole as well as
English.
>>>
>>>
>>
>>
>>> Some documents are the "Florida Comprehensive Assessment Test" test
>>> materials and while the document is in Spanish or Creole the test
>>> examples are always in English. The lack of coding for the language
>>> did cause speech to select a language and attempt to read the Creole
>>> with that language.
>>> >From the point of the first change to Creole on (even when text was
>>>
>>>
>>>> back
>>>>
>>>>
>>> to English), speech messed up. Adding the language code in the
>>> doctype and then to the specific sections which had a different
>>> language fixed the problem. The reason the language code wasn't
>>> done,
>>>
>>>
>>
>>
>>> simply because it wasn't required.
>>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Andrew Kirkpatrick
>>> Sent: Thursday, September 06, 2007 9:32 AM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> In the spirit of trying to reduce the extra weight of the new
>>> standards, I'll raise my question again -- why is language support
>>> in
>>>
>
>
>>> 508? We do have other WCAG standards that we have not included, and
>>> this seems like it is not needed in the U.S. standard.
>>>
>>> What is our rationale for requiring the language support in content
>>> formats and web and software provisions?
>>>
>>> AWK
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: = EMAIL ADDRESS REMOVED =
>>>> [mailto: = EMAIL ADDRESS REMOVED = ] On
>>>>
>>>>
>>> Behalf Of Peter
>>>
>>>
>>>
>>>> Korn
>>>> Sent: Tuesday, September 04, 2007 3:56 PM
>>>> To: TEITAC Web/Software Subcommittee
>>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>>
>>>> Hi Allen,
>>>>
>>>> We need to be careful with this one. Simple text editors (think
>>>> Notepad) won't be able to do this.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Peter Korn
>>>> Accessibility Architect,
>>>> Sun Microsystems, Inc.
>>>>
>>>>
>>>>
>>>>> Action item from Tuesday, 09/04.
>>>>>
>>>>> Content formats which support multiple languages MUST provide a
>>>>> programmatically determinable mechanism to identify the primary
>>>>> language, and the language of any sections which are in
>>>>>
>>>>>
>>>> another language
>>>>
>>>>
>>>>> from the primary language.
>>>>>
>>>>>
>>>>>
>>>>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>>>>
From: David Poehlman
Date: Tue, Sep 18 2007 7:20 AM
Subject: Re: I Thought ASCII was a character set?
yes, I think what we are talking about and confusing with ascii is
plain text or in some circles known as dos text.
On Sep 18, 2007, at 8:57 AM, Hoffman, Allen wrote:
You are correct, there is a difference between character sets and format
specifications.
Unicode would be a character set that would include ability to do
multilingual characters and would also be a format if used in certain
ways.
Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Taylor
Tom E
Sent: Tuesday, September 18, 2007 8:41 AM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [teitac-websoftware] I Thought ASCII was a character set?
Isn't ASCII a character set? At least it was the last time I looked a
character up, but it's been awhile. You should be able to write in
multiple languages in ASCII, some of the special characters might be
missing.
Thanks
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
= EMAIL ADDRESS REMOVED =
Sent: Monday, September 17, 2007 11:51 PM
To: = EMAIL ADDRESS REMOVED =
Subject: teitac-websoftware Digest, Vol 12, Issue 29
Send teitac-websoftware mailing list submissions to
= EMAIL ADDRESS REMOVED =
To subscribe or unsubscribe via the World Wide Web, visit
http://list.teitac.org/mailman/listinfo/teitac-websoftware
or, via email, send a message with subject or body 'help' to
= EMAIL ADDRESS REMOVED =
You can reach the person managing the list at
= EMAIL ADDRESS REMOVED =
When replying, please edit your Subject line so it is more specific than
"Re: Contents of teitac-websoftware digest..."
Today's Topics:
1. Re: 3d/3e for content format (Peter Korn)
2. Re: 3d/3e for content format (Hoffman, Allen)
3. Re: note for focus cursor (Andi Snow-Weaver)
4. Re: note for focus cursor (Gregg Vanderheiden)
----------------------------------------------------------------------
Message: 1
Date: Mon, 17 Sep 2007 12:30:40 -0700
From: Peter Korn < = EMAIL ADDRESS REMOVED = >
Subject: Re: [teitac-websoftware] 3d/3e for content format
To: TEITAC Web/Software Subcommittee
< = EMAIL ADDRESS REMOVED = >
Message-ID: < = EMAIL ADDRESS REMOVED = >
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Hi Allen,
I understand your logic, and I agree with your conclusions. But I
remain concerned that we are essentially saying that governments shall
not use ASCII for documents. We have not yet settled the question of
where these provisions should be applied - just to published web
documents? to formal memos in e-mail from management? to all documents
exchanged within the government on any topic? - but when we do, I think
we will find a lot of opposition to saying that ASCII cannot be used for
that purpose.
Regards,
Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
> Peter:
>
> My take is, ASCII would not allow language identification, so
> application of that standard for a product sing that format while
> feasible will yield a noncompliant result.
>
> So lets say I'm comparing three products for selection:
>
> 1. product delivering information in ASCII in multiple languages.
> 2. Product delivering information in multiple languages in HTML.
> 3. Product delivering information in one language in ASCII.
>
> Product 1 would fail 3d and 3e.
> Product 2 would be able to pass both if coded by the vendor correctly.
> Product 3 would fail both.
>
>
> We might just write that the natural language of each portion of
> content must be programmatically determinable from mark up. wouldn't
> that encapsulate this better?
>
>
>
> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
> Korn
> Sent: Friday, September 14, 2007 2:46 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] 3d/3e for content format
>
> Hi Allen,
>
> I think your test is too simplistic. Do we truly intend to say that
> an ASCII document (or e-mail or...) fails? Or should we find language
> to make it clear we are talking about a rich text document format.
>
> Certainly it should be understood that switching languages in ASCII,
> there is no way for an assistive technology to know what is going on.
>
> Maybe this is more of a communication issue than a procurement
issue...
>
>
> Regards,
>
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.
>
>
>> Andrew:
>>
>> It would be work to verify to a very high degree, but I don't think
>> this is an overwhelming requirement to test to a reasonable degree
>> via
>>
>
>
>> automated means.
>>
>> General test logic:
>> if content has no language identifier, it fails.
>> if it has (1) language identifier, it passes unless:
>> by character, or word analysis, it can be determined that
>>
> content
>
>> contains more than the initial language identifier.
>>
>> nailing down a specific list of failures is more difficult, but spell
>> check can probably address such a requirement by including language
>> identification as part of that function. I'd expect language
>> identification would have to be part of any multi-lingual authoring
>> tool anyway at some point.
>>
>>
>>
>>
>>
>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>> Andrew Kirkpatrick
>> Sent: Thursday, September 13, 2007 9:15 AM
>> To: TEITAC Web/Software Subcommittee
>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>
>> Just for the record, my objection is more to the "changes in
language"
>> section. Seems like a lot of extra work to verify this...
>> AWK
>>
>>
>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Hoffman, Allen
>>> Sent: Wednesday, September 12, 2007 2:34 PM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> is there synthetic speech for Creole? Just curious!
>>>
>>>
>>>
>>>
>>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Smith, Jamie
>>> Sent: Wednesday, September 12, 2007 2:29 PM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> I definitely feel we must have this as a provision. In Florida,
>>> public information is often in Spanish and Creole as well as
English.
>>>
>>>
>>
>>
>>> Some documents are the "Florida Comprehensive Assessment Test" test
>>> materials and while the document is in Spanish or Creole the test
>>> examples are always in English. The lack of coding for the language
>>> did cause speech to select a language and attempt to read the Creole
>>> with that language.
>>>> From the point of the first change to Creole on (even when text was
>>>
>>>
>>>> back
>>>>
>>>>
>>> to English), speech messed up. Adding the language code in the
>>> doctype and then to the specific sections which had a different
>>> language fixed the problem. The reason the language code wasn't
>>> done,
>>>
>>>
>>
>>
>>> simply because it wasn't required.
>>>
>>> -----Original Message-----
>>> From: = EMAIL ADDRESS REMOVED =
>>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
>>> Andrew Kirkpatrick
>>> Sent: Thursday, September 06, 2007 9:32 AM
>>> To: TEITAC Web/Software Subcommittee
>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>
>>> In the spirit of trying to reduce the extra weight of the new
>>> standards, I'll raise my question again -- why is language support
>>> in
>>>
>
>
>>> 508? We do have other WCAG standards that we have not included, and
>>> this seems like it is not needed in the U.S. standard.
>>>
>>> What is our rationale for requiring the language support in content
>>> formats and web and software provisions?
>>>
>>> AWK
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: = EMAIL ADDRESS REMOVED =
>>>> [mailto: = EMAIL ADDRESS REMOVED = ] On
>>>>
>>>>
>>> Behalf Of Peter
>>>
>>>
>>>
>>>> Korn
>>>> Sent: Tuesday, September 04, 2007 3:56 PM
>>>> To: TEITAC Web/Software Subcommittee
>>>> Subject: Re: [teitac-websoftware] 3d/3e for content format
>>>>
>>>> Hi Allen,
>>>>
>>>> We need to be careful with this one. Simple text editors (think
>>>> Notepad) won't be able to do this.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Peter Korn
>>>> Accessibility Architect,
>>>> Sun Microsystems, Inc.
>>>>
>>>>
>>>>
>>>>> Action item from Tuesday, 09/04.
>>>>>
>>>>> Content formats which support multiple languages MUST provide a
>>>>> programmatically determinable mechanism to identify the primary
>>>>> language, and the language of any sections which are in
>>>>>
>>>>>
>>>> another language
>>>>
>>>>
>>>>> from the primary language.
>>>>>
>>>>>
>>>>>
>>>>> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>>>>>
WebAIM is an initiative of:
