<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The markup is using OSIS in a standard way.<div class="">Here is Matt 1:1 in JapBungo (Indented for ease of reading):</div><div class=""><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><verse osisID='Matt.1.1'></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>アブラハムの</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><w gloss='こ'></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>子</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span></w></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>、ダビデの</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><w gloss='こ'></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>子</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span></w></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>、イエス・キリストの</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><w gloss='けいづ'></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>系圖</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span></w></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>。</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span></verse></div><div class=""><br class=""></div><div class="">By default JSword shows just the base text and not the gloss. アブラハムの子、ダビデの子、イエス・キリストの系圖。</div><div class="">There is no way to show the gloss. So, the release of the module won’t result in a bad user experience, just an incomplete one.</div><div class=""><br class=""></div><div class="">Not sure what the best way to present this in HTML, but perhaps using HTML5 ruby markup, which will be ignored by Bible Desktop, just showing it in a linear fashion:</div><div class=""><br class=""></div><div class="">アブラハムの<ruby><rb>子</rb><rt>こ</rt></ruby>、ダビデの<ruby><rb>子</rb><rt>こ</rt></ruby>、イエス・キリストの<ruby><rb>系圖</rb><rt>けいづ</rt></ruby>。</div><div class=""><br class=""></div><div class="">The above is fine if the browser can show it as interlinear, but is not appropriate for older browsers that cannot. The ruby fall back mechanism <rp> needs to be employed.</div><div class=""><br class=""></div><div class="">アブラハムの<ruby><rb>子</rb><rt><rp>(</rp>こ<rp>)</rp></rt></ruby>、ダビデの<ruby><rb>子</rb><rt><rp>(</rp>こ<rp>)</rp></rt></ruby>、イエス・キリストの<ruby><rb>系圖</rb><rt><rp>(</rp>けいづ<rp>)</rp></rt></ruby>。</div><div class=""><br class=""></div><div class="">Should this be a toggle?</div><div class=""><br class=""></div><div class="">DM</div><div class=""><br class=""></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Aug 20, 2017, at 1:01 PM, DM Smith <<a href="mailto:dmsmith@crosswire.org" class="">dmsmith@crosswire.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">My response on JSword-devel mailing list:<div class="">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.<div class=""><br class=""></div><div class="">The OSIS Bible markup page in our wiki, <a href="https://crosswire.org/wiki/OSIS_Bibles" class="">https://crosswire.org/wiki/OSIS_Bibles</a>, should be updated if we are going to move it from experimental to supported.</div><div class=""><br class=""></div><div class="">BTW, I fully understand the value in moving 5 Japanese texts from beta to main. I’m not adverse to that forcing the issue.</div><div class=""><br class=""></div><div class="">DM</div><div class=""></div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Aug 17, 2017, at 12:42 PM, Peter von Kaehne <<a href="mailto:refdoc@crosswire.org" class="">refdoc@crosswire.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">For years, decades probably, we have 5 Japanese Bibles in Beta. The<br class="">reason they did not move on was supposed lack of support for Ruby mark<br class="">up. At least in libsword dependent frontends this is now there (and<br class="">probably was for a long time already) - if you want to test it tick the<br class="">glosses module option. <br class=""><br class="">Is jsword there too? <br class=""><br class="">I will move them out later today into main. It is one embarrassment too<br class="">many....<br class=""><br class="">Also, as you will have seen, I have now a fairly well and fast working<br class="">setup for module making - at least as far as USFM, OSIS, TEI and IMP is<br class="">concerned. Handcrafted texts still take as long as ever. I think I have<br class="">dealt with any backlog. . I will in the next days and weeks work<br class="">through my stock of long ago submitted stuff, put them into my<br class="">framework and rerun the module import in order to ensure the maximum<br class="">amount of modules has the benefit of the newest toolkits and to ensure<br class="">that all I have ever done for CrossWire is actually somewhere<br class="">semipublic accessible and reproducible. So, if you see some major<br class="">uploads happening, it is probably not worth updating all and everything<br class="">in your own files. <br class=""><br class="">Peter<br class=""><br class="">_______________________________________________<br class="">sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class=""><a href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">Instructions to unsubscribe/change your settings at above page<br class=""></div></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class=""><a href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">Instructions to unsubscribe/change your settings at above page</div></blockquote></div><br class=""></div></body></html>