5 replies to this topic

[TaSwavo]

[edit]sorry I put this in the wrong place maybe - should it be in tools? as the question is for people who MAKE modules

 

 

As BeST is no longer supported and doesn't work on my new computer I've decided to write something which can do the same thing which I will then make open source so we don't end up with an unsupported thing people can't use.

 

I've already started to make improvements even though I've hardly started (no need presently to say what format the lines are in as I use a regular expression - which I could, in theory, allow a user to alter).

 

My question is

Did people really use the formats where verses could start with a newline in what I would call the header?

For example

 

Gen 1

2 the earth was without form and void, with darkness over the face of the abyss, and a mighty wind that swept{\cf6\super b} over the surface of the waters.

or anything like

 

Gen 2:1

the earth was without form and void, with darkness over the face of the abyss, and a mighty wind that swept{\cf6\super b} over the surface of the waters.

 

I think my code would cover the second case but not the first - as the book/chapter/verse are on different lines.

I can write code to cover this but...

It would make my life easier - i.e. I could move on from making Bibles to the other types and even conversions

But if people really needed

Gen 1

2 the earth was without form and void, with darkness over the face of the abyss, and a mighty wind that swept{\cf6\super b} over the surface of the waters.

 

I'll work on that - as I really want to deal with things one step at a time

Edited by TaSwavo, 06 April 2013 - 05:23 PM.

[patchworkid]

hi 

 

Please try this

http://www.biblesupp...ooltip-tool-nt/

 

I use this tool to make all my modules and many others use this tool.

 

thanks

[TaSwavo]

I remember in the old days helping with Tooltip development

I'm writing something to replicate BeST and then add features to (already ANY input format seems fine except the one I mentioned).

Then I can move on and add more.

 

The difference is, I think open code. I could be wrong here - not sure if tooltip code is available or not.

 

Once written I'll put it on free access so if I go awol - or if people want to alter it - they can alter it as the code is there, not just the program.

 

I'm primarily writing it for me - to replace BeST as I'm scanning NEB and converting (with footnotes as a cmtx hoepefully) for my own use.

 

Many users used to use BeST and if folks use other things I may well ask for their advice later - if this proves useful for others besides just me

[Josh Bond]

FYI: Tooltip NT is source viewable, through the calculator function. It's coded in APL, so you have to like reading right to left Egyptian style hyroglifics, which is the layout and appearance of APL. It's a symbol based language.

 

My suggestion: make sure your BBLX, CMTX, DCTX, and DEVX output doesn't have an RTF header. It should instead use the supplied e-Sword header. Otherwise, the module won't respect the e-Sword font size set by the user. This is how all official e-Sword modules are constructed.

[TaSwavo]

I'm not outputting an rtf-header, just straight forward text. Obviously there are the rtf-like controls that allow colour alteration, paragraphing, superscript, etc. But no header.

 

I'm not sure what you mean by the e-Sword header because all I'm doing at present is creating and filling the Bible and Details tables and creating an index. Just straight-forward database stuff really.

At current I'm writing in v9 style (i.e. text) and not using blob data - is that Mr Meyer's way of protecting the file data? Or is that a feature of v10?

[Josh Bond]

An RTF header is an initial declaration that associates each font and color used in the file with a number. It's standard in RTF files.

 

Without an RTF header defined (and therefore using e-Sword's built-in header), \f0 is always e-Sword's default font, \f1 is e-Sword's greek font, \f2 is e-Sword's hebrew font, etc. \cf1 is black, \cf2 is blue (255, 0, 0), etc.

 

With an RTF header, the colors and fonts would be defined in the RTF header and each time they could vary 

 

Blobtext: That's a data type used on encrypted modules but not unencrypted ones, I think.