Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread Karl Kleinpaste 
On 02/06/2016 05:19 AM, David Haslam wrote:
> Would it be too much to ask that colophon text be rendered in a smaller font
> size than the main text?
...iff it's done using a relative font size indicator.
___
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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread DM Smith 
The osis2mod program has changed the … to the milestoned version. It 
shouldn’t do that for type=“colophon”.

— DM

> On Feb 6, 2016, at 10:54 AM, Peter von Kaehne  wrote:
> 
> On Fri, 2016-02-05 at 12:50 -0500, DM Smith wrote:
>> Thanks! I did a quick read of the source looking for other problems.
>> Not seeing anything obvious.
>> 
>> While you have the patient open, would you also add support for > type=“colophon”> to at least put it on a next line? Outputting it as
>> a  would be one way to do this.
>> 
> 
> One problem here (including with David's request re different font
> size) is that the colophons are not encoded as I would expect them
> 
> bla bla 
> 
> but are milestoned. I do not think this is correct.
> 
> They feed through ok and I will commit later today a change which will
> change their "type" attribute to a "class" attribute.
> 
> Peter
> 
> 
> ___
> 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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread Peter von Kaehne 
On Sat, 2016-02-06 at 11:11 -0500, DM Smith wrote:
> The osis2mod program has changed the … to the milestoned
> version. It shouldn’t do that for type=“colophon”.

Ok, I have committed support for non-milestoned colophon divs to appear
as "class=colophon". Also committed changes to rdg, catchWord and
transChange. 

the transchange type is availble as a type attribute in the XHTML
 tag, but I have not done any styling with it. It is simply
silently there. 

I have also added a linefeed for milestoned colophone divs. 

regarding David's request for a different font size, something goes
wrong when I try this. The subsequent text is all suddenly small. So I
left that. I hope I have not broken anything. 

Peter

___
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] Types of notes

2016-02-06 Thread Peter von Kaehne 
The OSIS manual describes a long list of possible forms notes may
take. 

We routinely throw this info away and only keep xrefs and "notes". I
think we might be able to create/present more multilayered modules if
we were able to extract more info out of the notes. The following note
types are allowed in OSIS:

 * allusion The note explains an implicit reference the text makes to another 
text or concept.
 * alternative The note records an alternate possible reading of the text, 
whether due to ambiguity in
 * translation or to manuscript variation. This type of note will almost always 
include an  element.
 * background The note provides background information, such as cultural norms, 
explanations of geographic or other information original readers would have 
known, and so on.
 * citation The note cites a supporting text or further explanation of some 
kind.
 * crossReference The note provides a cross-reference to a related passage or 
other text.
 * devotional The note includes information of interest for devotional reading.
 * exegesis The note discusses a relevant point of exegesis or interpretation
 * explanation The note explains implicit, ambiguous, or otherwise non-obvious 
aspects of the passage.
 * speaker This type is intended mainly for use in sermons and other 
performance texts, where the performer may wish to make notes to him or 
herself. For example, "tell joke here".
 * study The note provides helps for a deeper study of the passage.
 * translation The note discusses an issue of translation, such as a
   word whose meaning is unclear in the original, or a reasons for the
   translator's choice of phrasing. Bible translation projects will
   likely use this heavily, using the subtype attribute to mark the
   status of each note as resolved or unresolved, the person
   responsible for the note, and so on. 
 * variant The note records a textual variation among source
   manuscripts. This will also often include an  element

The way we pass a note to the frontend currently is by passing a
complicated URL with various info on the note. 

Among this is a single character "x" or "n", where x stands for xref
and n for the whole rest. I propose to use the many variants and pass
on different characters for each of the kind of notes in existence.
This could then be read and acted upon by frontends. 

There would be some breakage in frontends if a frontend wants to
continue handling all notes but xrefs in one way but explicitly expects
an "n" being passed. This should be easily remedied.

I could implement this quite fast, I think, but would like to have your
thoughts +/- agreement.

In an sense this is continuation of my "styling" and "classifying"
work.

Peter

___
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

Re: [sword-devel] Types of notes

2016-02-06 Thread DM Smith 
Because SWORD recognizes study and crossReference, the KJV uses study, when it 
probably should be using alternative or translation instead. At this time it 
does not have xref notes.

Also, many notes in OSIS modules (e.g. ESV) have the n attribute which gives 
the footnote marker that the publisher uses.

Soon the KJV will have them. Interestingly, the original text uses a dagger 
(for translation notes), an 8 pointed star (for Psalm notes), a double vertical 
bar (for alternative notes) or letters (for cross-references and here and there 
for other notes).

(Aside: JSword uses them or manufactures the equivalent a-z, or 1-n within the 
context of what is displayed.)


> On Feb 6, 2016, at 12:47 PM, Peter von Kaehne  wrote:
> 
> The OSIS manual describes a long list of possible forms notes may
> take. 
> 
> We routinely throw this info away and only keep xrefs and "notes". I
> think we might be able to create/present more multilayered modules if
> we were able to extract more info out of the notes. The following note
> types are allowed in OSIS:
> 
> * allusion The note explains an implicit reference the text makes to another 
> text or concept.
> * alternative The note records an alternate possible reading of the text, 
> whether due to ambiguity in
> * translation or to manuscript variation. This type of note will almost 
> always include an  element.
> * background The note provides background information, such as cultural 
> norms, explanations of geographic or other information original readers would 
> have known, and so on.
> * citation The note cites a supporting text or further explanation of some 
> kind.
> * crossReference The note provides a cross-reference to a related passage or 
> other text.
> * devotional The note includes information of interest for devotional reading.
> * exegesis The note discusses a relevant point of exegesis or interpretation
> * explanation The note explains implicit, ambiguous, or otherwise non-obvious 
> aspects of the passage.
> * speaker This type is intended mainly for use in sermons and other 
> performance texts, where the performer may wish to make notes to him or 
> herself. For example, "tell joke here".
> * study The note provides helps for a deeper study of the passage.
> * translation The note discusses an issue of translation, such as a
>   word whose meaning is unclear in the original, or a reasons for the
>   translator's choice of phrasing. Bible translation projects will
>   likely use this heavily, using the subtype attribute to mark the
>   status of each note as resolved or unresolved, the person
>   responsible for the note, and so on. 
> * variant The note records a textual variation among source
>   manuscripts. This will also often include an  element
> 
> The way we pass a note to the frontend currently is by passing a
> complicated URL with various info on the note. 
> 
> Among this is a single character "x" or "n", where x stands for xref
> and n for the whole rest. I propose to use the many variants and pass
> on different characters for each of the kind of notes in existence.
> This could then be read and acted upon by frontends. 
> 
> There would be some breakage in frontends if a frontend wants to
> continue handling all notes but xrefs in one way but explicitly expects
> an "n" being passed. This should be easily remedied.
> 
> I could implement this quite fast, I think, but would like to have your
> thoughts +/- agreement.
> 
> In an sense this is continuation of my "styling" and "classifying"
> work.
> 
> Peter
> 
> ___
> 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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread Peter von Kaehne 
On Fri, 2016-02-05 at 12:50 -0500, DM Smith wrote:
> Thanks! I did a quick read of the source looking for other problems.
> Not seeing anything obvious.
> 
> While you have the patient open, would you also add support for  type=“colophon”> to at least put it on a next line? Outputting it as
> a  would be one way to do this.
> 

One problem here (including with David's request re different font
size) is that the colophons are not encoded as I would expect them

bla bla 

but are milestoned. I do not think this is correct.

They feed through ok and I will commit later today a change which will
change their "type" attribute to a "class" attribute.

Peter


___
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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread Peter von Kaehne 
On Sat, 2016-02-06 at 11:18 -0500, DM Smith wrote:
> 
> BTW, which render does Xiphos use, osishtmlhref or osisxhtml?

osisxhtml

___
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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread DM Smith 
Hey, I learned something new! May be old news to others or all.

CSS allows styling based on any attribute. 
(http://www.w3schools.com/css/css_attribute_selectors.asp 
)
So
.transChange[type=“added"] {…} will style added stuff

In Him,
DM

> On Feb 6, 2016, at 11:39 AM, Peter von Kaehne  wrote:
> 
> On Sat, 2016-02-06 at 11:11 -0500, DM Smith wrote:
>> The osis2mod program has changed the … to the milestoned
>> version. It shouldn’t do that for type=“colophon”.
> 
> Ok, I have committed support for non-milestoned colophon divs to appear
> as "class=colophon". Also committed changes to rdg, catchWord and
> transChange. 
> 
> the transchange type is availble as a type attribute in the XHTML
>  tag, but I have not done any styling with it. It is simply
> silently there. 
> 
> I have also added a linefeed for milestoned colophone divs. 
> 
> regarding David's request for a different font size, something goes
> wrong when I try this. The subsequent text is all suddenly small. So I
> left that. I hope I have not broken anything. 
> 
> Peter
> 
> ___
> 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] osis2mod changes

2016-02-06 Thread DM Smith 
I’ve just updated osis2mod to do 2 things:
1) leave … alone. That is don’t change the divs to 
milestones.
2) look for entities that shouldn’t be in a module and report them. While 
numeric entities are allowed in xml, SWORD does not convert these to their text 
value. At a later date, we can change osis2mod to convert them to their text 
value.

Now to document the change in the wiki…

In Him,
DM


___
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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread DM Smith 

> On Feb 6, 2016, at 10:02 AM, Karl Kleinpaste  wrote:
> 
> On 02/06/2016 05:19 AM, David Haslam wrote:
>> Would it be too much to ask that colophon text be rendered in a smaller font
>> size than the main text?
> ...iff it's done using a relative font size indicator.

Shouldn’t it be handled in osisxhtml as a class value?

BTW, which render does Xiphos use, osishtmlhref or osisxhtml?

— DM

___
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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread Karl Kleinpaste 
On 02/06/2016 11:18 AM, DM Smith wrote:
> which render does Xiphos use, osishtmlhref or osisxhtml?
Xiphos moved to osisxhtml in 2013.
___
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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread Greg Hellings 
On Sat, Feb 6, 2016 at 10:39 AM, Peter von Kaehne  wrote:
> On Sat, 2016-02-06 at 11:11 -0500, DM Smith wrote:
>> The osis2mod program has changed the … to the milestoned
>> version. It shouldn’t do that for type=“colophon”.
>
> Ok, I have committed support for non-milestoned colophon divs to appear
> as "class=colophon". Also committed changes to rdg, catchWord and
> transChange.
>
> the transchange type is availble as a type attribute in the XHTML
>  tag, but I have not done any styling with it. It is simply
> silently there.
>
> I have also added a linefeed for milestoned colophone divs.

I'm not sure we should be outputting milestoned and non-milestoned
divs differently. Seems like they should both operate the same way.

--Greg

>
> regarding David's request for a different font size, something goes
> wrong when I try this. The subsequent text is all suddenly small. So I
> left that. I hope I have not broken anything.
>
> Peter
>
> ___
> 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

Re: [sword-devel] diatheke missing bibletext.cls and sword.sty

2016-02-06 Thread Peter von Kaehne 
On Fri, 2016-02-05 at 17:14 -0800, Brian Jolly wrote:
> 
> Peter, thanks for your work on the filters. Are any of the LaTeX
> support files shareable even outside of SVN? 
> 

This is what i have started. My main aim so far was to make the
crossreferences work in a PDF. I have not put much effort into making
things look nice.

As you see there are a whole bunch of tags which are commented still.

I think I will do away with the call for sword.sty in the Diatheke.

I had hoped to have a latex subdirectory in /sword but Troy is not
keen. So this needs to go somewhere else. 

Peter\LoadClass[11pt,a4paper,twoside,headinclude=true,footinclude=true,BCOR=0mm,DIV=calc]{scrbook}
\NeedsTeXFormat{LaTeX2e}
\ProvidesClass{sword}[2015/03/29 CrossWire LaTeX class for Biblical texts]
\RequirePackage[perpage, para]{footmisc}
\RequirePackage{fancyhdr}
\pagestyle{fancy}
\RequirePackage[verbose,
  colorlinks=true,
  naturalnames=true,
  linkcolor=blue,]{hyperref}

\RequirePackage{polyglossia}


\newcommand{\swordchapter}[3]{\hypertarget{#1}{\small{#3} }}
\newcommand{\swordverse}[3]{\hypertarget{#1}{\small{#3} }}
\newcommand{\swordxref}[2]{\hyperlink{#1}{#2}}
\newcommand{\swordfootnote}[6]{\footnote{#6}}
\newcommand{\swordpoetryline}[1]{#1}
\newcommand{\sworddivinename}[1]{\textsc{#1}}
\newcommand{\swordmodule}{}
\newcommand{\swordtestament}{\part*}
\newcommand{\swordbook}{\chapter*}
%\sworddiclink{%s}{%s}{
%\sworddictref{%s}{%s}{
%\sworddict{%s}{

%\newcommand{\sworddivinename}{%s}{



%\swordfont{

%\swordfootnote{%s}{%s}{%s}{
%\swordfootnote{%s}{%s}{%s}{%s}{
%\swordmorph{
%\swordmorph[Greek]{%s}
%\swordmorph[lemma]{%s}
%\swordmorph{%s}
%\swordquote{
%\swordref{%s}{%s}{
%\swordsection{
%\swordsection{}{
%\swordsection{book}{
%\swordsection{sechead}{
%\swordstrong[Greek]{
%\swordstrong[Greektense]{
%\swordstrong[Hebrew]{
%\swordstrong[Hebrewtense]{
%\swordstrong[%s]{%s}{
%\swordstrong{%s}{%s}
\newcommand{\swordtitle}[3]{\textbf{#3}}
%\swordtranschange{supplied}{
%\swordtranschange{tense}{
%\swordwoj{
%\swordxref{
%\swordxref{%s}{%s}{
___
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

Re: [sword-devel] diatheke missing bibletext.cls and sword.sty

2016-02-06 Thread Peter von Kaehne 
Latex is used to produce scholarly editions with heavy apparatus, so i would 
dispute what you say re inability to achieve a good output

Sent from my phone. Apologies for brevity and typos.On 6 Feb 2016 5:39 am, 
Michael H  wrote:
>
> Brian, 
>
> You'll run into issues trying to build a Bible in Latex. Simon Cozens did, 
> and decided to fix it. Resulting in Sile. (That's a stretch and mangled 
> history, but theres a bit of truth in there.) 
>
> Sile is free and open source and is designed to produce printed books, with 
> Bibles in mind.
>
> https://www.youtube.com/watch?v=t_kk20vlamo
>
> It's also much younger and in active development.
>
> https://github.com/simoncozens/sile/
>
> Latex might produce a King James (text only, not references.. xrefs etc.) You 
> won't be very happy with it.  Sile can handle KJV with greek glossed in. 
> Mostly.  If you have time. 
>
> On Fri, Feb 5, 2016 at 7:14 PM, Brian Jolly  wrote:
>>
>> Thanks Guys,
>>
>> I am really trying to stick with the free and open set of tools 
>> (sword/diatheke/LaTeX).
>>
>> Peter, thanks for your work on the filters. Are any of the LaTeX support 
>> files shareable even outside of SVN? 
>>
>> Feel free to contact me off list if that's more appropriate. 
>>
>>
>> On Fri, Feb 5, 2016 at 12:17 AM, David Haslam  wrote:
>>>
>>> If you have the OSIS XML source file, why not use Prince XML to create the
>>> PDF for printing a Bible?
>>>
>>> Or do you only have the module and not the source text?
>>>
>>> http://www.princexml.com/
>>>
>>> Although the first page mentions HTML, the samples page gives an example for
>>> OSIS.
>>> http://www.princexml.com/samples/
>>>
>>> http://www.princexml.com/samples/titus.pdf
>>>
>>> It's all done using CSS for page layout and formating.
>>>
>>> btw. There was a companion program called Princess XML in 2010.
>>> https://code.google.com/archive/p/princess-2010/
>>>
>>> It's for Windows - so less interest for folk such as Peter.
>>> It's not been migrated to GitHub.
>>>
>>> Princess was developed at SIL by Jim Albright.
>>>
>>> Best regards,
>>>
>>> David
>>>
>>>
>>>
>>> --
>>> View this message in context: 
>>> http://sword-dev.350566.n4.nabble.com/diatheke-missing-bibletext-cls-and-sword-sty-tp4655990p4655992.html
>>> Sent from the SWORD Dev mailing list archive at 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

Re: [sword-devel] transChange within a rdg element

2016-02-06 Thread David Haslam 
Would it be too much to ask that colophon text be rendered in a smaller font
size than the main text?

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/transChange-within-a-rdg-element-tp4655995p4656006.html
Sent from the SWORD Dev mailing list archive at 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