Hi Matěj,
You should have a look in the location where you install your sword modules. If
you compile from source and use the default paths, then it would be
/use/share/sword/. Wherever that sword module location is, you should find a
locales.d/ folder with all the available locales. If you don
Also, you need to feed it with a scope, IIRC
Sent from my phone. Apologies for brevity and typos.On 1 Oct 2015 7:17 am,
Peter von Kaehne wrote:
>
> The locale needs to be in same directory
>
> Sent from my phone. Apologies for brevity and typos.On 30 Sep 2015 10:27 pm,
> Matěj Cepl wrote:
> >
The locale needs to be in same directory
Sent from my phone. Apologies for brevity and typos.On 30 Sep 2015 10:27 pm,
Matěj Cepl wrote:
>
> On 2015-09-30, 16:04 GMT, Peter Von Kaehne wrote:
> > You can play with it by looking a the utilities within the
> > library's source. i am not at home, bu
On 2015-09-30, 16:04 GMT, Peter Von Kaehne wrote:
> You can play with it by looking a the utilities within the
> library's source. i am not at home, but I think it is called
> vs2osiref
$ vs2osisref 'Př 8,22-24' cs
Př 8,22-24
$
What am I missing ('Př' is 'Přísloví' in Czech, that is
On 2015-09-30, 16:10 GMT, DM Smith wrote:
> I think Troy has a binding to the SWORD library in Java. If it
> exposes the same as Peter mentions, you can call out from xslt
> to Java. We do something similar for JSword.
>
> JSword can do some level of parsing of the references, but
> your example
erences called xreffix.pl
>>
>> Peter
>>
>>> Gesendet: Mittwoch, 30. September 2015 um 16:44 Uhr
>>> Von: "Matěj Cepl"
>>> An: sword-devel@crosswire.org
>>> Betreff: Re: [sword-devel] OSIS markup best practice: sanity check
>>>
&g
re is a very badly written script of mine in
> sword-tools/modules/crosswreferences called xreffix.pl
>
> Peter
>
>> Gesendet: Mittwoch, 30. September 2015 um 16:44 Uhr
>> Von: "Matěj Cepl"
>> An: sword-devel@crosswire.org
>> Betreff: Re: [sword-dev
woch, 30. September 2015 um 16:44 Uhr
> Von: "Matěj Cepl"
> An: sword-devel@crosswire.org
> Betreff: Re: [sword-devel] OSIS markup best practice: sanity check
>
> On 2015-09-30, 11:12 GMT, Peter Von Kaehne wrote:
> > Couple of points:
> >
> > 1) The idea to have
On 2015-09-30, 11:12 GMT, Peter Von Kaehne wrote:
> Couple of points:
>
> 1) The idea to have specific modules or av11ns in the
> reference is not new and is IIRC part of the OSIS
> specification as an option. As an option it makes sense in
> following circumstances:
I haven’t said (and I reall
According to the OSIS manual, the work prefix (module name in front of the
reference) is an optional element. When it is absent, it defaults to the
current module.
JSword ignores the work prefix at this time. Not sure what SWORD does if the
ESV module has KJV: as a prefix.
— DM
> On Sep 30,
och, 30. September 2015 um 11:52 Uhr
> Von: "Matěj Cepl"
> An: gpl.programs.i...@gmail.com, "SWORD Developers' Collaboration Forum"
>
> Betreff: Re: [sword-devel] OSIS markup best practice: sanity check
>
> On 02/05/14 09:36, John Austin wrote:
> >
On 02/05/14 09:36, John Austin wrote:
> - Scripture reference tags will all specify target modules using
> osisRefs like this: "ESV:Matt.1.1" (and it may be that the specified
> module is not always installed, thus its av11n unknowable).
After a long time I found this old email, and given I am jus
New configuration properties require documenting properly.
i.e. In http://crosswire.org/wiki/DevTools:conf_Files
If there are caveats about usage, these can be covered as section notes
using the ... syntax.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-m
On 2 May 2014, at 5:36 pm, John Austin wrote:
> - Scripture reference tags will all specify target modules using osisRefs
> like this: "ESV:Matt.1.1" (and it may be that the specified module is not
> always installed, thus its av11n unknowable).
Will this affect backwards compatibility? What
The book list was implemented at same time as scope in jsword.
On 2 May 2014 15:18, "DM Smith" wrote:
>
> On May 2, 2014, at 3:36 AM, John Austin
> wrote:
>
> - There will be a Scope parameter in the .conf file, formatted as an
> osisID of the specified v11n, which details the books, chapters, a
On May 2, 2014, at 3:36 AM, John Austin wrote:
> - There will be a Scope parameter in the .conf file, formatted as an osisID
> of the specified v11n, which details the books, chapters, and verses that are
> included in the entire module. The Scope param is the only way to detect
> which books
Hi John
On the Scope parameter, I believe this was discussed and rejected.
(although JSword will have support for this, and will write a separate conf
file, should the scope be absent from the .conf file).
Chris
On 2 May 2014 08:36, John Austin wrote:
> IBT's repository has dozens of SWORD B
IBT's repository has dozens of SWORD Bible modules, and they all need to
be rebuilt for SWORD 1.7+ using OSIS module best practices (as outlined
in the extremely useful CrossWire wiki). Below are some conceivably
controversial issues. We hope to achieve excellent module functionality
with the v
18 matches
Mail list logo
