Re: [sword-devel] Problem with verse range linking osis2mod Windows v3431

2019-01-09 Thread Dudeck, John
Is there any progress being made on this problem?

Do I need to log a bug in the tracker? If so, how/where do I do that?

John


> Hi John,
>
> I think the whole side of OSIS commentaries is a bit unloved and I am
> not surprised to see mistakes.
>
> I have not seen problems on the Bible side. I will look.
>
> As there is no real difference in terms of supposed engine handling of
> either, you can also create a commentary in the encoding of a Bible and
> simply enter a conf entry re module type. This will work fine on all
> frontends of which I know.
>
> But if you discover bugs for commentary specific tags (annotateRef
> being one of them) then these should be reported in the tracker.
>
> Thanks
>
> Peter
>
>
>
> On Sat, 2018-11-24 at 03:28 +, Dudeck, John wrote:
> > Greetings.
> >
> > Here is the pertinent info for reproducing my problem. (You'll have
> > to copy and paste the OSIS source below into an xml file).
> >
> > The text is a snippet of a commentary in French. There is only one
> > article (div), for Romans 1:2-5.
> >
> > I have tested this using osis2mod.exe with and without -z z
> > compression, and with both -s 4 and -s 2, with no change in results.
> >
> > When using the 64-bit osis2mod.exe that is furnished with the current
> > Xiphos, I use this command line (the variables are filled in by a
> > script):
> > "c:\Program Files\Xiphos\bin\osis2mod.exe" %modpath% %srcfile% -s 4
> > -z z -b 3 Segond > %modules%\compilerr.txt 2>&1
> > This does not link verses 3, 4, and 5 to verse 2.
> >
> > When using the 32-bit osis2mod.exe from the older Sword utilities, I
> > use this command line:
> > "c:\Program Files (x86)\CrossWire\sword-utilities\osis2mod.exe"
> > %modpath% %srcfile% -z z -b 3 Segond -s 4 > %modules%\compilerr.txt
> > 2>&1
> > This links verses 3-5 to verse 2 correctly.
> >
> > This is the OSIS source text:
> > =
> > =
> > 
> > http://www.crosswire.org/osis/namespace
> > http://www.crosswire.org/osis/osisCore.2.1.1.xsd; xmlns:xsi="
> > http://www.w3.org/2001/XMLSchema-instance;  xmlns="
> > http://www.bibletechnologies.net/2003/OSIS/namespace;>
> >  > canonical="false">
> > 
> >
> >Romains Commentaire biblique
> >Dickson, Brad
> >Bible. N.T. Romains
> > --Commentaires.
> > > type="Gregorian">2006
> >« C’est le mérite de ce
> > commentaire de Brad Dickson de nous présenter le texte de cette
> > épître d’une manière complète et facile d’accès. » - Alfred KuenTous
> > sont-ils perdus sans Christ ? Comment être transformé à l’image du
> > Christ ? Le salut est-il définitif ? Qu’est-ce que la prédestination
> > ? Dieu a-t-il un projet particulier pour le peuple juif ? Comment
> > vivre l’unité de la foi avec ceux qui ont des opinions différentes
> > des nôtres ?Dans ce commentaire, Brad Dickson donne des outils au
> > lecteur pour comprendre et vivre ce texte central de
> > l’Écriture.
> >Éditions CLÉ
> >fr
> >Copyright 2006
> > Éditions CLÉ
> >
> >
> >Bible
> >
> > 
> > 
> >
> >  > annotateRef="Rom.1.2-Rom.1.5">
> >
> > Parenthèse : l’Évangile
> > (v. )
> >  > ell> cet Évangile, Dieu l’avait promis auparavant
> > par ses prophètes dans les saintes Écritures,  > type="super">3 il concerne son Fils, né de la descendance de
> > David selon la chair, 4 et déclaré Fils de Dieu avec puissance selon
> > l’Esprit de sainteté, par sa résurrection d’entre les morts :
> > 5 Jésus-Christ notre Seigneur. C’est par lui que nous avons reçu la
> > grâce et l’apostolat pour amener, en son nom, à l’obéissance de la
> > foi toutes les nations, …
> > Paul nous communique en toute hâte deux informations concernant
> > l’Évangile. D’abord, son ancienneté, car « Dieu
> > l’avait promis auparavant » et ensuite, son centre d’intérêt car
> > « il concerne son Fils ».
> > L’enracinement de l’Évangile dans les  > type="bold">« saintes Écritures » est capital pour Paul. Il se
> > défend ainsi de créer une nouvelle religion. Il voit dans la personne
> > du Christ l’accomplissement des nombreuses prophéties qu’il citera
> > tout au long de l’épître. Sûrement a-t-il été accusé d’avoir
> > « inventé » sa bonne nouvelle.
> > L’épicentre de la bonne nouvelle n’est pas un dogme,
> > mais une personne, Jésus-Christ. Nous ferions tous bien de nous le
> > rappeler, sinon, notre foi risquerait fort de manquer de la joie qui
> > découle de la relation vivante à Dieu, relation trouvée en Christ
> > seul. Les remarques capitales qui suivent présentent la double nature
> > de cet homme/Dieu ; elles constituent le noyau dur de la bonne
> > nouvelle de Dieu. Il est deux fois « Fils ». Il
> > l’est d’abord « de David », un titre déjà
> > présent dans l’Ancien Testament () et signifiant le Messie, 

Re: [sword-devel] Text and module development on CrossWire

2019-01-09 Thread Matěj Cepl
On 2019-01-09, 14:53 GMT, David Haslam wrote:
> It’s unlikely that moving a repo from GitLab to CrossWire’s 
> GitLab will preserve all the useful information.

Gitlab has supported functionality for import from another 
GitLab instance including (of course) https://gitlab.com. When 
I try to use it though (http://git.crosswire.org/projects/new 
click on ImportProject and Gitlab.com) I get error message:

To enable importing projects from GitLab.com, ask your 
GitLab administrator to configure OAuth integration 
(http://git.crosswire.org/help/integration/gitlab).

(BTW, why don't we have https:// there, with LetsEncrypt it 
should be easy to get SSL certificate; it really is unconscious 
to communicate potentially secret information over unecnrypted 
Internet connections).

Could we get this integration switched on, if it is reasonably 
uncomplicated?

Blessings,

Matěj
-- 
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
Science is meaningless because it gives no answer to our
question, the only question important to us: ``What shall we do
and how shall we live?''
-- Lev Nikolaevich Tolstoy


___
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] Text and module development on CrossWire

2019-01-09 Thread Greg Hellings
On Wed, Jan 9, 2019 at 9:32 AM Peter von Kaehne  wrote:

> On Wed, 2019-01-09 at 14:53 +, David Haslam wrote:
>
> > Not sure if this was the wisest structure for what we are doing
> > here.
>
> No, possibly not. You start with one thing and then change it about
> until it fits. I have also created several other repos to which others
> only have access.
>

If there is one repo per module, then it would become relatively simple to
create automation to build and release modules into an alpha repository (or
even have one-repo-per-module for an alpha build) that regenerates
automatically every time the module's repository is pushed to. It also
gives the easiest way to have access control on a per-module basis, giving
one user ownership over their module without needing to have access to a
shared repository. A shared repo for something that can potentially have so
many owners can lead to a narrower bottleneck as you would have to approve
every PR/MR for any module.

--Greg


>
> ___
> 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] Text and module development on CrossWire

2019-01-09 Thread Peter von Kaehne
On Wed, 2019-01-09 at 14:53 +, David Haslam wrote:

> Not sure if this was the wisest structure for what we are doing
> here. 

No, possibly not. You start with one thing and then change it about
until it fits. I have also created several other repos to which others
only have access. 

___
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] Text and module development on CrossWire

2019-01-09 Thread David Haslam
It’s unlikely that moving a repo from GitLab to CrossWire’s GitLab will 
preserve all the useful information.

Also note that Peter created a single repository for TextDevelopment rather 
than a separate repository for each Text.

There are now (at least) five different works in the repo.

Not sure if this was the wisest structure for what we are doing here.

Regards,

David

Sent from ProtonMail Mobile

On Wed, Jan 9, 2019 at 13:12, Peter von Kaehne  wrote:

> On Wed, 2019-01-09 at 12:20 +0100, Matěj Cepl wrote:
>>
>> If I am granted access, I will immediately move all my
>> repositories from gitlab.com there.
>
> You got access. Please do not move Bible texts which are in the public
> domain and would benefit from wider collaboration (i.e. beyond
> CrossWire folk). Gitlab/Github exposure will do us only good. Also we
> want to keep our own backup needs to the minimum.
>
> But texts for which you want to have easy access to CrossWire wide help
> while needing to keep them otherwise under wraps and restricted access
> - our Gitlab is the right place for that.
>
> And of course it is the right place for all kinds of module related
> scripts etc.
>
> Yours
>
> 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] Text and module development on CrossWire

2019-01-09 Thread Tuomas Airaksinen
Hi,

For FinRK module, Crosswire has rights to publish in any digital form,
including OSIS xml. I would like to push my source XML git repository to
Crosswire's gitlab.

Best regards,
Tuomas


ti 8. tammik. 2019 klo 20.12 Peter von Kaehne (ref...@crosswire.org)
kirjoitti:

> Dear All,
>
> we have now a fairly sophisticated GitLab instance installed on
> CrossWire and I have started installing all kinds of projects there
> which had been lying fallow in parts. I also have invited several of
> you as contributors and developers there and will invite more as it
> becomes obvious and necessary.
>
> Yours
>
> 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
>


-- 
T: Tuomas
___
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] Text and module development on CrossWire

2019-01-09 Thread Cyrille
I can do the same with the Kikongo and Lingala, but how to do it without
lost of infos (the issues in my case)?

Il 09/01/2019 12:20, Matěj Cepl ha scritto:
> On 2019-01-08, 18:11 GMT, Peter von Kaehne wrote:
>> we have now a fairly sophisticated GitLab instance installed 
>> on CrossWire and I have started installing all kinds of 
>> projects there which had been lying fallow in parts. I also 
>> have invited several of you as contributors and developers 
>> there and will invite more as it becomes obvious and 
>> necessary.
> If I am granted access, I will immediately move all my 
> repositories from gitlab.com there.
>
> Matěj



___
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] Text and module development on CrossWire

2019-01-09 Thread Peter von Kaehne
On Wed, 2019-01-09 at 12:20 +0100, Matěj Cepl wrote:
> 
> If I am granted access, I will immediately move all my 
> repositories from gitlab.com there.

You got access. Please do not move Bible texts which are in the public
domain and would benefit from wider collaboration (i.e. beyond
CrossWire folk). Gitlab/Github exposure will do us only good. Also we
want to keep our own backup needs to the minimum. 

But texts for which you want to have easy access to CrossWire wide help
while needing to keep them otherwise under wraps and restricted access
- our Gitlab is the right place for that. 

And of course it is the right place for all kinds of module related
scripts etc. 

Yours

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] Text and module development on CrossWire

2019-01-09 Thread Matěj Cepl
On 2019-01-08, 18:11 GMT, Peter von Kaehne wrote:
> we have now a fairly sophisticated GitLab instance installed 
> on CrossWire and I have started installing all kinds of 
> projects there which had been lying fallow in parts. I also 
> have invited several of you as contributors and developers 
> there and will invite more as it becomes obvious and 
> necessary.

If I am granted access, I will immediately move all my 
repositories from gitlab.com there.

Matěj
-- 
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
Less is more or less more.
   -- Y_Plentyn on #LinuxGER
  (from fortunes -- I cannot resist :-)


___
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] Text and module development on CrossWire

2019-01-09 Thread ref...@gmx.net
DoneSent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [sword-devel] Text and module development on CrossWireFrom: Dominique Corbex To: sword-devel@crosswire.orgCC: Dear Peter,I'd be glad if you could grant me access to the Gitlab instance onCrosswire, I'd like to upload scripts I have written to buildseveral French modules and are in serious need of maintenance.In Christ,+DomOn Tue, 08 Jan 2019 18:11:19 +Peter von Kaehne  wrote:> we have now a fairly sophisticated GitLab instance installed on> CrossWire and I have started installing all kinds of projects there> which had been lying fallow in parts. I also have invited several of> you as contributors and developers there and will invite more as it> becomes obvious and necessary-- domcox ___sword-devel mailing list: sword-devel@crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-develInstructions 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] Text and module development on CrossWire

2019-01-09 Thread Dominique Corbex
Dear Peter,

I'd be glad if you could grant me access to the Gitlab instance on
Crosswire, I'd like to upload scripts I have written to build
several French modules and are in serious need of maintenance.

In Christ,
+Dom

On Tue, 08 Jan 2019 18:11:19 +
Peter von Kaehne  wrote:

> we have now a fairly sophisticated GitLab instance installed on
> CrossWire and I have started installing all kinds of projects there
> which had been lying fallow in parts. I also have invited several of
> you as contributors and developers there and will invite more as it
> becomes obvious and necessary

-- 
domcox 

___
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