[sword-devel] How to represent special characters in osisID attributes in a gen book

2011-10-04 Thread Martin Denham
In gen books it seems that the osisID is normally used as the chapter title
e.g.
div type=chapter osisID=Chapter 1

However some chapter titles can contain special characters e.g.
div type=chapter osisID=God's Sovereignty
contains an apostrophe.

I thought that, being an xml attribute, it should be:
div type=chapter osisID=Godapos;s Sovereignty
but that gives the error:
The value 'God's Sovereignty' of attribute 'osisID' on element 'div' is
not valid with respect to its type, 'osisIDType'.

So how should a chapter title of God's Sovereignty be represented?

Thanks
Martin
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to represent special characters in osisID attributes in a gen book

2011-10-04 Thread Greg Hellings
I thought osisID attributes were very strictly defined with certain
reference schemes and abbreviations?  I get fuzzy on the osisID topic
but I thought it was an enumerated list of values that were pretty
much like matt.1.1, matt.1.2, etc? You're probably looking for a title
attribute/element (not sure which it is in OSIS).

--Greg

On Tue, Oct 4, 2011 at 10:05 AM, Martin Denham mjden...@gmail.com wrote:
 In gen books it seems that the osisID is normally used as the chapter title
 e.g.
     div type=chapter osisID=Chapter 1
 However some chapter titles can contain special characters e.g.
     div type=chapter osisID=God's Sovereignty
 contains an apostrophe.
 I thought that, being an xml attribute, it should be:
     div type=chapter osisID=Godapos;s Sovereignty
 but that gives the error:
     The value 'God's Sovereignty' of attribute 'osisID' on element 'div' is
 not valid with respect to its type, 'osisIDType'.
 So how should a chapter title of God's Sovereignty be represented?
 Thanks
 Martin
 ___
 sword-devel mailing list: sword-devel@crosswire.org
 http://www.crosswire.org/mailman/listinfo/sword-devel
 Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] How to represent special characters in osisID attributes in a gen book

2011-10-04 Thread Brian J Dumont

Per Chris Little (circa 2009 when I asked the same question:

   The relevant bit of the regex is: (\p{L}|\p{N}|_|(\\[^\s]))+

   The last option permits escaping any non-space character with a
   leading \. Further to that, NBSP (0xA0), by convention, represents
   space (0x20) in osisID/osisRef. But it will need to be escaped since
   it's not a letter, number, or underscore.

In my experience since then, the non-breaking space is far more 
confusing than it's worth.  I would suggest:

div type=chapter osisID=Gods_Sovereignty

A bit crude, but it has a number of advantages:
- It is valid
- I think it works on all SWORD front-ends that support genbooks
- It doesn't get messed up by code that is passing a link (imagine that 
someone later wants to create a hyperlink from a different module to 
this spot in your module)


Brian

On 10/04/2011 11:05 AM, Martin Denham wrote:
In gen books it seems that the osisID is normally used as the chapter 
title e.g.

div type=chapter osisID=Chapter 1

However some chapter titles can contain special characters e.g.
div type=chapter osisID=God's Sovereignty
contains an apostrophe.

I thought that, being an xml attribute, it should be:
div type=chapter osisID=Godapos;s Sovereignty
but that gives the error:
The value 'God's Sovereignty' of attribute 'osisID' on element 
'div' is not valid with respect to its type, 'osisIDType'.


So how should a chapter title of God's Sovereignty be represented?

Thanks
Martin


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



--
---
The question is not Have you accepted Jesus into your heart, but Has
Jesus accepted you into His heart?; not have you given your whole
life for God, but has God given His whole life for you
- Pr Bryan Wolfmueller, 2010


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


[sword-devel] EMTV text source URL is now unrelated

2011-10-04 Thread David Haslam
The file EMTV.conf includes


However, this URL no longer relates to the EMTV translation.  It appears to
be a site about the Stock Market.

A Google search reveals that the relevant URL should now be
http://www.majoritytext.com/

David

--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/EMTV-text-source-URL-is-now-unrelated-tp3871411p3871411.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] CLucene 2

2011-10-04 Thread Troy A. Griffitts

Deji,

That's awesome!  Thank you (and to Tom)!

Anyone want to take a shot at adding to configure.am and cmake a define 
and ifdef those lines depending on the version of clucene found?




On 10/04/2011 05:46 AM, Deji Akingunola wrote:

On Fri, Sep 2, 2011 at 12:48 PM, Greg Hellingsgreg.helli...@gmail.com  wrote:

So I'm looking at the trouble with building CLucene 2 and the first
snag seems to hinge around the helper functions we use -
lucene_utf8towcs and lucene_wcstoutf8 and the like. These are still
present in CLucene 2, but they are not exposed through a public
header.  As I see it, we can either choose to add their signatures to
our own headers when CLucene 2 is detected and move on with it, or we
can appropriate their entire implementation of the functionality and
rename it as sword_utf8towcs and the like provided the licenses allow
us to do so.  Anyone have a firm opinion on the better path to take?


Tom Callaway created the attached patch to make sword-1.6.2 work with
clucene-2.3.3.4. I have tested the patched sword with Xiphos, and it
seems to work O.K.

- Deji




___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page