[sword-devel] Web Interface

Sat, 22 Feb 2003 18:53:11 EST

--part1_bf.2e8f7ebd.2b896767_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 2/22/2003 1:32:35 PM Pacific Standard Time, 
hvdkooij@vanderkooij.org writes:

> It seems you are not entirely informed. PHP can be completely transparant. 
> Wether or not valid HTML/XHTML/.... is generated is the programmers 
> responsibility.
> 
> But javascript is not an option for anyone using any of the following 
> browsers:
> - Lynx
> - w3m
> - links

As I asked in the previous mail- does those browser support Bibical Hebrew 
and Greek?

> 
> Beyond that I see no point in adding javascript when all issues can be 
> handled very well without them.

Disagree. How do you allow user to only put in a valid book and chapter 
combination when user cannot type in that language from his computer ? (A lot 
of Chinese user in US only have Chinese font but do not have Chinese input 
method but the book abbreviation is in Chinese and they do not know English 
Abbreviation)

> 
> We want to be accessible to all. While a text browser works for blind 
> using a brialle ruler, using frames and/or javascript makes it completely 
> inaccessable to them.

There are different definitation about accessibility. Yes, allow blind peopel 
to use brialle ruler is accessibility issue. Allow a Chinese user have 
chinese font but no Chinese input method to access the book is ALSO 
accessibility issue. 
The difference is are we using the JavaScript to solve accesssibility issue, 
or we remove JavaScript so other accessability technology which do not 
support JavaScript can deal with it. 

As I said in my early mail. There are no need to be "I win you loss" or "You 
win you loss" There are win win solution out there. Just cost higher.

> 
> Hugo.

--part1_bf.2e8f7ebd.2b896767_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=
=3D"Arial" LANG=3D"0">In a message dated 2/22/2003 1:32:35 PM Pacific Standa=
rd Time, hvdkooij@vanderkooij.org writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">It seems you are not entirely i=
nformed. PHP can be completely transparant. <BR>
Wether or not valid HTML/XHTML/.... is generated is the programmers <BR>
responsibility.<BR>
<BR>
But javascript is not an option for anyone using any of the following <BR>
browsers:<BR>
- Lynx<BR>
- w3m<BR>
- links</BLOCKQUOTE></FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLO=
R: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">As I asked in the previous m=
ail- does those browser support Bibical Hebrew and Greek?</FONT><FONT  COLOR=
=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERI=
F" FACE=3D"Arial" LANG=3D"0"><BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
Beyond that I see no point in adding javascript when all issues can be <BR>
handled very well without them.</BLOCKQUOTE></FONT><FONT  COLOR=3D"#000000"=20=
style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Ar=
ial" LANG=3D"0"><BR>
<BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">Disagree. How do you allow u=
ser to only put in a valid book and chapter combination when user cannot typ=
e in that language from his computer ? (A lot of Chinese user in US only hav=
e Chinese font but do not have Chinese input method but the book abbreviatio=
n is in Chinese and they do not know English Abbreviation)<BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
We want to be accessible to all. While a text browser works for blind <BR>
using a brialle ruler, using frames and/or javascript makes it completely <B=
R>
inaccessable to them.</BLOCKQUOTE></FONT><FONT  COLOR=3D"#000000" style=3D"B=
ACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0"><BR>
<BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">There are different definita=
tion about accessibility. Yes, allow blind peopel to use brialle ruler is ac=
cessibility issue. Allow a Chinese user have chinese font but no Chinese inp=
ut method to access the book is ALSO accessibility issue. <BR>
The difference is are we using the JavaScript to solve accesssibility issue,=
 or we remove JavaScript so other accessability technology which do not supp=
ort JavaScript can deal with it. <BR>
<BR>
As I said in my early mail. There are no need to be "I win you loss" or "You=
 win you loss" There are win win solution out there. Just cost higher.</FONT=
><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMIL=
Y=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
</FONT><FONT  COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
Hugo.</BLOCKQUOTE><BR>
<BR>
</FONT></HTML>
--part1_bf.2e8f7ebd.2b896767_boundary--