I'm not particularly concerned with the rendering, but since we added it for the NASB (and before we started 'class'ifying our HTML output) I simply used the same rendering they use. A reader of the NASB would be used to it. It is explained in their preamble (and here, search for 'asterisk'):
http://www.lockman.org/nasb/nasbprin.php Again, I don't care much about the rendering, but I'm mostly concerned with a regression of losing distinction. I simply deferred the rendering choice to the print publisher of the only SWORD module I know which contains a tenseChange. Thanks for sending the CSS. I had no idea how to render this with CSS. Troy On 02/08/2016 11:36 AM, DM Smith wrote: > Troy, > > Is it important to prefix with an asterisk or can some other markup be used? > > There is nothing in the conf or on the page that would indicate what the * > would mean. As it is, it looks like a dangling footnote marker. > > In Him, > DM > >> On Feb 8, 2016, at 1:16 PM, Troy A. Griffitts <scr...@crosswire.org> wrote: >> >> Here is an example of the transChange in the NASB. While looking this >> up, I noticed the previous verse has formatting differences with old and >> new version of the proposed NASB. I am not sure where we are not, but >> if we want to check where we are now, I would suggest we publish the >> absolute latest version on swordweb and build a list of parallel links >> to verses which demonstrate challenging markup, like the link below: >> >> http://crosswire.org/study/parallelstudy.jsp?add=NASB&add=NASBnew&key=Mat.2.18#cv >> >> >> I don't know which converted was used over the years to produce "NASB" >> and "NASBnew" but new is obviously work than the previous version in >> verse 18. Verse 19 shows the transChange '*'. >> >> Troy >> >> >> >> On 02/08/2016 10:40 AM, Troy A. Griffitts wrote: >>> Hey guys. The tenseChange to add a '*' was part of the NASB source >>> updates. The NASB renders tenseChange with a '*' next to the verb. >>> Typically in the Gospels, when the author is storytelling, they >>> frequently switch to the present tense (we do this in English too when >>> tell stories, e.g., "so I go into the store, and the clerk gives me a >>> winning lottery ticket and asks me to cash it and he only asks me for >>> 40% of the gross winnings. It turns out, after taxes, that's ALL the >>> winnings!"). The NASB and most all other English translations, change >>> the verbs to past tense. The NASB at least marks the verbs with an '*' >>> to show they changed the tense to read more formally. >>> >>> I realize we prefer not to use an '*' directly in the filter, but >>> instead CSS to let the frontends decide how they wish to render these, >>> but removing the '*' without providing proper CSS to insert an '*' or >>> some other default rendering is a backwards step, and one specifically >>> affecting the release of the NASB. >>> >>> Troy >>> >>> >>> On 02/05/2016 10:32 AM, Peter Von Kaehne wrote: >>>> is this in svn head? Or simply a release? >>>> >>>> Peter >>>> >>>> *Gesendet:* Freitag, 05. Februar 2016 um 17:10 Uhr >>>> *Von:* "DM Smith" <dmsm...@crosswire.org> >>>> *An:* "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org> >>>> *Betreff:* Re: [sword-devel] transChange within a rdg element >>>> At this point the code (osisxhtml) says: >>>> if ((type == "added") || (type == "supplied")) >>>> outText("<span class=\"transChangeSupplied\">", buf, u); >>>> else if (type == "tenseChange") >>>> buf += "*"; >>>> >>>> Note: supplied is not a valid value for transChange and probably >>>> represents an earlier OSIS text. >>>> >>>> It really bother’s me that tenseChange is given with mark down. And that >>>> none of the other transChange type attributes are passed as class values. >>>> >>>> Here is how it handles catchWord and rdg. >>>> // <catchWord> & <rdg> tags (italicize) >>>> else if (!strcmp(tag.getName(), "rdg") || !strcmp(tag.getName(), >>>> "catchWord")) { >>>> if ((!tag.isEndTag()) && (!tag.isEmpty())) { >>>> outText("<i>", buf, u); >>>> } >>>> else if (tag.isEndTag()) { >>>> outText("</i>", buf, u); >>>> } >>>> } >>>> >>>> This is not good. Probably should have been <span class=“…”> And catch >>>> word should be styled as bold. >>>> >>>> DM >>>> >>>> >>>> On Feb 5, 2016, at 11:52 AM, Greg Hellings <greg.helli...@gmail.com> >>>> wrote: >>>> >>>> At this point, I believe that SWORD hands off styling like that to the >>>> app to do with CSS (for those apps using HTML output). Does it not? I >>>> don't thin it's using <i> or <em>, although I could be wrong. >>>> >>>> --Greg >>>> >>>> On Fri, Feb 5, 2016 at 10:26 AM, David Haslam >>>> <dfh...@googlemail.com> wrote: >>>> >>>> Something that DM and I have mooted. >>>> >>>> When transChange is used within a rdg element (i.e. inside a >>>> note), and >>>> since SWORD renders text within a rdg as italics, then the text >>>> within the >>>> transChange ought ideally to be rendered as normal type in order >>>> to maintain >>>> the contrast with the other text that's in italics. >>>> >>>> If not already done, please could this be patched in the SWORD >>>> source code. >>>> >>>> DM will implement it in JSword. >>>> >>>> Best regards, >>>> >>>> David >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> >>>> http://sword-dev.350566.n4.nabble.com/transChange-within-a-rdg-element-tp4655995.html >>>> Sent from the SWORD Dev mailing list archive at Nabble.com >>>> <http://nabble.com>. >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel@crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel@crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>>> _______________________________________________ sword-devel mailing >>>> list: sword-devel@crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to >>>> unsubscribe/change your settings at above page >>>> >>>> >>>> _______________________________________________ >>>> sword-devel mailing list: sword-devel@crosswire.org >>>> http://www.crosswire.org/mailman/listinfo/sword-devel >>>> Instructions to unsubscribe/change your settings at above page >>>> >>> >>> _______________________________________________ >>> sword-devel mailing list: sword-devel@crosswire.org >>> http://www.crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >>> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page