Troy A. Griffitts wrote:
... I need a new laptop and considering buying a Mac! :)
Good choice. My MacBook is the best notebook computer I have ever used.
You should definitely seriously consider a new MacBook or MacBook Pro.
You can run Parallels on it and run Windows and Linux in virtual
m
Personally, I would like to see God's Word copied freely with no
barriers to copying, but I do like the idea of authentication with
digital signatures to detect tampering. We can do that with some texts,
but will not get legal permission to distribute some of them without
some annoyances. So, ironi
DM Smith wrote:
> Regarding poetry in general, I think lines provide little, if any,
> semantic meaning. (But then again, I failed the poetry part of high
> school English!) It seems that the sole purpose of poetic markup is to
> present poetry. (I'd be curious as to where the line breaks would be
Greg Hellings wrote:
> It remains a fact that a large portion of the world does not have
> high-bandwidth download options nor does it have modern computers. So
> we're still trying to accommodate people who are on POTS or slower
> systems with possibly tiny hard drives in remote areas of the worl
Chris Little wrote:
> We post Windows binaries because most Windows users don't have a
> compiler. We don't post Linux binaries because most Linux users _do_
> have a compiler (or could get one quickly and easily). I don't
> actually know whether Macs come with I compiler or not.
The vast majority
Dmitrijs Ledkovs wrote:
2009/4/24 Dmitrijs Ledkovs :
2009/4/22 Jonathan Marsden :
One quick first impression: there are still a few files in the RC2 tarball
that
licencecheck -r *
src/modules/common/sapphire.cpp: *No copyright* UNKNOWN
last ema
Dmitrijs Ledkovs wrote:
2009/4/24 Kahunapule Michael Johnson <kahunap...@mpj.cx>
Dmitrijs Ledkovs wrote:
2009/4/24 Dmitrijs Ledkovs :
2009/4/22 Jonathan Marsden :
One quick first impression: there are still a few files
DM Smith wrote:
> A good place for this would be:
> www.crosswire.org/wiki/Alternate_Versification.
>
> Just add a section that gives:
> The name of the versification, the description of the versification
> and the date that it was added to the SWORD engine.
The number of versification schemes tha
Is there any hope of getting Bibledit's Sword module generator working
with Sword well enough that it actually works in the near future?
I just tried it, again, and failed to get something that actually works
in Xiphos.
I have permission to create Sword modules from a large number of Bible
transl
Matthew Talbert wrote:
Is there any hope of getting Bibledit's Sword module generator working
with Sword well enough that it actually works in the near future?
Are you trying to generate a module within Bibledit or using the
usfm2osis.pl script, then osis2mod? I believe every
subversion repository.
Teus.
On Fri, 2009-08-21 at 13:55 +1000, Kahunapule Michael Johnson wrote:
Is there any hope of getting Bibledit's Sword module generator working
with Sword well enough that it actually works in the near future?
I just tried it, again, and failed to get somethin
I noticed, while attempting to access
https://crosswire.org/svn/gobible/, that crosswire.org's self-signed
security certificate is expired. I recommend replacing that expired,
self-signed certificate with a free class 1 certificate from
http://www.startssl.com/, since the root certificate is alread
On 01/01/2010 10:12 PM, David Haslam wrote:
> ...
>
> On the whole, Steve was very favorable as regards the same issuer referred
> to as http://cert.startcom.org/ StartCom .
>
This is the same organization that runs the startssl.com site (which is
linked to from the above site). I'm happy with
L.Allan-pbio wrote:
> FYI:
>
> www.borland.com/us/products/turbo/index.html
>
> I haven't installed or evaluated these (C++, Delphi, Delphi-Net, C#) and
> they are huge files.
>
Cool! I needed something productive to do with my new broadband connection!
I'm still downloading, but it looks like
Troy A. Griffitts wrote:
> Peter,
> This is a great idea. The non-technical challenge seems to be to get
> ESV, NASB, or NET copyright holders to allow us to use the xrefs and
> possibly the notes from the Bible. ...
Another possibility is to use the free crossreference lists included
wit
Peter von Kaehne wrote:
I read this with interest. Can these utilities insert the crossreferences into USFM? Or do they merge at a different level?
WordSend inserts and
translates crossreferences on the fly while converting from USFM to
Microsoft Word XML for publication. It is intended
[EMAIL PROTECTED]
wrote:
Is there a
tool available to convert a
Bible from GBF to OSIS?
Yes. See http://ebible.org/translation/gbf.html.
That is a .NET executable, so it requires the .NET runtime or Mono.
I haven't tried running it on Linux, but with Mono, it should be
possib
The domain byztxt.com no longer hosts a Greek New Testament. It has been
taken over by a porn site operator. This site should be deleted from
mentions on the Crosswire web site and in the Sword project source code. :-(
Michael
___
sword-devel mailing l
I was just looking at converting some Bibles to Sword modules, and read
http://crosswire.org/sword/develop/swordmodule/. It all seemed easy
enough to actually do, until I found out that the Win32 executables at
http://crosswire.org/ftpmirror/pub/sword/utils/win32/ don't actually
work on my Windows
Thanks. That helps. :-)
Michael
Chris Little wrote:
It looks like the debug builds of two of the utilities were released. In
any case, they're all updated now to release builds of the latest versions.
--Chris
Kahunapule Michael Johnson wrote:
I was just looking at conve
Chris Little wrote:
> I'm not totally convinced we should do that. When I prepare modules from
> OSIS docs, I always perform validation in an external validator.
> (Personally I use Oxygen, but there are also XML Spy, MSV, topologi,
> Xerces, etc.)
>
> Do people feel that incorporating a real va
DM Smith wrote:
> In XML any attribute can have an empty value (btw, there is a unicode
> close quote above) and Sword/JSword handle it properly.
>
> But you have given me the idea to use an empty marker attribute for
> the eID milestone as in:
> The
>
That should work. :-) Of course, just n
How does the Sword project handle display of OSIS text quotations when:
1. the or element is used without a marker attribute,
2. the or element is used with a marker attribute,
3. no or elements appear, or
4. quotation punctuation (“, ‘, ’, ”, «, », —, newline, etc.) appears
outside of or e
Karl Kleinpaste wrote:
> One thing I have to observe is that even your mail message here came
> across claiming a character set of "windows-1252". There is also
> -1251 and possibly a couple others. These are very nonstandard,
> Microsoft-only encodings where \221 thru \227 (in particular) have
>
DM Smith wrote:
Kahunapule Michael Johnson wrote:
How does the Sword project handle display of OSIS text quotations when:
1. the or element is used without a marker attribute,
The speech element is not handled, except to process its content. It is
as if the element
Chris Little wrote:
> I know XML allows for empty attribute values, but I'm not sure whether
> they are formally equivalent to no attribute at all.
>
No, actually there is nothing in XML that specifies such an equivalence.
It is the semantics of the particular application that determine that.
I
So... it sounds like I could simply convert USFM to OSIS with the
obvious conversions (like \p ... -> ...) plus
\qt ->
\qt* ->
\wj ->
\wj* ->
<< -> (unless at the beginning of a paragraph
with an unended quotation in progress, then
>> ->
< -> (unless at the beginning of a paragraph
with an
DM Smith wrote:
Kahunapule Michael Johnson wrote:
So... it sounds like I could simply convert USFM to OSIS with the
obvious conversions (like \p ... -> ...) plus
Remember to have the surround the entire paragraph.
Of course.
In various source I have seen
I think I remember some discussion about how pre-verse text should be
marked in OSIS-based Sword modules. For example, you might want to
include a Psalm title before verse 1 officially starts when getting the
first verse of a Psalm, or maybe include a subtitle (for those
translations that have them
DM Smith wrote:
> If a title does not have the type of main or chapter, then it is
> understood as a preverse title. There is no special tagging needed.
>
Cool.
> Titles which are part of the Bible (e.g. psalm titles) should have the
> attribute canonical="true". This will prevent Sword from h
Chris Little wrote:
> There is no such mechanism, to my knowledge.
>
> Should I start indexing all of our modules?
>
> Pros:
> - Users won't have to do their own indexing.
> - Most users don't know about indexing at all, so they'll suddenly see
> huge speed improvements and be able to access Lucen
Chris Little wrote:
> Unfortunately, that's impractical. With a virus scanner on, the
> compression takes 5 minutes for a single Bible (OT+NT) on my Win32
> system (2GHz Pent-M, 7200RPM drive), due to the constant disk access. We
> would either have to tell users to disable virus protection or d
Dear Joshua:
This is a problem with The Sword Project engine used by Gnomesword. It
does not handle white space properly on some module types. It also
affects MacSword. I don't know if an update is available directly from
Crosswire.org that fixes that, yet, or not.
Michael
Joshua David wrote:
>
[EMAIL PROTECTED] wrote:
Psalm 23 has a missing space between "restores" and "my soul".
Actually, it doesn't. See http://ebible.org/web/Psalms.htm#C23V3. Are
you reading the text in one of The Sword Project Bible readers? They
have some issues in properly converting Bibles and di
DM, I hope the following document accurately reflects the dialect of
OSIS we discussed:
http://ebible.org/translation/SaneOSIS.htm
Any comments? Typos? Improvement suggestions?
Yes, I know the dialect of OSIS documented above isn't what I generate
with the WEB & HNV, yet, but I plan to make it s
DM Smith wrote:
> Michael,
> It is good to hear from you again.
>
You, too...
Of course, I now feel really stupid, but I'm glad you pointed out the
error of my ways before I went too far down that path. :-)
> Couple of comments:
> does not have a milestoned form.
Arghh. That pretty much messes
Any suggestions on the best way to encode interlinear texts in OSIS?
Take a look at a good Greek/English interlinear New Testament for an
idea of what I'm talking about.
My current idea is to encode the translations a separate works, but add
milestone markers at sync points to each translation. A
DM Smith wrote:
> Different question:
> How would one display an interlinear in HTML?
> The key requirement is that a line of stacked text would naturally wrap,
> responding to window resizes in an expected way.
>
I was hoping someone else would answer this. I couldn't think of a good
way, real
Troy A. Griffitts wrote:
> I hate releasing when I know there are outstanding issue.
There are ALWAYS outstanding issues. Every once in a while, we might be
in ignorant bliss and not know about some of them, but there is never a
time when there are no outstanding issues. The question we should be
a
Troy wrote:
>> Either way, just to clarify, SWORD is licensed under version 2. We do
>> not add the common "or later" clause. It seems odd to me that so many
>> projects effectively give GNU the right to license their software under
>> whatever future terms they want. 3 is still fairly controver
Has anyone sought official permission to distribute the Tok Pisin
(Melanesian Pidgin) Bible from the copyright owners, The Bible Society
of Papua New Guinea, yet?
If not, I would like to volunteer to do so, both for Crosswire Bible
Society and for my own web sites. I have in my possession a
hi
Chris Little wrote:
> We don't have anyone pursuing permission to distribute this Bible, so it
> would be great if you did.
>
OK. I'll start with a paper letter to them, with a donation enclosed. :-)
Gift exchange is an important part of the culture, here.
Shalom,
Michael
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This evening, I met with the executive directory and a Bible translation
consultant of the Bible Society of Papua New Guinea. I hand-delivered a
written request for permission for the Crosswire Bible Society to
distribute all of their copyrighted Scri
Daniel Griswold wrote:
> Hello Michael Paul Johnson,
> I use the WEB frequently on my Mac using the program MacSword. I am
> using the text version 1.6 and it seems that there are a LOT of spaces
> missing. Typically every chapter will have at least a few (sometimes
> quite a few) words joined toge
Chris Little wrote:
Eeli Kaikkonen wrote:
On Sun, 23 Mar 2008, Kahunapule Michael Johnson wrote:
The missing spaces are all there in the master copy of the World English
Bible at http://eBible.org/web/. Therefore, you are seeing a bug in
MacSword, either with the
Troy A. Griffitts wrote:
> Steve DeRose has started to compile a comprehensive list of English
> Bible. If anyone has time to review and comment, it would be most
> appreciated:
>
> http://derose.net/steve/Bible/EnglishBibleTranslations.html
>
Some additional details for the World English Bi
I contacted the Bible Society of Papua New Guinea some time ago, asking
permission to post the many Bible translations in many languages that
they hold the copyright to online in various formats (including Sword).
I got a nice letter back saying that they needed to consider the
ramifications an
Chris Little wrote:
> If you think it would help your efforts (which we certainly appreciate),
> you could mention that WBTI gave us permission to distribute 40 Bibles
> (38 NTs, a full Bible, and an NT+Psalms), primarily in languages of
> Mexico & Guatemala. There may be more, but that's the fi
Chris Little wrote:
> Should the NASB be presented with verse-per-line layout (e.g. via a
> at the end of each verse)?
I think so, because that is the way the translators intended for it to
be presented, and therefore how they punctuated it.
> Does anyone have a printed edition that
> uses a
[EMAIL PROTECTED] wrote:
hi
do u know of a site where they read the bible from Gen to Rev? I was
off line for 4 years and i cant find the one I used to use.
A man read the bible from beg to end (free audio) and it was an easy
way for me to do my devotions and write comments. Can u help?
Tr
WEB and HNV modules in as close to OSIS format as can be reasonably done
are available at http://eBible.org/web/webosis.zip and
http://eBible.org/hnv/hnvosis.zip. Those files validate against the OSIS
schema. As far as I know, the only significant compliance issue has to
do with changing quotat
Thanks for working on that, Chris. :-)
An updated ASV text is on the way. It turns out that the texts at
asv1901.com and eBible.org/asv have been corrected with different sets
of user feedback, so converting them to a common format and seeing what
is different has revealed some more typos to corr
I see Chris is already working on this, but I'll provide some
information, just in case it might be useful.
The GBF specification is at http://ebible.org/bible/gbf.htm. There are a
couple of extensions not listed there, but those are not in use by HNV
or WEB texts. GBF is kind of an old format,
Chris Little wrote:
> The text derives from the OSIS document on ebible.org (with only the
> header and apocrypha removed before running the importer), so it isn't
> conformant OSIS 2.1. But there is some chatter about changing the
> standard in various ways to accomodate presentational quotation m
Why Use OSIS When USFM and USFX Work Better?
By
(Kahunapule) Michael Johnson, http://kahunapule.org
6
February 2006
Conclusion
OSIS is a poor choice for a standard Scripture archiving,
authoring, and interchange format for members of the Forum of Bible
Translation Agencies. Its inadequacies
moting one markup that hasn't really caught on because
of its problems when a better one is available won't necessarily make it
more likely that you will get a widely-accepted standard. Indeed, you
could kill off a better standard only to see your favorite pet die of
its own birth defects
Sean Boisen wrote:
> I appreciate the problems with trying to use an inherently
> tree-structured notation like XML to mark overlapping regions. I'm not
> in touch with what the OSIS thinkers are thinking: other than the
> milestone approach, has anybody considered combining in-line markup
> identi
Chris Little wrote:
>
>
> Kahunapule Michael Johnson wrote:
>> Chris Little wrote:
>>> The text derives from the OSIS document on ebible.org (with only the
>>> header and apocrypha removed before running the importer), so it isn't
>>> conformant OSI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Blessed are you who don't take offense easily at what others post, for you
shall not be continually irritated.
Blessed are you who only write loving and kind words, for you shall be
spared many flame wars.
Blessed are you who take the time to send
Chris Little wrote:
> Like any NEW technology, it requires that we do work. To that extent,
> it is more work than we would have had to do had we just stuck with
> GBF, ThML, etc. But I would rather move to OSIS alone than stick with
> those formats because OSIS can actually handle markup needs tha
wrote:
>
> Kahunapule Michael Johnson wrote:
>
>> XML Myths Debunked
>>
>> Myth 1: Anything in XML is inherently better for archiving and
>> processing than non-XML formats. *False.* XML is just a set of rules
>> defining how text files can define data, with ta
Chris Little wrote:
> Kahunapule Michael Johnson wrote:
>> First, please let me apologize. By the personal attacks in your message,
>> you may have gotten the impression that I was attacking you personally
>> instead of promoting the idea that OSIS is not appropriate to set f
I recently received a couple of queries about the World English Bible
Sword module. I haven't checked to see what the last update was, but
lots of updates in the Old Testament and a few typo corrections in the
New Testament have happened over the last year or so. Anyway, I'm
planning to post anothe
I'm wondering if the seemingly redundant verse end tags might actually
be useful for encoding of this sort. You could put extra titles and
stuff that goes before a canonical verse after the end tag for the
previous verse, but before the verse marker. Then, when going to
display a verse range wi
Tom Stout wrote:
> Hello I just invested several days formatting a Bible Text to use with
> e-sword. Let's just say it was an experience that drew me closer to
> the Lord in terms of patience and perseverance. :)
>
> The translation is a South American Indian language called Guarani.
> And before
It is a good idea to automatically detect if the right key was used or
not before feeding possible gibberish to the next process in the chain.
The tricky part about this is to make the way you do that of least
practical use to an attacker who might be using a brute force
key-checking attack. Natura
Ultimately, anything you can see on screen can be copied and converted
to other useful formats, technically, if not legally. Ease of doing so
may vary greatly with the application. Any Bible study program that is
any good supports text export and copy & paste functions, but you
may have to do i
DM Smith wrote:
> There is a simple advantage to supporting OSIS as the only format
> going forward: Standardization.
Standardization is sometimes a good thing. Sometimes it is a bad thing.
Suppose that I proposed a new standard for electrical power
distribution, world-wide. Instead of 120 VAC 60
L.Allan-pbio wrote:
>> Please, any of you that have the time, read the manual and provide
>> revisions and comments. As they are actively working on OSIS 2.5, now
>> is a good time.
>
> Based on your reading, would the upgraded osis spec be usable to
> prepare a module that could be used to generat
Chris Little wrote:
> To make a long story short, OSIS is the best format for everything
> that Sword needs to do. It encodes Bibles richly and explicitly. It
> can contain every other type of book we handle (though none of these
> require the same level of richness in markup). And it's open and it
Jonathon Blake wrote:
On 3/5/06, Kahunapule Michael Johnson <[EMAIL PROTECTED]> wrote:
The future is hard to predict. Currently, OSIS (or rather a subset of OSIS) is used by The Sword Project as one option for Scripture text import.
There also is a utility progra
Jonathon Blake wrote:
ThinkAll .. do not believe that they will agree to bring their distribution practice into conformance with the requirements of the law or with what they are permitted to do under the GPL.
This is where The Sword Project can use the services
Jonathon Blake wrote:
Kahuna pule Michael wrote:
program that reads Unicode USFM Scripture files and produces a Microsoft Word 2003 XML (WordML) document
Given your desire for open standards, why does it produce output for a
non-standard, proprietary, closed file format
Martin Gruner wrote:
Besides, it gave a working solution while I waited for
OpenOffice.org Writer to gain OpenDocument text format support, and while
I'm still waiting for SIL Graphite support to be added to OOo.
Oh! I didn't know that SIL Graphite was already incorporated in
David Blue (Mailing List Addy) wrote:
On Friday 10 March 2006 23:29, Kahunapule Michael Johnson wrote:
I am not a religious follower of open source and ISO standards. Actually, I
care little about ISO endorsement of any standard unless the standard is
both relevant to the task at
I just set up a new Linux (Ubuntu Bionic Beaver) system for someone, including
an install of Xiphos. When trying to preload a few Bible translations, I
noticed that Xiphos couldn't see the eBible.org repository. However, I can see
and use it just fine from some other front ends. Is anyone else h
Aloha!
A Blackfoot Matthew module is in the eBible.org repository as bla1890eb,
sourced from Jon Bitgood's digitization. (Duplication of Public Domain texts
doesn't bother me, by the way, but it might be worth checking before working on
a module if duplicated effort might bother you.)
I am try
a breaking change that I wasn't
aware of until just now.) Anyway, we are back in service. The Blackfoot Matthew
module is listed under the language autonym (Siksika).
On 12/16/18 9:01 AM, Kahunapule Michael Johnson wrote:
> Aloha!
>
> A Blackfoot Matthew module is in the eBible.org
ubject: Re: [sword-devel] Module upload: BlaMat
>>> From: David Haslam
>>> To: sword-devel@crosswire.org
>>> CC:
>>>
>>>
>>> Installed bla1890eb from eBible.org to PocketSword.
>>>
>>> No search ind
Yes, indeed. It is in my work queue, to follow SILE integration with Haiola for
PDF generation.
On 5/2/20 7:51 PM, David Haslam wrote:
> This underlined the need and urgency for PocketSword development to continue.
> It’s also 2 years since PS 1.4.8 was released to support iOS 10 and 64-bit.
>
>
Forwarded Message
Subject: Message from 172.70.178.47
Date: Thu, 3 Mar 2022 11:06:53 + (UTC)
From: mich...@ebible.org
Reply-To: noctisde...@yahoo.com
To: kahunap...@gmail.com
Name-> anonymous
Email-> noctisde...@yahoo.com
Subject-> reporting typ
urely structural document can long survive in total
absence of some way to control the presentation. CSS helps...
--
Aloha,
Kahunapule Michael Johnson
You may donate
online or
mark "Fund Code #70" and mail to:
WORLD OUTREACH
MINISTRIES
PO BOX B
MARIETTA GA
As I am working on the source for one of hundreds of Bible
translations that I have processed recently, I'm amazed at the
variations and spottiness of the scope of translations, especially
with respect to Old Testament portions. The number of variations is
almost as high
that makes use of the \rq_...\rq* tag.
It prompted a minor improvement to Dirk Kaiser's utility. ;-)
David
On 2012-02-20 19:23, Kahunapule Michael Johnson wrote:
Fixed. Thanks.
On 02/20/2012 06:21 AM, you wrote:
http://crosswire.org/wiki/Converting_SFM_Bibles_to_OSIS#Markers_Not_Yet_Supported_by_usfm2osis.pl
says:
"If you come across USFM files containing markers that are not yet supported,
please contact one of the Perl script developers in CrossWire."
After processing over 200 USFM Bible translations
On 03/03/2012 06:47 AM, Matěj Cepl wrote:
>> Nearly half the OSIS editor body is subscribed to this list, so please,
>> if you have an honest question about the standard, humbly ask and know
>> that there might be an answer you hadn't considered.
>
> I am not sure why I should be humble, when notic
On 03/03/2012 09:55 AM, Matěj Cepl wrote:
> On 3.3.2012 20:38, Kahunapule Michael Johnson wrote:
>> Bible formatting that were not shared by my good friends, the Bible
>> translators. That means that either the Bible formatting has to
>
> Tell me about. What I am doing i
On 03/03/2012 02:55 PM, Matěj Cepl wrote:
>
>> Wrt USFX - this is simply a XML-fied form of USFM and adds very little
>> to the discussion. It is essentially a structureless mess, replacing
>> each USFM tag with a XML set of tags. If I did not have OSIS, I would go
>> ThML, but certainly never USFX
On 03/04/2012 11:08 AM, Daniel Owens wrote:
> But BibleTime, Xiphos, and BibleCS simply do not display the text of
> Canonical psalm titles. That is a severe bug.
Wow. That is a scary bug! I guess that means that for now, it is not OK to use
___
sw
On 03/05/2012 03:20 AM, Greg Hellings wrote:
> You seem quite taken with USFM, but remember that CrossWire and SWORD
> do not support USFM as an import or display format. Therefore
> information beyond just how to convert USFM into OSIS or ThML or GBF
> which are supported is not really of importan
On 03/05/2012 08:07 AM, Peter von Kaehne wrote:
On 05/03/12 17:33, Greg Hellings wrote:
On Mon, Mar 5, 2012 at 11:28 AM, Kahunapule Michael Johnson
wrote:
On 03/05/2012 03:20 AM, Greg Hellings wrote:
You seem quite
On 03/06/2012 12:47 AM, Jonathan Morgan wrote:
You accurately preserve all of the original text and
punctuation (including quotation punctuation) exactly as
it was in the original USFM. This involves the complete
On 03/05/2012 09:59 PM, Peter von Kaehne wrote:
> ...
>> I'm trying to convert Scripture files on a scale and with speed that
> is apparently unprecedented.
>
> The scale might be unprecedent, but there are reasons for that
>
> 1) None of us have yet encountered a USFM text which is actually clean.
On 03/06/2012 04:12 PM, Jonathan Morgan wrote:
On Wed, Mar 7, 2012 at 6:17 AM,
Kahunapule Michael Johnson <kahunap...@mpj.cx>
wrote:
On 03/06/2012 12:47 AM, Jonathan Morgan
On 03/07/2012 04:53 PM, Jonathan Morgan wrote:
... I'm suggesting copyright is the wrong tool to use to
enforce such claims, since I can't see that it will actually
target the one responsible for the wrong. I agree quality
control is a
On 03/07/2012 09:04 PM, Matěj Cepl wrote:
> On 8.3.2012 07:14, Kahunapule Michael Johnson wrote:
>> The #1 reason they give me for copyrighting Bibles is that they want
>> some way to protect the text from corruption. Arguments to the
>> contrary are futile.
>
> Can I
On 03/08/2012 12:46 AM, Jonathan Morgan wrote:
Hi Michael,
On Thu, Mar 8, 2012 at 5:14 PM,
Kahunapule Michael Johnson <kahunap...@mpj.cx>
wrote:
On 03/07/2012 04:53 PM,
Jonathan Morgan
On 03/08/2012 03:53 PM, Karl Kleinpaste wrote:
> Howzabout you grant us a smidgen of respect for the positively alarming
> amount of effort that gets put into our collective software efforts and
> our collective module creation skills. Waddayasay you don't use as your
> starting assumption that we
Interesting reading... and I much prefer word spaces. In practice, though, I
had to adjust some of my software to not insert any extra spaces in Khmer. I
think I got it right
On 03/10/2012 05:49 AM, David Haslam wrote:
> Jot and tittle or typograpical custom?
>
> Some background reading for
On 03/10/2012 10:10 PM, David Haslam wrote:
> The preliminary Khmer NT module contains zero-width spaces as word
> separators.
I did the same thing in the Khmer Hammond Version and the Khmer Standard
Version. The zero-width spaces are points where line breaks are allowed and
where letters don't
1 - 100 of 323 matches
Mail list logo
