[sword-devel] Updates- Myanmar Bible Project.

Levi Lim sword-devel@crosswire.org
Tue, 24 Feb 2004 21:49:20 -0600


This is a multi-part message in MIME format.

------=_NextPart_000_008C_01C3FB20.0F1BA0E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear  Sword Team & KMTAye,

Greetings. Sorry for the late reply. I have been on the road for some =
missions trip.
I have recently revisited Myanmar was out internet communication for a =
while.

Updates on the Myanmar Bible Project:

Phase 1: Complete Burmese Language Bible Software.
1. New Testament (Judson Version) has been completed typed and in the =
process of editing.
2. Old Testament (Judson Version) has begun and will take 1-3 months to =
complete typing.

Began to interface this soft copy of Judson Version Burmese Bible with =
the Sword Project Platform.
Have 8 volunteers in Myanmar, Malaysia and USA helping right now.
Target to complete the Beta version of Burmese Bible by December 2004. =
New Testament by July 2004.

Need Help:
(1) To produce Burmese Unicode for the software..... so that the entire =
software can be operated by Burmese literate people with no English =
functionality. There is currently Myanmar fonts and the "ability to do =
word processing using this true type fonts."

PHASE 2: Complete Chin, Kachin, Karen and other Myanmar languages .
1.  Many of these tribal languages used Roman alphabets and therefore =
post lesser technical challenges. I am confident to be able to secure =
permission for various Bible Societies to install the Bible into the =
sword project.

PHASE 3: Bible Commentaries, Bible Dictionary, Sermons and other helps =
in Burmese language.

PHASE 4: Making the Myanmar Bible Software available to the Myanmar =
churches world-wide.

PHASE 5: Continual Research and Development of more Myanmar Bible =
Reference Materials.

------=_NextPart_000_008C_01C3FB20.0F1BA0E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: SimSun;
}
@font-face {
	font-family: Sylfaen;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @SimSun;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue bgColor=3Dwhite>
<DIV>
<DIV><STRONG><FONT face=3DArial>Dear&nbsp;&nbsp;Sword Team &amp;=20
KMTAye,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=3DArial>Greetings. Sorry for the late reply. I have been =
on the=20
road for some missions trip.</FONT></DIV>
<DIV><FONT face=3DArial>I have recently revisited Myanmar was out =
internet=20
communication for&nbsp;a while.</FONT></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial>Updates on the Myanmar Bible=20
Project:</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial><U>Phase 1: Complete Burmese Language =
Bible=20
Software.</U></FONT></STRONG></DIV>
<DIV><FONT face=3DArial>1. New Testament (Judson Version) has been =
completed typed=20
and in the process of editing.</FONT></DIV>
<DIV><FONT face=3DArial>2. Old Testament (Judson Version) has begun and =
will take=20
1-3 months to complete typing.</FONT></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=3DArial>Began to interface this soft copy of Judson =
Version=20
Burmese Bible with the Sword Project Platform.</FONT></DIV>
<DIV><FONT face=3DArial>Have&nbsp;8 volunteers in Myanmar, Malaysia and =
USA=20
helping right now.</FONT></DIV>
<DIV><FONT face=3DArial>Target to complete the Beta version of Burmese =
Bible by=20
December 2004. New Testament by July 2004.</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><STRONG>Need Help:</STRONG></FONT></DIV>
<DIV><FONT face=3DArial>(1) To produce Burmese Unicode for the =
software..... so=20
that the entire software can be operated by Burmese literate people with =
no=20
English functionality. There is currently Myanmar fonts and the "ability =
to do=20
word processing using this true type&nbsp;fonts."</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial>PHASE&nbsp;2: Complete Chin, Kachin, =
Karen and=20
other Myanmar languages .</FONT></STRONG></DIV>
<DIV><FONT face=3DArial>1.&nbsp; Many of these tribal languages used =
Roman=20
alphabets and therefore post lesser technical challenges. I am confident =
to be=20
able to secure permission for various Bible Societies to install the =
Bible into=20
the sword project.</FONT></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial>PHASE 3: Bible Commentaries, Bible =
Dictionary,=20
Sermons and other helps in Burmese language.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial>PHASE 4:&nbsp;Making the Myanmar Bible =
Software=20
available&nbsp;to the Myanmar&nbsp;churches =
world-wide.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=3DArial></FONT></STRONG>&nbsp;</DIV>
<DIV><STRONG><FONT face=3DArial>PHASE 5: Continual Research and =
Development of=20
more Myanmar Bible Reference Materials.</FONT></STRONG></DIV>
<DIV>&nbsp;</DIV></DIV></BODY></HTML>

------=_NextPart_000_008C_01C3FB20.0F1BA0E0--