> or not, I cannot judge). BPBible uses VC++ to build Sword binaries to
> make it work with the standard Python distribution on Windows.
Just so you know, it's completely possible to build the Sword binaries
and the Python SWIG bindings with MinGW on Windows, and have them work
with the standard
On Sat, Oct 3, 2009 at 1:07 AM, Jonathan Marsden wrote:
> OK, I'll bite. Let's run with this discussion a bit...
>
> Greg Hellings wrote:
>
>> Most Linux or FreeBSD users are familiar with a source tree compile
>> with autotools.
>
> Really? In 2009? Do you have a source or at least some anecdo
On Fri, Oct 2, 2009 at 10:42 PM, Gerald Zimmerman wrote:
> I have an additional request. Windows, as delivered, makes everything easy
> for "frontenders" but ignores any thirst for the knowledge of compiling. I
> suspect that any of us Windows users could use the most recent Sword upgrades
> i
I have an additional request. Windows, as delivered, makes everything easy for
"frontenders" but ignores any thirst for the knowledge of compiling. I suspect
that any of us Windows users could use the most recent Sword upgrades if we
knew how to compile. Could someone provide instructions and/o
> It is largely a frontend issue on what to do with the data, but the
> engine could make it easier to know what the data is (as DM has pointed
> out). I'd like maybe an SWMgr::parse method that would return
> module/key pairs in a ListKey somehow. Dunno. Please don't think we're
> abandoning su
Yeah yeah, I know we need more support for everything :)
It is largely a frontend issue on what to do with the data, but the
engine could make it easier to know what the data is (as DM has pointed
out). I'd like maybe an SWMgr::parse method that would return
module/key pairs in a ListKey som
Greg Hellings wrote:
A common (and understandable) response. Chris maintains the Windows
build of the tools used to create modules. The link is somewhere in the
archives, though obviously any binary build could be dated relative to SVN.
The Windows utilities are hosted at:
http://crosswire
On 10/02/2009 04:18 PM, Matthew Talbert wrote:
It "seems" straightforward.
Does it handle "self"? (Which will be in dictionaries.)
Doesn't appear to.
Does it handle Bible.KJV:reference or Bible.ref-system.work:reference? (I.e.
where the workID is not merely the name of the module but
> It "seems" straightforward.
> Does it handle "self"? (Which will be in dictionaries.)
Doesn't appear to.
> Does it handle Bible.KJV:reference or Bible.ref-system.work:reference? (I.e.
> where the workID is not merely the name of the module but contains other
> info?) At least it should then spl
On 10/02/2009 03:06 PM, Matthew Talbert wrote:
I thought there was a long discussion about
this previously and we discovered that there was indeed support for
this, just the OSISHTMLHREF filters needed updated to output something
for it. As of 1.6.0, the filters have been modified to output swo
>> I thought there was a long discussion about
>> this previously and we discovered that there was indeed support for
>> this, just the OSISHTMLHREF filters needed updated to output something
>> for it. As of 1.6.0, the filters have been modified to output sword://
>> style links for these referen
On 10/02/2009 01:54 PM, Matthew Talbert wrote:
3) A reference with a workID that matches the [NAME] of a module will refer
to that module. It is not required that the module exist at all. The use of
future names will probably merit some discussion to codify them. There is no
support for this in t
I think there is some misunderstanding here Matthew.
It is not a ICU problem as such here, but a problem which transliteration is
printed.
Ruby is a means to assert one of several ways of pronouncing a given Kanji sign
by giving a "Ruby" pronounciation guide in a different script, a syllable b
> 3) A reference with a workID that matches the [NAME] of a module will refer
> to that module. It is not required that the module exist at all. The use of
> future names will probably merit some discussion to codify them. There is no
> support for this in the SWORD engine at this time.
Is this st
On Fri, Oct 2, 2009 at 15:07, Jonathan Marsden wrote:
> I suggest that this is a clear sign that today's Linux distros do not expect
> their users to be experienced in downloading and compiling tarballs at a
> command line in order to install software :)
I'd go further and suggest that Linux us
2009/10/2 jovanni :
> When reading Japanese Kougo module ( which has ruby annotations ) with
> Xiphos 3.1, right cricking on the text and selecting [Modules options]
> ->[Tranliteration] , we have alphabetical texts instead of kanji characters.
>
> For example, japanese text of Genesis 1.1
>
> はじめに
OK, I'll bite. Let's run with this discussion a bit...
Greg Hellings wrote:
> Most Linux or FreeBSD users are familiar with a source tree compile
> with autotools.
Really? In 2009? Do you have a source or at least some anecdotes to
back up that idea?
If you are correct, why was it valuable t
When reading Japanese Kougo module ( which has ruby annotations ) with
Xiphos 3.1, right cricking on the text and selecting [Modules options]
->[Tranliteration] , we have alphabetical texts instead of kanji characters.
For example, japanese text of Genesis 1.1
はじめに神は天と地とを創造された。
is transliterated
On Oct 2, 2009, at 8:40 AM, Brian J. Dumont wrote:
Jonathan Morgan wrote:
On Fri, Oct 2, 2009 at 2:19 AM, Brian J. Dumont > wrote:
Additionally, I have a question about tags. I'd like to put
down
markers for other modules to later link to. Is it true that OSIS
tags
only support "hre
John,
On Fri, Oct 2, 2009 at 7:27 AM, wrote:
> Greg,
>
> I didn't mean to trigger anything between Windows and Linux users !!
>
I don't think you did - I think it was other peoples' comments, my own
included.
>
> To be honest, all I'm trying to do is create one Bible to submit to the
> team f
Chris,
That has been very helpful, thanks. It clarifies for me how to mark the
deuterocanonical texts. I'll have a look at the OSIS manual when I get to
that stage, and try to get the subtype implementation done correctly when
I've reached the OSIS stage. At present, I'm working on trying to ext
Jonathan Morgan wrote:
> On Fri, Oct 2, 2009 at 2:19 AM, Brian J. Dumont wrote:
>
>> Additionally, I have a question about tags. I'd like to put down
>> markers for other modules to later link to. Is it true that OSIS tags
>> only support "href" and not "name" attributes? Maybe this should
Greg,
I didn't mean to trigger anything between Windows and Linux users !!
To be honest, all I'm trying to do is create one Bible to submit to the team
for use on the various platforms. So I'm not going to be a regular user and
Linux is therefore too much of a learning curve for me.
My m
> Von: David Haslam
> We Windows users (using the latest binary v1.5.11, & not having compiled
> from source) see several beta modules that cannot be installed yet.
> Four of these are not due to needing av11n, but because they require the
> Ruby markup feature.
I am not aware that any frontend
On Fri, Oct 2, 2009 at 2:19 AM, Brian J. Dumont wrote:
> Hi all,
>
> I'm preparing a commentary in OSIS, and have some feature requests :
>
> OSIS tables
> additional hi types: small-caps, underline, super, sub (small-caps is most
> important of these, but I'd appreciate all four)
> markers. Whe
Everyone,
My "tongue-in-cheek" "scratchy-head smiley" provocative remark has achieved
what I'd hoped for.
viz. Some clarification of the perceptions and related technical
background.
For that I am profoundly grateful.
One further point in my mind relates to the use of The SWORD Project for
Win
26 matches
Mail list logo
