[sword-devel] Web Interface
sword-devel@crosswire.org
sword-devel@crosswire.org
Sat, 22 Feb 2003 22:08:48 EST
--part1_cb.2ff53560.2b899540_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 2/22/2003 6:40:46 PM Pacific Standard Time,
chrislit@crosswire.org writes:
> >Does those text browser support UTF-8, Greek and Hebrew?
>
> lynx supports UTF-8 just fine. Greek / Hebrew would depend on whether the
> user has fonts and other things set up correctly for it.
>
> Most users don't care about that though. 90% of users will just want
> English. Probably 98% just need a Latin-* charset.
:( :( :( very very very western kind of thinking. Don't know how you come out
that number. (90% and 98%). English user is less than 30% of the total
Internet users these days. And Latin * charset users is < 70% of the Internet
users these days. Does Bible said "God so loved the World" or does the Bible
said "God so loved the western world". :{
>
> >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.
>
> Just assuming browers support BiDi reordering is a bad idea. To do a
> proper implementation, we would need to survey those browers and OSes that
> can handle logical vs. visual ordering and serve up the appropriate one.
> I would be surprised if IE on Win9x did reordering automatically (since
> the rest of that OS doesn't).
I think that depend on which version of IE is running on it. Since my team
implement the Bi-di support in Mozilla, I think I can figure it out early
next week.
Doing the actual visual reordering on the
>
> server side is trivial since Sword has a filter (basically just a wrapper
> for an ICU call) to do this (and implementing it actually was kind of
> fun :).
>
Not fun if you have no idea does the client support it or not
--part1_cb.2ff53560.2b899540_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 6:40:46 PM Pacific Standa=
rd Time, chrislit@crosswire.org writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">>Does those text browser sup=
port UTF-8, Greek and Hebrew?<BR>
<BR>
lynx supports UTF-8 just fine. Greek / Hebrew would depend on whether=20=
the <BR>
user has fonts and other things set up correctly for it.<BR>
<BR>
Most users don't care about that though. 90% of users will just want <BR>
English. Probably 98% just need a Latin-* charset.</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">:( :( :( very very very west=
ern kind of thinking. Don't know how you come out that number. (90% and 98%)=
. English user is less than 30% of the total Internet users these days. And=20=
Latin * charset users is < 70% of the Internet users these days. Does Bib=
le said "God so loved the World" or does the Bible said "God so loved the we=
stern world". :{</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>
>Does those text browser build in Bi-Di ordering? Can they display <BR>
>Biblical Greek and Biblical Hebrew? Does php support Bi-Di ordering on t=
he <BR>
>server side so you can convert the Hebrew from Logical order to Visual o=
rder <BR>
>on the php before send to those text browser?<BR>
><BR>
>Netscape start to have Hebrew support since Nsetcape 6.2 althought we st=
ill <BR>
>have some selection bug there. <BR>
>If we are going to display OT Hebrew, it better to assume the brower cou=
ld <BR>
>support Logical order Hebrew. It is not fun to add Bi-Di ordering code t=
o the <BR>
>server side. <BR>
<BR>
Just assuming browers support BiDi reordering is a bad idea. To do a <=
BR>
proper implementation, we would need to survey those browers and OSes that <=
BR>
can handle logical vs. visual ordering and serve up the appropriate one.&nbs=
p; <BR>
I would be surprised if IE on Win9x did reordering automatically (since <BR>
the rest of that OS doesn't). </BLOCKQUOTE></FONT><FONT COLOR=3D"#000=
000" 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">I think that depend on which=
version of IE is running on it. Since my team implement the Bi-di support i=
n Mozilla, I think I can figure it out early next week. <BR>
<BR>
Doing the actual visual reordering on the </FONT><FONT COLOR=3D"#000000" st=
yle=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Aria=
l" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT><FONT COLOR=3D"#000000"=
style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"A=
rial" LANG=3D"0"><BR>
server side is trivial since Sword has a filter (basically just a wrapper <B=
R>
for an ICU call) to do this (and implementing it actually was kind of <BR>
fun :).<BR>
</BLOCKQUOTE><BR>
Not fun if you have no idea does the client support it or not<BR>
<BR>
</FONT></HTML>
--part1_cb.2ff53560.2b899540_boundary--