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
This isn't quit an OSIS question, but it is a Sword Module Question.
I've been working on an Inuktitut Sword Module, and been having some
font/rendering issues, most of which are now solved - but not all.
The last and final 'font' issue seems to be related to how a module is
represented in client
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
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
On 07/20/2012 11:43 AM, Andrew Thule wrote:
This isn't quit an OSIS question, but it is a Sword Module Question.
I've been working on an Inuktitut Sword Module, and been having some
font/rendering issues, most of which are now solved - but not all.
The last and final 'font' issue seems to be rel
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
Chris thanks for your reply.
>> So Inuktitut is in Alkitab's database, where it was missing from Xiphos' (or
>> there was some other problem there).
It doesn't seem to be completely so. Xiphos renders Inuktitut
properly in the bible window and gives you the ability to expressly
choose fonts for
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'
Andrew Thule writes:
> Xiphos renders Inuktitut properly in the bible window and gives you
> the ability to expressly choose fonts for bible rendering. In the
> left pane (module window) however the same is not true.
I don't understand the distinction you're making between "the bible
window" and
Karl, fonts 'appear' rendered differently in the main window (large
upper right where bible text appears) and not rendered at all (in
windows) in the pane immediately to the left (upper left above the
previewer pane), which I understand (perhaps incorrectly) pulls some
info from the .conf file.
In
>>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:
> Karl, fonts 'appear' rendered differently in the main window (large
> upper right where bible text appears) and not rendered at all (in
> windows) in the pane immediately to the left (upper left above the
> previewer pane), which I understand (perhaps incorrectly) pulls some
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
Yes, Xiphos in Linux is perfect.
On Friday, July 20, 2012, Karl Kleinpaste wrote:
> Andrew Thule > writes:
> > Karl, fonts 'appear' rendered differently in the main window (large
> > upper right where bible text appears) and not rendered at all (in
> > windows) in the pane immediately to the left
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 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
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
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
Hi, all.
I am in a position to learn "Scala" in the near future.
And at the same time, I came to a stage where I would like to contribute
to the opensource community beside translations in a long term.
So far I found this language seems to be good at making things
"semantic" or "AI", like LISP
19 matches
Mail list logo
