<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 2, 2008, at 10:58 PM, Gary Lo wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; ">Hi,<br><br>I'm a newbie to the Jsword comunity, and was wondering if its ok, if I help by writing documentation for the code on the Wiki. I know its probaby flawed with errors so please correct and teach me. Trying to do what I can to help.<br><br></div></span></blockquote>Gary,</div><div><br></div><div>Welcome!</div><div><br></div><div>Please feel free to do so. Once you have an account, you'll need to wait for 4 days before you can edit anything. The waiting period prevents lots of spam and wiki vandalism.</div><div><br></div><div>Having a high-level overview in the wiki would be great. There will be many of us that will pitch in to help correct your work.</div><div><br></div><div>I'd also suggest that low-level documentation be put into the code itself as JavaDoc. This would simply be patches to the code.</div><div><br></div><div>There is a lot in the jsword-devel archives that would be good to put into the wiki, too.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM<br></div><div><br></div><div><br></div><div><br></div><br></body></html>