Matthew Talbert ransom1...@gmail.com writes:
Am I understanding this correctly that you have keys with spaces, and
you put in NBSP and that all works in Xiphos? I thought that neither
normal spaces nor NBSP would actually work.
I don't know how he edited it, but the import file has plain
On 01/19/2011 05:39 AM, Karl Kleinpaste wrote:
Matthew Talbertransom1...@gmail.com writes:
Am I understanding this correctly that you have keys with spaces, and
you put in NBSP and that all works in Xiphos? I thought that neither
normal spaces nor NBSP would actually work.
I don't know how he
, while NBSP has a higher chance.
Peter
Original-Nachricht
Datum: Wed, 19 Jan 2011 05:39:47 -0500
Von: Karl Kleinpaste k...@kleinpaste.org
An: sword-devel@crosswire.org
Betreff: Re: [sword-devel] OSIS links
Matthew Talbert ransom1...@gmail.com writes:
Am I understanding
DM Smith dmsm...@crosswire.org writes:
The problem with spaces in an osisRef is that a space is defined as the
separator between one reference and another.
E.g. osisRef=Rom.1.1 Rom.2.1-Rom.3.1
Then I would like to think that either URL-standard '+' or hex-encoded
%20 would work in place of a
On 01/19/2011 09:18 AM, Karl Kleinpaste wrote:
DM Smithdmsm...@crosswire.org writes:
The problem with spaces in an osisRef is that a space is defined as the
separator between one reference and another.
E.g. osisRef=Rom.1.1 Rom.2.1-Rom.3.1
Then I would like to think that either URL-standard
Summarizing...
a. The regex is a horror.
b. The manual's definition is inconsistent, re: multiples.
c. The () -vs- [] syntax is wrong.
d. Whitespace isn't allowed at all.
e. Ignoring [d], there is a transform to something that ought to work,
but it's not known whether it actually does work.
On 01/19/2011 01:00 PM, Karl Kleinpaste wrote:
Summarizing...
a. The regex is a horror.
b. The manual's definition is inconsistent, re: multiples.
c. The () -vs- [] syntax is wrong.
d. Whitespace isn't allowed at all.
e. Ignoring [d], there is a transform to something that ought to work,
but
Do they work?
What is the proper format for a internal link - i.e. table of content in
a GenBook?
Peter
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change
On 18/01/11 21:24, Peter von Kaehne wrote:
Do they work?
What is the proper format for a internal link - i.e. table of content in
a GenBook?
The wiki has interestingly an empty section on that subject
Peter
___
sword-devel mailing list:
On Jan 18, 2011, at 6:08 PM, Peter von Kaehne wrote:
On 18/01/11 21:24, Peter von Kaehne wrote:
Do they work?
No. There is no support in the engine.
What is the proper format for a internal link - i.e. table of content in
a GenBook?
IIRC, the reference should have a workId of self.
On Wed, Jan 19, 2011 at 10:13 AM, DM Smith dmsm...@crosswire.org wrote:
On Jan 18, 2011, at 6:08 PM, Peter von Kaehne wrote:
On 18/01/11 21:24, Peter von Kaehne wrote:
Do they work?
No. There is no support in the engine.
There is support in the OSIS html href filters (look under
On 18/01/11 21:24, Peter von Kaehne wrote:
Do they work?
No. There is no support in the engine.
There is support in the OSIS html href filters (look under reference in
https://crosswire.org/svn/sword/trunk/src/modules/filters/osishtmlhref.cpp)
Looks like the following would work, where
On 18/01/11 23:31, Matthew Talbert wrote:
Except that genbooks often have spaces in the keys, and this doesn't
work. This was actually discussed quite a bit a few months ago when
Brian was working on some genbooks. I believe the recommendation for
spaces was to use special non-breaking spaces,
spaces was to use special non-breaking spaces, and these need some
kind of support in the filters. The importers may also be breaking
them, I'm not sure.
Thanks Matthew - this worked just fine, at least for Xiphos. NBSP is
accessible on most keyboards by using shift-space.
Am I
14 matches
Mail list logo
