Thread Subject: Default language
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.
From: Jared Smith
Date: Tue, Aug 14 2007 1:05 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
I just wanted to capture some conversation from today's call and open
this to discussion. The issue was regarding defining language in
electronic documents that do not support this, such as .txt documents.
Existing draft language is:
The default human language of electronic documents can be
programmatically determined, where the content format provides a means
for encoding language information.
SUGGESTED WORDING:
For electronic documents that support the identification of language,
the default human language can be programmatically determined.
This structure (limitation first, requirement last) better mirrors
other provisions we have.
Another more difficult issue is the identification of language for
passages or phrases within a document that doesn't support this. For
entire documents, the default language of the document is usually
apparent and can be determined, but for parts of a document, this is
more difficult.
OPTION 1:
In electronic documents that support the identification of language,
the human language of each passage or phrase can be programmatically
determined.
OPTION 2:
The human language of each passage or phrase in electronic documents
can be programmatically determined or are made available in text.
Option 2 allows the language of parts of text be identified in text
for .txt documents and the like, but also allows the non-programmatic
identification of language in things like HTML.
Thoughts?
Jared Smith
- Next message in Thread: None
- Previous message in Thread: None
WebAIM is an initiative of:
