The two versions mentioned are the only two that I have used. I have not tried
a 32-bit version of the latest release. The issue with the older 32-bit version
Rev 2893 ostensibly is the lack of the French versifications, which I need,
which is why I'm trying to use the more recent version.
I'm
The 32-bit was an earlier version. I don’t think the bit-ness matters.
— DM Smith
> On Nov 24, 2018, at 6:23 AM, David Haslam wrote:
>
> So the reported bug arises only from the 64 bit compilation of osis2mod.exe
> for Windows?
>
> Have I got this right?
>
> AFAIK, the 64 bit utilities
So the reported bug arises only from the 64 bit compilation of osis2mod.exe for
Windows?
Have I got this right?
AFAIK, the 64 bit utilities are only maintained by Karl as bundled with Xiphos
releases. I think Greg only provides 32 bit utilities where he compiles them
from time to time for
Worth noting that adyeths u2o.py converts some related USFM tags to OSIS
milestones.
Ideally, we should recognise the attributes allocated therein.
David
Sent from ProtonMail Mobile
On Sat, Nov 24, 2018 at 10:19, ref...@gmx.net wrote:
> Milestone or some such is exactly what I thought as
Hi John,
I think the whole side of OSIS commentaries is a bit unloved and I am
not surprised to see mistakes.
I have not seen problems on the Bible side. I will look.
As there is no real difference in terms of supposed engine handling of
either, you can also create a commentary in the encoding
Milestone or some such is exactly what I thought as they can be ignored easily. There is no issue for non CSS capable front-end, if a front-end is not able to deal with it they simply get switched off. Not different to other features. The rendering is no challenge and can be left to front-end who
Could this be done using the existing OSIS milestone element, allocating
suitable a new x-attribute to record that [say] the n attribute stores a verse
label?
cf. We already use milestone elements for particular module features, such as
the Pilcrow sign in the KJV.
The rendering by front-ends
This is a proposal which I think I can largely do at the library end myself,
but as it reflects a significant change I would like to have some input and
discussion.
I want to introduce verse number markers as a element separate from the verse
tag. By default these should not be shown, but
