JSword uses CSS for the distinction. It also treats generated titles as
distinct from what the module provides.
In Him,
DM
> On May 27, 2017, at 12:09 PM, David Haslam wrote:
>
> Hi Dominique,
>
> The problem is that SWORD doesn't.
>
> It treats chapter descriptions as titles and therefore
Introductions have been mentioned.
For comparison, Aydeths' u2o.py (which we generally don't use) contains
these lines:
# # chapter cd tags # #
# the osis user manual says cd titles should be in an introduction div.
r'\cd': (u'\ufdd0',
u'\ufdd0'),
Aside: Unic
Thanks Troy,
Just so you all know, it's the content of the following USFM tag.
\cd text
What the Python script *usfm2osis.py* does is to convert this to:
1 Ko e fakatupu ʻoe langi mo māmani, 3 ʻOe
maama, 6 Mo e ʻatā, 9 Mo e mavahe ʻoe fonua mei he ngaahi vai, 11 Mo e
ngaohi ia ke fua, 14 ʻAe l
Hi David. I'm a little confused by your reply. When you say "SWORD doesn't,"
what do you mean?
If usfm2osis does something odd converting chapter 'descriptions' (I'd like a
definition of a chapter description. Is this a chapter intro?) to OSIS titles
then the owner of usfm2osis needs to improve
Hi Dominique,
The problem is that SWORD doesn't.
It treats chapter descriptions as titles and therefore as headers, but they
are neither.
This is because *usfm2osis* converts chapter descriptions to title elements,
even though they are simply not ordinary titles.
Aside: *ParaTExt* uses styleshe
On Sun, 21 May 2017 08:40:08 -0700 (PDT)
David Haslam wrote:
> In printed Bibles, *Chapter Titles* are normally bold text and typically
> without italics.
> SWORD always displays titles with a larger text size than verse text.
>
> *Chapter Descriptions* are normally in italics and either normal
Troy,
thank you for help. Intros are working now.
Stephan
Am 29.02.2012 12:34, schrieb Troy A. Griffitts:
Stephan,
There is a fundamental peace if info that might clear this up:
modules maintain their own keys unless you set them with a persistent
key. So your code would probably work with o
Stephan,
There is a fundamental peace if info that might clear this up:
modules maintain their own keys unless you set them with a persistent
key. So your code would probably work with one addition:
> VerseKey vk = VerseKey(key);
> vk.Headings(true);
> vk.setChapter(0);
> vk.setVerse(0);
vk
Manfred,
Recently I had a good go at reducing the numbers of both
http://www.crosswire.org/wiki/Special:LonelyPages orphaned pages and
http://www.crosswire.org/wiki/Special:UncategorizedPages uncategorized pages
in our wiki.
Next time people visit the wiki, in the left side panel, select
h
Am 18.12.2009 um 13:33 schrieb DM Smith:
> For details see:
> http://crosswire.org/wiki/OSIS_Bibles
> and
>
> http://crosswire.org/wiki/Osis2mod#Handling_of_Introductions.2C_Titles_and_Inter-Verse_Material
Umm. I haven't seen the wiki page about Osis2Mod.
Actually I think many thing
Regarding OSIS markup and osis2mod. For the most part osis2mod has to guess as
to where to put non-verse material. Basically, everything in the OSIS file
except the OSIS preamble (it's called a header but that's confusing for this
discussion) will be put somewhere in the module.
I'm not sure th
Hello Troy.
Ok, let me summarise:
Headings (as the name of the VerseKey function) are used for module, testament,
book and chapter intros.
>From looking into osis2mod.cpp they have to be encoded in OSIS like:
// Everything between the begin book tag and the first begin chapter tag is
inBookIntr
Sorry, I usually ignore my many typos, but some of these are in code...
fixed below:
The API lets you set this material with code like:
> VerseKey *vk = (VerseKey *)module.getKey();
> vk->Headings(true);
> (*vk) = "jn.2.0";
> module.setEntry("Intro Text for John 2");
>
These next 2 lines below w
Dear Manfred,
On 12/17/2009 12:02 PM, Manfred Bergmann wrote:
> Is it necessary to use a VerseKey for positioning in order to retrieve the
> headings?
>
VerseKey::Headings(true|false) is currently how to turn intro records on
and off for VerseKey navigated modules. These include:
testament.bo
Richard,
The windows software shows the number first, before any contents of the
entry (the heading is included in the entry). We have a new mechanism
that we call EntryAttributes. In the future, the heading information
will be parsed out of the entry and into something like:
[Headin
The ISV Bible has some, too.
Joachim
> Hi there ..
>
> On 13 Jun 2002 at 11:58, Daniel Freedman wrote:
> > 11. I have
> > yet to see the headings? Are they there, can someone give me a reference
> > to look at them?
>
> I know they are there in the Phillips (locked) module because I put the
Joachim,
I'm not sure what you need for the headings. What do you mean by "their
own paragraph"? As it is, they should display on their own line, using
line breaks before and after the heading. Are you looking for something
else? Do you need them to be outside the verse some how? I'm not sur
17 matches
Mail list logo
