Troy's JNI bindings are specific to Android currently. --Greg
On Wed, Sep 30, 2015 at 11:10 AM, DM Smith <[email protected]> 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 is > not in a form that JSword can parse. > > — DM > >> On Sep 30, 2015, at 12:04 PM, Peter Von Kaehne <[email protected]> wrote: >> >> Yes, we do have a tool. >> >> What it requires is a locale for Czech and the text of the reference. >> >> It is a method in the engine. >> >> 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. >> >> You can access the method directly from many languages - I use Perl - with >> the help of the various bindings. >> >> The main difficulty is to determine how much of the text to feed to the >> method. There 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" <[email protected]> >>> An: [email protected] >>> 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 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 really didn’t mean to say) that this >>> couldn’t be *optionally* very useful. I was just confused >>> whether it is now mandatory. I guess from your answer, it isn’t, >>> right? >>> >>>> 2) parser for references - what exactly are you trying to do? >>>> We have a few utilities etc which go this way and there is >>>> some equipment within the engine. >>> >>> I have notes with references in free text, e.g.: >>> >>> <note type="study" osisRef="Gen.1.1" osisID="Gen.1.1!v1" >>> n="v1">Př 8,22—24; Ž 93,2; 102,25—27v; Iz 40,21; Mk 13,19; >>> J 1,1—3; He 1,10—12; 1J 1,1; [Jde o počátek vesmíru a člověka; >>> nikoli Boha, který přebývá ve věčnosti (Iz 66,1n — tj. mimo prostor >>> a čas.]</note> >>> >>> So, I guess there is no other alternative than just develop >>> a good ol' regular expression which will be able to find all >>> those references ('Ž' is 'Žalmy' or 'Psalms' in Czech, 'Př' is >>> 'Proverbs', etc.) and spit out good <reference> elements inside >>> those <note>s. >>> >>> Or do you have some tools which can help me? I doubt it, but >>> certainly I don't resist using any of them. As of now, I am in >>> the depths of SAX events and all that fun. >>> >>> Best, >>> >>> Matěj Cepl >>> >>> -- >>> http://www.ceplovi.cz/matej/, Jabber: [email protected] >>> GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC >>> >>> There is no reason to suppose that most human beings are engaged >>> in maximizing anything unless it be unhappiness, and even this >>> with incomplete success. >>> -- Ronald Coase >>> Introduction to “The Firm, the Market, and the Law” >>> >>> >>> _______________________________________________ >>> sword-devel mailing list: [email protected] >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: [email protected] >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
