Hi,
Sorry for late response, I just realized this message.
In Alkitab (JSword based) all rendering structure is done using XSL
(osis to html) , so any note placement will be greatly influenced by
the XSL that used by JSword/BibleDesktop. Alkitab as in source code
does not place particular note in
Hi Andrew,
I would suggest you look into MacPorts -- it allows you to install the various
libraries that you'll need to compile Xiphos natively on your Mac. You'll need
Xcode, which is free on the Mac App Store, and then install the MacPorts
installer from http://www.macports.org and then dow
Nic say:
"Also, it was rather trivial to get Xiphos working native under X11 on
a Mac, so that may be a lot easier than running it under a VM on a
Mac?"
You could be right, however I run the VM for other reasons. I need
the tools 'Backtrack Linux' so nicely wraps together (day job requires
penetr
On 21/07/2012, at 6:42, Karl Kleinpaste wrote:
> Find us someone willing to put in the work to produce a Mac package.
> The build has been done before, but not in a manner representing a
> complete, install-ready package. We've been asking, but no one has been
> willing to step up to take on th
On 07/20/2012 01:42 PM, Karl Kleinpaste wrote:
Andrew Thule writes:
Chris, the '%2B' is a bug then. Is there a bug submission process for
Xiphos I can poke?
If it were a Xiphos bug, from the menubar: Help -> Report Bug.
But I don't perceive this as a Xiphos bug. I believe the engine filter
Confusion comes from POSIX's permissive approach to basename/dirname.
POSIX.1-2001 suggests something to the effect that the trailing slash
denotes where the dirname ends and the basename begins (which is
unfortunately in my opinion)
For example if you look at basename/dirname (which conforms to P
On 07/20/2012 12:48 PM, Andrew Thule wrote:
However, this idea of in line notes was from the OSIS Manual which
says "It is customary to include the notes directly within the text,
at the point to which they apply", so I was trying not to fight the
standard in my understanding - go with the flow t
>>Also, typically notes of this sort are labelled by letters or digits. Is
>>there a reason why you're using non-alphanumerics?
I didn't realize there was a restriction on using non-alphanumerics.
I was also tempted to try "†". I will dig into the standard to
conform to it, but no - no reason in
Andrew Thule writes:
> Xiphos (which I wish I could get working in OSX sometimes). I run it
> in a VM from Linux (on OSX).
Find us someone willing to put in the work to produce a Mac package.
The build has been done before, but not in a manner representing a
complete, install-ready package. We'
Karl, Chris, thanks for your responses.
Karl I appreciate your comments because you have removed some of the
mystique of Xiphos' behavior; which I appreciate. My tool of choice
for personal bible work happens to be Xiphos (which I wish I could get
working in OSX sometimes). I run it in a VM from
On 07/20/2012 11:06 AM, Andrew Thule wrote:
One benefit of having markup is that rendering mark-up is left to the
client. Even so, I'm looking at notes in Xiphos, Bibletime and
Alkitab and each treats them slightly different ways.
For example the following note 8:15 is rendered in:
Xiphos as su
Andrew Thule writes:
> The Xiphos behavior complete perplexes me - how is *n%2B constructed?
The short answer: Xiphos displays whatever the engine filters give it.
The long answer: For many years the filters generated just "*n" for
footnotes and "*x" for xrefs, without per-element identifiers fo
One benefit of having markup is that rendering mark-up is left to the
client. Even so, I'm looking at notes in Xiphos, Bibletime and
Alkitab and each treats them slightly different ways.
For example the following note 8:15 is rendered in:
Xiphos as superscript link "*n%2B" (with contents of the n
13 matches
Mail list logo
