Re: [sword-devel] Packaging Ezra Bible App for Snap and Flatpak users?

2024-01-20 Thread Aaron Rainbolt
On Sat, Jan 20, 2024 at 4:27 PM Matěj Cepl  wrote:
>
> On Sat Jan 20, 2024 at 7:18 PM CET, Aaron Rainbolt wrote:
> > It appears that the Ezra Bible App can only be installed using
> > upstream packages for a select group of popular Linux distributions
> > currently. It would be handy for users to be able to install it by
> > using widely available repositories such as the Snap Store and
> > Flathub. I'm fairly skilled at software packaging for distros (though
> > I haven't done Snap or Flatpak before - I'm interested in learning how
> > though) and am thinking about trying to make Snap and Flatpak packages
> > for Ezra Bible App.
>
> Given that Snap really works only on Ubuntu (AFAIK, certainly it
> does work neither with Fedora nor with openSUSE), then I would
> hugely prefer Flatpak.

No clue about openSUSE, but I know Snap works on Debian and I thought
for sure it worked on Fedora (though of course you'd have to install
snapd first, whereas it's preinstalled on Ubuntu). But still, I do
intend on doing both Snap and Flatpak - each has a user base that the
other one doesn't. I'll go ahead and do the Flatpak first since I now
know someone wants a Flatpak for it :)

Thanks for letting me know, and God bless.

> Best,
>
> Matěj
>
> --
> http://matej.ceplovi.cz/blog/, @mcepl@floss.social
> GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
>
> All men's miseries derive from not being able to sit in a quiet
> room alone.
>   -- Blaise Pascal
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] Packaging Ezra Bible App for Snap and Flatpak users?

2024-01-20 Thread Matěj Cepl
On Sat Jan 20, 2024 at 7:18 PM CET, Aaron Rainbolt wrote:
> It appears that the Ezra Bible App can only be installed using
> upstream packages for a select group of popular Linux distributions
> currently. It would be handy for users to be able to install it by
> using widely available repositories such as the Snap Store and
> Flathub. I'm fairly skilled at software packaging for distros (though
> I haven't done Snap or Flatpak before - I'm interested in learning how
> though) and am thinking about trying to make Snap and Flatpak packages
> for Ezra Bible App.

Given that Snap really works only on Ubuntu (AFAIK, certainly it
does work neither with Fedora nor with openSUSE), then I would
hugely prefer Flatpak.

Best,

Matěj

-- 
http://matej.ceplovi.cz/blog/, @mcepl@floss.social
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
All men's miseries derive from not being able to sit in a quiet
room alone.
  -- Blaise Pascal



signature.asc
Description: PGP signature
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] Packaging Ezra Bible App for Snap and Flatpak users?

2024-01-20 Thread Tobias Klein

Hi Aaron,

I'd be very open to that!

You should start with the build instruction:

https://github.com/ezra-bible-app/ezra-bible-app/blob/master/BUILD.md#linux

If you need to add a build script consider the existing ones for Linux here:
https://github.com/ezra-bible-app/ezra-bible-app/tree/master/build_scripts/linux

The build targets for the different platforms are also available as npm run 
actions via the package.json file:

https://github.com/ezra-bible-app/ezra-bible-app/blob/master/package.json

Feel free to raise a pull request if you want to add this additional 
packaging in the existing structures mentioned above. I'd be happy to test/ 
review your work.


Best regards,
Tobias

Am 20. Januar 2024 19:18:33 schrieb Aaron Rainbolt :


It appears that the Ezra Bible App can only be installed using
upstream packages for a select group of popular Linux distributions
currently. It would be handy for users to be able to install it by
using widely available repositories such as the Snap Store and
Flathub. I'm fairly skilled at software packaging for distros (though
I haven't done Snap or Flatpak before - I'm interested in learning how
though) and am thinking about trying to make Snap and Flatpak packages
for Ezra Bible App.

Does this seem like a good idea? Are there hurdles I should be aware
of (other than having to work with Electron)? Would the developers
prefer that I not do this?


___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


[sword-devel] Fwd: Packaging Ezra Bible App for Snap and Flatpak users?

2024-01-20 Thread Aaron Rainbolt
Gah, once again I have failed to send my response to everyone.

-- Forwarded message -
From: Aaron Rainbolt 
Date: Sat, Jan 20, 2024 at 1:07 PM
Subject: Re: [sword-devel] Packaging Ezra Bible App for Snap and Flatpak users?
To: Fr Cyrille 


On Sat, Jan 20, 2024 at 12:42 PM Fr Cyrille  wrote:
>
>
>
> Le 20/01/2024 à 19:18, Aaron Rainbolt a écrit :
>
> It appears that the Ezra Bible App can only be installed using
> upstream packages for a select group of popular Linux distributions
> currently. It would be handy for users to be able to install it by
> using widely available repositories such as the Snap Store and
> Flathub. I'm fairly skilled at software packaging for distros (though
> I haven't done Snap or Flatpak before - I'm interested in learning how
> though) and am thinking about trying to make Snap and Flatpak packages
> for Ezra Bible App.
>
> Adding it to debian repo would be nice too. And easier for sharing modules 
> than snap.

Getting it into Debian would be nice, and I actually thought about
doing that initially, but it would be... difficult. Ezra Bible App is
Electron-based. Due to the policies of Debian, Ubuntu, Fedora, and
probably most other distros I would guess, all of a package's
dependencies *have* to be in the distribution's repos in order for
software that uses those dependencies to be accepted into the repos.
Electron isn't packaged for Debian, Ubuntu, or Fedora. That means in
order to get an official Debian package for Ezra, I would have to
package **all of Electron.** Electron is based on Chromium, which
takes time and eternity to compile even on hardware much faster than
anything I own, so actually doing that packaging would be hard, and
then on top of it there are potential hurdles with versions and
whatnot - for instance Electron upstream is at version 28.1.4, Ezra is
still using 17.1.0.

Ezra's developers can distribute packages with Ezra and Electron
included because they're able to ignore policies like this - their
builders can have Internet access at build time, can use software
directly from upstream, can take advantage of package managers such as
npm, etc. None of those are available in an official Debian package -
the package has to be able to build without Internet access, use only
distro-internal dependencies, etc. So... yeah, it would be a **lot**
of work. And then I would be the maintainer of Electron in Debian,
which is probably a monumental task, one I almost certainly don't have
time for.

On the other hand, I know there are Electron apps packaged as Flatpaks
and Snaps (namely Element, but also others). If I understand
correctly, Snap and Flatpak packages have significantly more lenient
requirements, which makes packaging much easier for those platforms.
Then there would be Ezra packages not only for Debian, Fedora, and
derivatives, but also for Arch, Gentoo, RHEL, NixOS, etc., etc. That
seems like it would take significantly less time to do and would
potentially have a better impact.

> Does this seem like a good idea? Are there hurdles I should be aware
> of (other than having to work with Electron)? Would the developers
> prefer that I not do this?
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
>
> --
> Vous aimez la Bible ? Vous êtes étudiant en théologie ? Utilisez 
> l'application libre Xiphos ou Andbible et accédez aux textes sources, à des 
> commentaires, des dictionnaires et beaucoup d'autres fonctionnalités... Me 
> contacter pour des traductions en français.
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] Packaging Ezra Bible App for Snap and Flatpak users?

2024-01-20 Thread Fr Cyrille



Le 20/01/2024 à 19:18, Aaron Rainbolt a écrit :

It appears that the Ezra Bible App can only be installed using
upstream packages for a select group of popular Linux distributions
currently. It would be handy for users to be able to install it by
using widely available repositories such as the Snap Store and
Flathub. I'm fairly skilled at software packaging for distros (though
I haven't done Snap or Flatpak before - I'm interested in learning how
though) and am thinking about trying to make Snap and Flatpak packages
for Ezra Bible App.
Adding it to debian repo would be nice too. And easier for sharing 
modules than snap.

Does this seem like a good idea? Are there hurdles I should be aware
of (other than having to work with Electron)? Would the developers
prefer that I not do this?
___
sword-devel mailing list:sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


--
Vous aimez la Bible ? Vous êtes étudiant en théologie ? Utilisez 
l'application libre Xiphos  ou Andbible 
 et accédez aux textes sources, à des 
commentaires, des dictionnaires et beaucoup d'autres fonctionnalités... 
Me contacter pour des traductions en français.___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


[sword-devel] Packaging Ezra Bible App for Snap and Flatpak users?

2024-01-20 Thread Aaron Rainbolt
It appears that the Ezra Bible App can only be installed using
upstream packages for a select group of popular Linux distributions
currently. It would be handy for users to be able to install it by
using widely available repositories such as the Snap Store and
Flathub. I'm fairly skilled at software packaging for distros (though
I haven't done Snap or Flatpak before - I'm interested in learning how
though) and am thinking about trying to make Snap and Flatpak packages
for Ezra Bible App.

Does this seem like a good idea? Are there hurdles I should be aware
of (other than having to work with Electron)? Would the developers
prefer that I not do this?
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] Catholic versification

2024-01-20 Thread Michael Johnson
Even better than per-book versification, I think that per-translation 
versification makes more sense. That way, no change to the code would 
need to be made to tweak the versification yet again. No matter how many 
versifications we define, someone will find or invent another one.


On 1/20/24 06:06, Michael H wrote:
In my limited study of 'Fixing' versification (meaning parallel 
display across versification...)


Can I recommend revamp to support an additional 'BOOK' level 
versification.  This would pretty much eliminate the need for (yet) 
another versification system, if each book rather than module could 
name its own versification.


So for Cyrille's example the module is 'catholic' (for all 70ish) 
books, but Esther is book versified to 'cath2' or whatever already 
matches it.




On Sat, Jan 20, 2024 at 7:00 AM Fr Cyrille  
wrote:


Hello,
Recently a person interested in the Catholic bible in French told me
about the mapping problems between Catholic versification and the
kjva
concerning Esther. So I'm bringing up the question of a new Catholic
versification that could better deal with this kind of problem and at
the same time incorporate some of the errors in current Catholic
versifications. I should mention that two versifications for French
Bibles have been added since my proposal for a new Catholic
versification, which was made long before these versifications were
added, and which was not favorably received at the time. In our case,
the number of Bibles that follow this versification is simply
enormous,
since the majority of Catholic Bibles do. I would also add that
the LXX
versification is not entirely correct. There are no LXX today that
put
16 chapters to Esther. Ralph's already uses letters to integrate
Greek
passages into the text.
In fact, Catholic versification simply follows Ralph's. So I suggest
that we seriously reopen this question with concrete suggestions.
For my part, the suggestion is simple: convert the numbers in the
Greek
passages into verses and offset the numbered verses in the same
chapters. I'll copy you on what that might look like.

Br Cyrille___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list:sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

--
signature

Aloha,
*/Michael Johnson/**
26 HIWALANI LOOP • MAKAWAO HI 96768-8747*• USA
mljohnson.org  • eBible.org  
• WorldEnglish.Bible  • PNG.Bible 


Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921
Skype: kahunapule • Telegram/Twitter: @kahunapule • Facebook: 
fb.me/kahunapule 
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


Re: [sword-devel] Catholic versification

2024-01-20 Thread Michael H
In my limited study of 'Fixing' versification (meaning parallel display
across versification...)

Can I recommend revamp to support an additional 'BOOK' level
versification.  This would pretty much eliminate the need for (yet) another
versification system, if each book rather than module could name its own
versification.

So for Cyrille's example the module is 'catholic' (for all 70ish) books,
but Esther is book versified to 'cath2' or whatever already matches it.



On Sat, Jan 20, 2024 at 7:00 AM Fr Cyrille  wrote:

> Hello,
> Recently a person interested in the Catholic bible in French told me
> about the mapping problems between Catholic versification and the kjva
> concerning Esther. So I'm bringing up the question of a new Catholic
> versification that could better deal with this kind of problem and at
> the same time incorporate some of the errors in current Catholic
> versifications. I should mention that two versifications for French
> Bibles have been added since my proposal for a new Catholic
> versification, which was made long before these versifications were
> added, and which was not favorably received at the time. In our case,
> the number of Bibles that follow this versification is simply enormous,
> since the majority of Catholic Bibles do. I would also add that the LXX
> versification is not entirely correct. There are no LXX today that put
> 16 chapters to Esther. Ralph's already uses letters to integrate Greek
> passages into the text.
> In fact, Catholic versification simply follows Ralph's. So I suggest
> that we seriously reopen this question with concrete suggestions.
> For my part, the suggestion is simple: convert the numbers in the Greek
> passages into verses and offset the numbered verses in the same
> chapters. I'll copy you on what that might look like.
>
> Br Cyrille___
> sword-devel mailing list: sword-devel@crosswire.org
> http://crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


[sword-devel] Catholic versification

2024-01-20 Thread Fr Cyrille

Hello,
Recently a person interested in the Catholic bible in French told me 
about the mapping problems between Catholic versification and the kjva 
concerning Esther. So I'm bringing up the question of a new Catholic 
versification that could better deal with this kind of problem and at 
the same time incorporate some of the errors in current Catholic 
versifications. I should mention that two versifications for French 
Bibles have been added since my proposal for a new Catholic 
versification, which was made long before these versifications were 
added, and which was not favorably received at the time. In our case, 
the number of Bibles that follow this versification is simply enormous, 
since the majority of Catholic Bibles do. I would also add that the LXX 
versification is not entirely correct. There are no LXX today that put 
16 chapters to Esther. Ralph's already uses letters to integrate Greek 
passages into the text.
In fact, Catholic versification simply follows Ralph's. So I suggest 
that we seriously reopen this question with concrete suggestions.
For my part, the suggestion is simple: convert the numbers in the Greek 
passages into verses and offset the numbered verses in the same 
chapters. I'll copy you on what that might look like.


Br Cyrille/**
 *
 *  canon_catholic3_lit.h -	Versification data for the Catholic system
 *
 * $Id: canon_catholic3_lit.h 2915 2017-11-20 16:55:54Z l'Africain $
 *
 * Copyright 2010-2017 CrossWire Bible Society (http://www.crosswire.org)
 *	CrossWire Bible Society
 *	P. O. Box 2528
 *	Tempe, AZ  85280-2528
 *
 * This program is free software; you can redistribute it and/or modify it
 * under the terms of the GNU General Public License as published by the
 * Free Software Foundation version 2.
 *
 * This program is distributed in the hope that it will be useful, but
 * WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 * General Public License for more details.
 */

#ifndef CANON_CATHOLIC3_LIT_H
#define CANON_CATHOLIC3_LIT_H

SWORD_NAMESPACE_START


// Versification system: Catholic3_lit
// Book order: Gen Exod Lev Num Deut Josh Judg Ruth 1Sam 2Sam 1Kgs 2Kgs 1Chr 2Chr Ezra Neh Tob Jdt Esth 1Macc 2Macc Job Ps Prov Eccl Song Wis Sir Isa Jer Lam Bar Ezek Dan Hos Joel Amos Obad Jonah Mic Nah Hab Zeph Hag Zech Mal Matt Mark Luke John Acts Rom 1Cor 2Cor Gal Eph Phil Col 1Thess 2Thess 1Tim 2Tim Titus Phlm Heb Jas 1Pet 2Pet 1John 2John 3John Jude Rev

/**
 * [on]tbooks_catholic - initialize static instance for all canonical
 *		 text names and chapmax
 */
struct sbook otbooks_catholic3_lit[] = {
  {"Genesis", "Gen", "Gen", 50},
  {"Exodus", "Exod", "Exod", 40},
  {"Leviticus", "Lev", "Lev", 27},
  {"Numbers", "Num", "Num", 36},
  {"Deuteronomy", "Deut", "Deut", 34},
  {"Joshua", "Josh", "Josh", 24},
  {"Judges", "Judg", "Judg", 21},
  {"Ruth", "Ruth", "Ruth", 4},
  {"I Samuel", "1Sam", "1Sam", 31},
  {"II Samuel", "2Sam", "2Sam", 24},
  {"I Kings", "1Kgs", "1Kgs", 22},
  {"II Kings", "2Kgs", "2Kgs", 25},
  {"I Chronicles", "1Chr", "1Chr", 29},
  {"II Chronicles", "2Chr", "2Chr", 36},
  {"Ezra", "Ezra", "Ezra", 10},
  {"Nehemiah", "Neh", "Neh", 13},
  {"Tobit", "Tob", "Tob", 14},
  {"Judith", "Jdt", "Jdt", 16},
  {"Esther", "Esth", "Esth", 10},
  {"I Maccabees", "1Macc", "1Macc", 16},
  {"II Maccabees", "2Macc", "2Macc", 15},
  {"Job", "Job", "Job", 42},
  {"Psalms", "Ps", "Ps", 150},
  {"Proverbs", "Prov", "Prov", 31},
  {"Ecclesiastes", "Eccl", "Eccl", 12},
  {"Song of Solomon", "Song", "Song", 8},
  {"Wisdom", "Wis", "Wis", 19},
  {"Sirach", "Sir", "Sir", 51},
  {"Isaiah", "Isa", "Isa", 66},
  {"Jeremiah", "Jer", "Jer", 52},
  {"Lamentations", "Lam", "Lam", 5},
  {"Baruch", "Bar", "Bar", 6},
  {"Ezekiel", "Ezek", "Ezek", 48},
  {"Daniel", "Dan", "Dan", 14},
  {"Hosea", "Hos", "Hos", 14},
  {"Joel", "Joel", "Joel", 4},
  {"Amos", "Amos", "Amos", 9},
  {"Obadiah", "Obad", "Obad", 1},
  {"Jonah", "Jonah", "Jonah", 4},
  {"Micah", "Mic", "Mic", 7},
  {"Nahum", "Nah", "Nah", 3},
  {"Habakkuk", "Hab", "Hab", 3},
  {"Zephaniah", "Zeph", "Zeph", 3},
  {"Haggai", "Hag", "Hag", 2},
  {"Zechariah", "Zech", "Zech", 14},
  {"Malachi", "Mal", "Mal", 3},
  {"", "", "", 0}
};

/**
 *	Maximum verses per chapter
 */

int vm_catholic3_lit[] = {
  // Genesis
  31, 25, 24, 26, 32, 22, 24, 22, 29, 32,
  32, 20, 18, 24, 21, 16, 27, 33, 38, 18,
  34, 24, 20, 67, 34, 35, 46, 22, 35, 43,
  54, 33, 20, 31, 29, 43, 36, 30, 23, 23,
  57, 38, 34, 34, 28, 34, 31, 22, 33, 26,
  // Exodus
  22, 25, 22, 31, 23, 30, 29, 28, 35, 29,
  10, 51, 22, 31, 27, 36, 16, 27, 25, 26,
  37, 30, 33, 18, 40, 37, 21, 43, 46, 38,
  18, 35, 23, 35, 35, 38, 29, 31, 43, 38,
  // Leviticus
  17, 16, 17, 35, 26, 23, 38, 

[sword-devel] Module release: GerNeUe

2024-01-20 Thread domcox
Dear All,

This is to announce that we have just now uploaded GerNeUe
in the CrossWire (main) repository.

## Language:
German

## Description:
Neue evangelistische Übersetzung

## Category:
Biblical Text

## Version:
This is an update. Version: 3.2

## What's new:
Source text version from January 1, 2024. Also fixed passages in italics.

Many thanks to Manuel_Roth for the hard work.

We wish you enjoyable reading,
The Module Team

P.S.: This email is sent automatically on upload of a new/updated module

___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page