[sword-devel] Japanese Bibles in Beta and some other stuff

DM Smith dmsmith at crosswire.org
Sun Aug 20 10:01:50 MST 2017

My response on JSword-devel mailing list:
JSword has no support for ruby markup. I haven’t looked at it for years, but from what I remember, it was experimental, using OSIS in a non-standard way. Chris added support for it in the engine as he did for other things that are still not considered as worthy of use. Such as support for additional compression schemes, i.e. bz2 and xz. (I did add support for those and Chris and I tested them.) So, to add ruby, I’ll need to have a clear understanding of the markup, how it is beneficial to an end user and how that abstract usage is appropriate for a Japanese text and reader.

The OSIS Bible markup page in our wiki, https://crosswire.org/wiki/OSIS_Bibles <https://crosswire.org/wiki/OSIS_Bibles>, should be updated if we are going to move it from experimental to supported.

BTW, I fully understand the value in moving 5 Japanese texts from beta to main. I’m not adverse to that forcing the issue.


> On Aug 17, 2017, at 12:42 PM, Peter von Kaehne <refdoc at crosswire.org> wrote:
> For years, decades probably, we have 5 Japanese Bibles in Beta. The
> reason they did not move on was supposed lack of support for Ruby mark
> up. At least in libsword dependent frontends this is now there (and
> probably was for a long time already) - if you want to test it tick the
> glosses module option. 
> Is jsword there too? 
> I will move them out later today into main. It is one embarrassment too
> many....
> Also, as you will have seen, I have now a fairly well and fast working
> setup for module making - at least as far as USFM, OSIS, TEI and IMP is
> concerned. Handcrafted texts still take as long as ever. I think I have
> dealt with any backlog. . I will in the next days and weeks work
> through my stock of long ago submitted stuff, put them into my
> framework and rerun the module import in order to ensure the maximum
> amount of modules has the benefit of the newest toolkits and to ensure
> that all I have ever done for CrossWire is actually somewhere
> semipublic accessible and reproducible. So, if you see some major
> uploads happening, it is probably not worth updating all and everything
> in your own files. 
> Peter
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20170820/e0b4062c/attachment-0001.html>

More information about the sword-devel mailing list