I took some time tonight looking more into where all the time is spent
loading a chapter of text. I put some microsecond timers around the more
significant calls in my LoadText call and this is what I found when
loading KJV version of Psalm 119 w/ all options off.
m_modCurText->SetKey(keyCur);
On Jul 8, 2008, at 9:46 AM, Ben Morgan wrote:
> There are two things to note here:
> a) the ESV is a compressed module (uses the zText driver).
> The zText driver is quite a bit slower than the rawtext one (around
> 20-30x slower!)
> Here are the times taken to getRawEntry for a compressed and
That was for the whole of the ESV.
Machine specs were something like:
1.67GHz processor with 490MB RAM under WinXP.
Its a few years old.
This was done from python.
God Bless,
Ben
---
The Lord is not slow to f
On Jul 7, 2008, at 11:58 PM, Daniel Owens wrote:
Here is the wiki page:
http://www.crosswire.org/wiki/index.php/Frontends:SWORDReader
It's pretty bare right now. I would be happy to add more than just a
wish list such as features, screenshots, etc., but I thought that
might be a place to
Thank you!
Daniel Owens wrote:
> Here is the wiki page:
> http://www.crosswire.org/wiki/index.php/Frontends:SWORDReader
>
> It's pretty bare right now. I would be happy to add more than just a
> wish list such as features, screenshots, etc., but I thought that
> might be a place to list support
This French website has several African Bible translations!
http://visionneuse.free.fr/ La Bible multilingue
Bible complète en français avec notes et glossaire ("Bible du Semeur")
Nouveau Testament en français avec glossaire ("Bible du Semeur")
Nouveau Testament en Arabe standard
Bible co
DM Smith wrote:
> Should SWORD directly render the gloss attribute? Or should it treat it
> the same way as it does a lemma or a morph? And would it be a good time
> to add xlit also?
Gloss is handled fairly similarly to lemma and morph. The render filter
should do something to render the att
Chris Little wrote:
> DM Smith wrote:
>
>> I'm wondering whether it is encoded sufficiently. I see how the module
>> is marked, but it doesn't seem that it maps well to the definition of
>> ruby. I'm not sure of the OSIS semantic that is being used.
>>
>
> For those who haven't looked at
DM Smith wrote:
> I'm wondering whether it is encoded sufficiently. I see how the module
> is marked, but it doesn't seem that it maps well to the definition of
> ruby. I'm not sure of the OSIS semantic that is being used.
For those who haven't looked at the markup, the first ruby annotated
wor
I'm wondering whether it is encoded sufficiently. I see how the module
is marked, but it doesn't seem that it maps well to the definition of
ruby. I'm not sure of the OSIS semantic that is being used.
The w3c definition of ruby (see: http://www.w3.org/TR/ruby/) allows for
markup for renders tha
Daniel,
I'll help out. I already moderate a couple of others here, so I know
what I am getting myself into.
-- DM
Daniel Glassey wrote:
> The copyright at crosswire dor org mailing list is moderated and I
> (and Troy) haven't had time for a long time to keep up with it so
> there are now more tha
Hi
Thanks for your feedback! Yes you are correct the Ruby text is not currently
correctly displayed. This is a software limitation - lack of adequate control
in the back end and lack of adequate display functionality in the frontends.
The current plan is to have this matter resolved in the next
Sure David!
Just let me know what you'd like me to do... by the looks of if you should
start by simply deleting everything that was populated into the CMS by
default and then start to create what you want.
If you give me some direction I can run with it and see what happens. Email
me or hit me u
Ben,
For reference what verses did you use for this example, and what were
the machine specs?
David
Ben Morgan wrote:
> Hi,
>
> There are two things to note here:
> a) the ESV is a compressed module (uses the zText driver).
> The zText driver is quite a bit slower than the rawtext one (around
> 20
Hi,
The beta versions of the japanese modules use ruby, which the engine doesn't
support yet. Support for this is planned in the next version of the engine.
So I don't think this is a problem with the JapKougo module (you would
probably find the same with the other japanese modules in beta).
God
Hi,
There are two things to note here:
a) the ESV is a compressed module (uses the zText driver).
The zText driver is quite a bit slower than the rawtext one (around 20-30x
slower!)
Here are the times taken to getRawEntry for a compressed and uncompressed
ESV:
uncompressed: 1.89 seconds (this is a
Hi,
I just downloaded the Mac OSX beta version of JapKougo. I opened it and found
that the pronunciation guide (I think it is also known as Ruby text) ended up
becoming part of the sentence instead of being placed in parenthesis or above
the character. Is there any way to change that? Because
The KJV is free for your use. Every now and then we get questions
about the origin of the Strong's numbers, so it is a good idea to let
people know this. The terms and conditions are as follows:
King James Version (1769) with Strongs Numbers and Morphology
This is the King James Version of t
18 matches
Mail list logo
