|
On 08/15/2015 04:32 PM, DM Smith wrote:
Bible Desktop 1.6, the latest release, does not handle zips that
have directory entries. The next release (any day now, for a real
long time) does not have this problem. This means that none of the
modules are available to users of Bible Desktop.
I'm glad that Bible Desktop is going to fix that problem, since the
module and repository creation instructions say that the zip files
should have directory entries.
The first few modules I tried didn’t have zips at all.
E.g. any of the dictionaries. This provides an unpleasant user
experience in BibleDesktop as it does a HEAD on the zip to get its
size.
I'll fix those, hopefully within a couple of days. All of the Bibles
should have zips, though.
As a matter of style, Description should be the
“title” of the work, not an actual description. That is, it
should be short. Here is one of the long ones:
| The World Messianic Bible
British Edition is a Public Domain translation of the
Holy Bible into modern English as spoken among Messianic
Jews outside of the United States of America. This
translation is also known as the World English Bible:
British Messianic Edition. |
This probably should be
World
Messianic Bible British Edition
The content is more appropriate in the About field.
OK. I have a short title in my metadata. I just need to use that
instead of what I call a description in the Description field.
The [name] of the module should be the appropriate
english abbreviation for the module. It has to be ASCII letters
and digits. We’ve recently added Abbreviation as a means of
providing internationalization of the name. I don’t know how
many applications show the Abbreviation instead of the module
name.
The same module above has
WBBM should be what is in the []. The value of what
you provide is that their is very unlikely to be collisions with
other repositories.
The module names I provided also avoid collisions within the same
large repository. Most of the Bibles in the repository don't
actually have an abbreviation other than a language code. Some do.
Abbreviations are not globally unique, but only unique within a
language, so putting the abbreviation in the [module name space]
isn't a great idea with this many modules. For example, I have both
an English KJV and a Thai KJV. I also have an NVI in Spanish and an
NVI in Portuguese that I would like to get permission to distribute.
Many applications in laying out their UI assume that
the name is very short.
That is a silly, but reasonable, assumption when working with just
English language translations, plus maybe a few others. However, it
seems that it might make more sense to allow longer actual module
names, but use the abbreviation field contents for the UI to display
the current version.
I also noticed, but didn’t take note of the place,
that ShortCopyright=…. was at the end of the About field in
several modules.
I'm not sure what you mean. Yes, there are ShortCopyright = lines.
Hope this helps.
Yes. Thank you.
In His Service,
DM
Please forgive the missed
modules. I tried to save time by selecting only the
modules with upper case letters for rebuilding, and
missed some. In my excitement, I kept working on this
even while traveling. It is kind of awkward remote
controlling my computer at home with a
smaller-screened laptop, so the text is tiny and the
scrolling is jerky. That still worked better than
trying to do all of this from my laptop directly,
because of bandwidth constraints traveling. Still, it
would have been faster to rebuild everything,
apparently. That is what happens when I'm rushed and
tired.
On the other hand, during the day I was in a set of
meetings where I met the director of the Philippine
Bible Society, so I have high hopes of getting some
more Bible translations for us. Stay tuned on that.
Yesterday, I added the Binandere Mark, Luke, and Acts
to the set. That is probably more exciting to a small
group of people from the Oro Province of Papua New
Guinea than for you.
I'm back at home, now. I think I have manually rebuilt
the modules with capitalization errors, but I just
kicked off a full rebuild, just in case.
On 08/14/2015 11:12 AM, Karl Kleinpaste wrote:
On 08/14/2015 12:10 PM,
Kahunapule Michael Johnson wrote:
The eBible.org
repository refresh is done, again, with no case
squashing anywhere, and consistent capitalization. I
hope. (Tell me if I missed something, of course.)
For the 3rd time,
there are case errors causing installation failure
and, of course, failure of the module to be usable
in any case-sensitive filesystem such as Linux/UNIX
systems, if the modules are manually installed.
Examples:
$ grep DataPath tzo*
tzoNT1995.conf:DataPath=./modules/texts/ztext/tzoNT1995/
tzoSA1983.conf:DataPath=./modules/texts/ztext/tzosa1983/
tzoZNT2009.conf:DataPath=./modules/texts/ztext/tzoznt2009/
ftp> cd pub/sword/modules/texts/ztext
250 CWD command successful
ftp> dir tzo*
227 Entering Passive Mode (74,208,71,128,140,61).
150 Opening ASCII mode data connection for file list
drwxrwxr-x 2 ebible psacln 4096 Aug 14
02:00 tzoNT1995
drwxrwxr-x 2 ebible psacln 4096 Aug 11
17:25 tzoSA1983
drwxrwxr-x 2 ebible psacln 4096 Aug 11
17:26 tzoZNT2009
My testing of this has been simply to select all
modules for installation. You could do this
yourself and find the same result. I don't
understand why this is such a challenge.
--
Aloha,
Kahunapule Michael Johnson
MICHAEL
JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
USA |
eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule |
_______________________________________________
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
--
Aloha,
Kahunapule Michael Johnson
MICHAEL JOHNSON
PO BOX 881143
PUKALANI HI 96788-1143
USA |
eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule |
|
