Le 05/01/2018 à 00:34, Peter von Kaehne a écrit :
> So, for text development, I suggest continue to use Gitlab, Github etc
> or simply your private arrangements. Any finalised OSIS etc is stored
> safely on CW's server until superseded.
Do you think it would be possible to create a common reposi
Hello,
Le 04/01/2018 à 15:49, Troy A. Griffitts a écrit :
> We've had a process to create an LXXM module from this source for
> quite some time. It can be created from this script in the sword-tools
> repo:
>
> http://crosswire.org/svn/sword-tools/trunk/modules/lxxm/convert.sh
>
Ok I download it
Le 05/01/2018 à 00:34, Peter von Kaehne a écrit :
>
> So, for text development, I suggest continue to use Gitlab, Github etc
> or simply your private arrangements. Any finalised OSIS etc is stored
> safely on CW's server until superseded.
Do you think it would be possible to create a common repo
Dear All,
This is to announce that we have just now uploaded LinVB.
This is is an updated version of LinVB.
Many thanks to Fr for the hard work.
yours
The Module Team
P.S.: This email is sent automatically on upload of a new/updated module
___
sword-d
Hi Matej,
We have an internal store which is not shared other than the current
module team. This is not a repo - we do not do much text development,
but simply the last source text at any given time, so that we can
rapidly reissue a module based on the same text if there are module
making script e
Just a reminder, following my last reply to Fr Cyrille.
Some of us have "two hats" that we wear at different times.
- At times we are acting as volunteers for CrossWire Bible Society
- At times we are voluntary collaborators in text development with
non-CrossWire agents
I doubt that I'm the onl
There's an important distinction between not maintaining a revision controlled
source text and having copies of a source text to process at a particular point
in time.
There's also a difference between what gets officially stored on the CrossWire
server and what gets stored unofficially by any
Le 04/01/2018 à 18:09, David Haslam a écrit :
> Everyone - please understand that CrossWire does *not* maintain the
> source text files for any SWORD modules apart from the flagship *KJV*
> and *KJVA* modules.
Ok it is clear, but what you do with texts send by people for the module
creation (Exam
Everyone - please understand that CrossWire does not maintain the source text
files for any SWORD modules apart from the flagship KJV and KJVA modules.
All other module updates depend on someone starting again from the most recent
source text files provided by third parties.
This is why there a
Le 04/01/2018 à 12:17, Peter Von Kaehne a écrit :
>> Von: Cyrille
> I would like to react to this message, I hope that I will not hurt
>> anyone, if my remarks are too direct, be indulgent knowing that English
>> is not my native language.
> No worries whatsoever, Cyrille, English is also not m
On 2018-01-04, 09:08 GMT, Cyrille wrote:
> Afterwards, I would like to add my point of view regarding
> Catholic modules. I deplore the lack of initiative on the part
> of Catholics (I am, so I do not accuse anyone from outside),
> the obstinacy to keep the rights and the refusal to freely
> sp
On 2018-01-04, 10:53 GMT, Peter Von Kaehne wrote:
> Wrt the wider question of keeping source files for
> collaborative work - we do keep source about, since I started
> doing the module uploads, so currently we hold teh source for
> about 80 or so modules.
How can I get access to this shared re
We've had a process to create an LXXM module from this source for quite some
time. It can be created from this script in the sword-tools repo:
http://crosswire.org/svn/sword-tools/trunk/modules/lxxm/convert.sh
The issue we had at the time was the CCAT license which basically required
every use
Here is the best source I could find
http://ccat.sas.upenn.edu/gopher/text/religion/biblical/lxxmorph/01.Gen.1.mlxx
> Gesendet: Donnerstag, 04. Januar 2018 um 10:53 Uhr
> Von: "Peter Von Kaehne"
> An: sword-devel@crosswire.org
> Betreff: Re: [sword-devel] New LXX module
>
> Von: Cyrille
>
>
> Von: Cyrille
I would like to react to this message, I hope that I will not hurt
> anyone, if my remarks are too direct, be indulgent knowing that English
> is not my native language.
No worries whatsoever, Cyrille, English is also not my first language either.
Many of us are using it solely
Von: Cyrille
> Hello,
> Currently the LXX module use the default versification not the lxx! :)
> What to do?
I think our LXX module is ancient and derived from an old OLB module at a time
when we neither had alternative versifications nor the convictions we have now
regarding going always back
Hello,
Why the canon_LXX.h have the new testament books versification?
Le 04/01/2018 à 10:26, Cyrille a écrit :
> Hello,
> Currently the LXX module use the default versification not the lxx! :)
> What to do?
>
> Le 04/01/2018 à 09:29, Cyrille a écrit :
>>
>>
>>
>> Le 03/01/2018 à 22:40, David Hasl
Hello,
Currently the LXX module use the default versification not the lxx! :)
What to do?
Le 04/01/2018 à 09:29, Cyrille a écrit :
>
>
>
> Le 03/01/2018 à 22:40, David Haslam a écrit :
>> Actually, Cyrille, your having the OSIS XML file for the existing
>> *LXX* is not strictly a necessity.
>>
>>
Hello,
I would like to react to this message, I hope that I will not hurt
anyone, if my remarks are too direct, be indulgent knowing that English
is not my native language.
First, I thank each and every one of you for the wonderful work you have
done for all Bible readers and Christians in particul
Le 03/01/2018 à 22:40, David Haslam a écrit :
> Actually, Cyrille, your having the OSIS XML file for the existing
> *LXX* is not strictly a necessity.
>
> *osis2mod* has a command line switch *-a* that enables an existing
> module to be *augmented*.
Ok! This is really interesting.
>
> All you n
Greetings Sword devs,
I've put a little elbow grease into the CMake build scripts to bring the
"make tests" option there up to snuff. The current heads of both trunk and
sword-1-8-x should be able to run the tests/testsuite/runall.sh option with
a CMake build now. This is all nicely packaged with
21 matches
Mail list logo
