[sword-devel] Web Interface
sword-devel@crosswire.org
sword-devel@crosswire.org
Sat, 22 Feb 2003 18:45:59 EST
--part1_182.1761cc26.2b8965b7_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 2/22/2003 12:57:40 PM Pacific Standard Time,
eekaikko@mail.student.oulu.fi writes:
> As far as I know there are no text based browsers which support javascript
> at
> the moment.
Does those text browser support UTF-8, Greek and Hebrew?
>
> Some people use a text mode browser through text terminal connection (in
> universities etc.) Some people don't even have a choice.
Again, Does those text browser support UTF-8, Greek and Hebrew?
>
> Some people like to switch javascript off because of security and popup
> windows.
>
> Probably all needed UI stuff can be made with just normal html without
> javascript.
As I said before, this is a feature, compatability trade off game. You can
always use html 3.2 to implement the UI and what will you got is good
compatability and less feature.
And there are WIN-WIN solution out there. We can make more than one
implementation of the UI by using different selector in the GET URL to
select. There are no need to be - a "you win I loss " or "I win you loss"
situration. However, of course, support multiple version of browser is always
a challenge. Not sure how to support Hebrew display for those text base
browser. Does those text browser build in Bi-Di ordering? Can they display
Biblical Greek and Biblical Hebrew? Does php support Bi-Di ordering on the
server side so you can convert the Hebrew from Logical order to Visual order
on the php before send to those text browser?
Netscape start to have Hebrew support since Nsetcape 6.2 althought we still
have some selection bug there.
If we are going to display OT Hebrew, it better to assume the brower could
support Logical order Hebrew. It is not fun to add Bi-Di ordering code to the
server side.
--part1_182.1761cc26.2b8965b7_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 12:57:40 PM Pacific Stand=
ard Time, eekaikko@mail.student.oulu.fi writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">As far as I know there are no t=
ext based browsers which support javascript at <BR>
the moment.</BLOCKQUOTE></FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-=
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">Does those text browser supp=
ort UTF-8, Greek and Hebrew?</FONT><FONT COLOR=3D"#000000" style=3D"BACKGRO=
UND-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>
Some people use a text mode browser through text terminal connection (in <BR=
>
universities etc.) Some people don't even have a choice.</BLOCKQUOTE></FONT>=
<FONT COLOR=3D"#000000" style=3D"BACKGROUND-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">Again, Does those text brows=
er support UTF-8, Greek and Hebrew?</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>
Some people like to switch javascript off because of security and popup <BR>
windows.<BR>
<BR>
Probably all needed UI stuff can be made with just normal html without <BR>
javascript.</BLOCKQUOTE><BR>
<BR>
As I said before, this is a feature, compatability trade off game. You can a=
lways use html 3.2 to implement the UI and what will you got is good compata=
bility and less feature. <BR>
<BR>
And there are WIN-WIN solution out there. We can make more than one implemen=
tation of the UI by using different selector in the GET URL to select. There=
are no need to be - a "you win I loss " or "I win you loss" situration. How=
ever, of course, support multiple version of browser is always a challenge.=20=
Not sure how to support Hebrew display for those text base browser. Does tho=
se text browser build in Bi-Di ordering? Can they display Biblical Greek and=
Biblical Hebrew? Does php support Bi-Di ordering on the server side so you=20=
can convert the Hebrew from Logical order to Visual order on the php before=20=
send to those text browser?<BR>
<BR>
Netscape start to have Hebrew support since Nsetcape 6.2 althought we still=20=
have some selection bug there. <BR>
If we are going to display OT Hebrew, it better to assume the brower could s=
upport Logical order Hebrew. It is not fun to add Bi-Di ordering code to the=
server side. <BR>
<BR>
</FONT></HTML>
--part1_182.1761cc26.2b8965b7_boundary--