Thanks.
I can access it now from Xiphos (Windows) via the normal ftp connection.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/FTP-JSword-and-Xiphos-tp4651970p4651979.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
I've just alerted Brian Fernandez of FireBible
http://thegoan.com/firebible .
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/ESV-module-updated-to-current-version-possible-tp4650937p4651980.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
Hi DM,
I'm looking at it for how it displays in BPBible. Mostly it seems to show
up fine.
At the moment the code I had in place actually shows the tr greek text
links, though it doesn't know what to look them up in (there's no
dictionary matching the tr: scheme, right?).
I think I'll make it
On Feb 19, 2013, at 8:55 AM, Ben Morgan benpmor...@gmail.com wrote:
Hi DM,
I'm looking at it for how it displays in BPBible. Mostly it seems to show up
fine.
At the moment the code I had in place actually shows the tr greek text links,
though it doesn't know what to look them up in
Hi DM,
Did you think further about
http://crosswire.org/wiki/User:Dmsmith/KJV2011#Pilcrow_signs
since my last response therein?
David
PS. A curious aside: After Acts 20:36 there are no more pilcrows in the KJV.
/Specialist historians think the 1611 printers simply ran out of the movable
type
Please revert possessives back to ordinary apostrophes!
See http://crosswire.org/wiki/User:Dmsmith/KJV2011#Apostrophes
I already wrote to you about this, but I received no response.
David
--
View this message in context:
I updated the wiki with my response. They are the Unicode standard's preferred
possessive apostrophe.
In Him,
DM
On Feb 19, 2013, at 10:14 AM, David Haslam dfh...@googlemail.com wrote:
Please revert possessives back to ordinary apostrophes!
See
Yes. I thought my prior response was sufficient. The module has had them that
way for 7 years. Front-ends have a variety of ways that they handle the
pilcrow. I don't see the need for the change in the module.
If you take a look at the 1611, there is no space following the pilcrow:
On Tue, Feb 19, 2013 at 9:21 AM, David Haslam dfh...@googlemail.com wrote:
Some Bible modules that are for a language with a non-Roman script do NOT
have an attribute 'n' value in the OSIS,
so the automatically generated footnote markers (a, b, c, d, ...) look
especially bad.
That is what
On 2/19/2013 6:43 AM, DM Smith wrote:
On Feb 19, 2013, at 8:55 AM, Ben Morgan benpmor...@gmail.com
mailto:benpmor...@gmail.com wrote:
Hi DM,
I'm looking at it for how it displays in BPBible. Mostly it seems to
show up fine.
At the moment the code I had in place actually shows the tr greek
On Feb 19, 2013, at 11:12 AM, Chris Little chris...@crosswire.org wrote:
On 2/19/2013 6:43 AM, DM Smith wrote:
On Feb 19, 2013, at 8:55 AM, Ben Morgan benpmor...@gmail.com
mailto:benpmor...@gmail.com wrote:
Hi DM,
I'm looking at it for how it displays in BPBible. Mostly it seems to
The layout of some European PC keyboards combined with problematic keyboard
driver semantics causes many users to use a grave accent or an acute accent
instead of an apostrophe when typing in English (e.g. typing John`s or
John´s instead of John's)
That's a quotation from
Pilcrows look fun when they're red :)
But that's not a bug. :P
Oh, and if pilcrows could be moved to the end of the previous verse instead of
the start of the current verse, that would be fun :) But all good if they're
staying where they are ;)
There was some comments about the TR markup, and
Re: Google Summer of Code
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page
I strongly suspect Google would sponsor activity related to recent 'cloud
based notes with personal cloud option' technology recently discussed.
If someone has time to
14 matches
Mail list logo
