Thanks David. It’ll be a while before I get to it, but I appreciate having it documented on Jira and with a specific test case.
I’m not sure what is “official” wrt the issues tracker. I think it was originally bugs.crosswire.org <http://bugs.crosswire.org/> and I changed it to tracker.crosswire.org <http://tracker.crosswire.org/>, since it’d be used for more than just bugs, but also requests and planning. I don’t care for jira.crosswire.org <http://jira.crosswire.org/> as that is product specific and not purpose driven. The emails that jira sends have tracker.crosswire.org <http://tracker.crosswire.org/>. You said it works more or less. What is less about it? DM > On Apr 2, 2025, at 3:00 AM, David Haslam <dfh...@protonmail.com> wrote: > > Hi DM, > > I've added a link for the OSIS Zip. > > See my new comment in [MODTOOLS-108] osis2mod fails badly on some Bible > translations - CrossWire Tracker: Bugs, Issues, Requests and Plans > <https://jira.crosswire.org/browse/MODTOOLS-108?orderby=created+DESC%2C+priority+ASC%2C+updated+DESC> > > Aside: IIRC, our issues tracker URL domain is now officially > jira.croswire.org <https://jira.croswire.org/> > though tracker.crosswire.org <https://tracker.crosswire.org/> also still > works (more or less). > > Best regards, > > David > > Sent with Proton Mail <https://pr.tn/ref/SWXT9A5YZ67G> secure email. > > On Tuesday, April 1st, 2025 at 8:42 PM, DM Smith <dmsm...@crosswire.org> > wrote: >> Is this related to MODTOOLS-108 in Jira, which Michael just created a few >> days ago? See: http://tracker.crosswire.org/browse/MODTOOLS-108 >> >> If so, can you add the comment there. Otherwise can you find or create an >> appropriate issue in Jira in MODTOOLS? >> >> Can you supply a mock osis xml that reliably goes into an infinite loop? >> I’ve heard reports of this but cannot reproduce. >> >> I’m not sure what you meant by “do not exist in any of the SWORD >> versifications” as osis2mod only considers the versification that is >> supplied when running it. >> >> The goal of osis2mod is to build a module, handling most errors as >> recoverable and giving exactly what recovery was provided. So in that sense, >> it should not stop. >> >> When a book is not in the v11n, it is appended to the module, which means it >> is appended to the last verse of the chosen v11n. >> >> Maybe a different message if the book or chapter is not in the >> versification? This would avoid calling out each verse that is not in the >> v11n. >> >> Perhaps a flag for diagnostics only? >> >> Maybe creating a histogram of repeated messages (don’t output the same >> message, one right after the other but rather buffer them with a count. When >> the new message is different from the last, output the last with a count. At >> the end of the program, output the outstanding buffered messages). >> >> Maybe we need a separate tool to find the best v11n, of the known v11ns? >> I.e. the one with the least mismatches. >> >> DM >> >>> On Apr 1, 2025, at 2:19 AM, David Haslam <dfh...@protonmail.com> wrote: >>> >>> If osis2mod encounters a set of osisID that do not exist in any of the >>> SWORD versifications - it appears to go into an endless loop attempting to >>> link each one to Rev.22.21 >>> >>> Wouldn’t it be preferable for it to fail with an error message? eg >>> >>> INVALID osisID - cannot continue! >>> >>> Best regards, >>> >>> David >>> >>> Sent from Proton Mail <https://proton.me/mail/home> for iOS >>> _______________________________________________ >>> sword-devel mailing list: sword-devel@crosswire.org >>> http://crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
