wrote:
On Fri, 2015-07-31 at 14:44 -0500, Michael H wrote:
I haven't worked on it myself,
And I think this is the problem.
Xrefs can take any number of complicated forms. lists, ranges, etc.
They are context dependent - sometimes the xref is only to a verse or a
chapter/verse combo
A live production repository probably shouldn't be the immediate landing
place for a developmental script. Can I suggest a 2nd development ebible
repository, where untested modules generated by the script can land to be
validated without destroying a known working version?
Main sword repositories
3) include into the sorting and display of the list a fall back which shows
the origin of duplicate modules.
ex:
KJC (King James Clarified)
KJV (King James with Sword -- from Crosswire)
KJV (King James Bible -- from ebible)
KJV (King James Bible with maps and corrected crossreferences --from
Properly coded USFM has the book names for cross references listed in the
header info of each book (/toc1, /toc2, /toc3, or /h). That info, added
back to a well formed AV11N, should allow for easy to parse xrefs.
I haven't worked on it myself, but it should be easier to deal with digits
only to
I'm missing at a minimum the case of sub-verse ranges: references to
Matthew 7:23b and the like. I submit that for clicking through, I don't
think this level of accuracy is necessary. Even on tiny phones, in most
cases you land on the screen with the intended target point. A very few
longer verses
This is forward thinking, but not too far off...
7000 includes only 1 work per language. If you expand the thinking to
include commentaries, devotions, dictionaries, and genbooks... 16 bit
(65,000) might be a good total allowance for the next decade, but 24 bit
(16,000,000) or more is the goal.
On BibleDesktop (1.6) running on Windows 7 professional (in a Parallels
environment on top of Mac OSX Yosemite):
1. eng_t4t2014: The given URL C:\Users\me\Application
Data\Sword\modules\texts\ztext\eng_t4t2014 could not be created as a
directory. Browsing with a file manager shows application
The only working copy of BibleDesktop I have currently is in windows 7,
BibleDesktop version 1.6. I don't see any 'view source' option, which would
be really nice to have available. Which platform/version of BibleDesktop
has this feature enabled?
On Sun, Aug 2, 2015 at 1:57 PM, DM Smith
I've been unable to verify what I was looking at when I came to the
conclusion that NRSV was used when osis2mod is run without a -v parameter.
My apologies to DM Smith and David H for creating any misunderstanding.
I now suspect I've misread a New Testament introduction that claims to be
I'm updating SPARVG to the 2015 text, and making a few corrections (moving
the directives in psalms to their proper place prior to verse 1. and a
single opening question mark into the redletter zone in matthew 16.)
I'm working on the conf file now.The RVG module on crosswire has
In modern Bible Translation (Wycliffe/SIL) circles, "default" versification
in the translation programs (ParaTExt, SIL Translation Editor, and Teus'
BiblEdit) is 'English' which is (as far as I know) the same versification
as what Sword calls NRSV, so this change should be considered. It will
These extraverse 'descriptions' labelled here "canonical titles" are also
almost universally marked up as body text in a slightly smaller bold font,
or an italic centered font, but NOT the same style as chapter or book
titles.
Many (all?) sword front ends treat as a main title,
and not as the
The primary USFM translation program, ParaTExt, sorts things by chapter.
Specifically, everything between \c and \c is considered 1 chapter. and the
normal view of the Paratext program is to limit what appears on screen in
this way: Only text that occurs after the \c shows with the rest of that
There used to be digital versions available at http://peshitta.org . I'm
not sure, but I think Lamsa's version is the source of the English in the
interlinear you can see there. My copy of Lamsa's Bible is at work, but I
could verify some verses once I'm back at my office.
On Tue, Sep 29, 2015
Slightly related, but still a degree of separation or two away from Sword
technology:
SILE is a pagebuilder program. SILE directly uses Harfbuzz. The programmer,
Simon Cozens, is investing in SILE to get Bibles into peoples hands...
https://www.youtube.com/watch?v=t_kk20vlamo
This is an aside, but only one step off the path:
Have we considered that the NASB has a major revision due out this year?
Lockman won't publicly predict a date, but another group I watch has
members with first hand knowledge and suggest there will be a NASB 2016
revision, which will supercede
Adobe InDesign up to CS6 can open quark files with limited success. If i
remember right, the original InDesign cloud version could also deal with
qxp files, but CC14 and CC15 no longer recognize them.
Likely, there will also be font issues to solve, because quark effectively
predates open type
Hi Matej,
There is an OSIS2USFM python script on github, but a quick glance suggests
it is built for a specific purpose and did not try to understand the
complete OSIS or USFM specifications. However, If you do it yourself, that
might be a place to start.
OSIS and USFM have similar purposes, but
SimpleXML export
https://www.dokuwiki.org/plugin:simplexml
looks like a very good starting point.
On Mon, Feb 8, 2016 at 2:12 AM, Peter von Kaehne wrote:
> As far as I understand Glaubesstimme is produced in Dokuwiki and then
> uses Dokuwiki plugins to export into various
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.
Whether a module will open depends on the conf file. The threads I've seen
suggest the conf should exclude all frontends pre sword 1.8 if they use
these versifications.
On Wed, Aug 26, 2015 at 3:33 PM, Kahunapule Michael Johnson <
kahunap...@ebible.org> wrote:
> If I use the new versifications
https://www.crosswire.org/wiki
On Fri, Mar 11, 2016 at 6:03 AM, Fr Cyrille wrote:
> OK but where can I found the developer's wiki?
>
>
> Le 11/03/2016 12:01, David Haslam a écrit :
>
>> They are documented in the developers' wiki.
>>
>> Follow the Versification category.
Back in 2006-2088 I built NIV and a few other modules that used links to '
m.biblegateway.com' to pull 'restricted' texts into parallel displays. It
worked pretty well, but then biblegateway changed schemes a bit... Those
dinosaurs are still lurking out on Archive.org somewhere.
On Sat, Mar 19,
https://archive.org/details/BibleGatewaySwordModule
On Fri, Apr 1, 2016 at 6:14 AM, Michael H <cma...@gmail.com> wrote:
> Back in 2006-2088 I built NIV and a few other modules that used links to '
> m.biblegateway.com' to pull 'restricted' texts into parallel displays. It
> wor
And apparently I published a beta that used the primary site. The mobile
site fit into the front ends much nicer.
On Fri, Apr 1, 2016 at 6:14 AM, Michael H <cma...@gmail.com> wrote:
> Back in 2006-2088 I built NIV and a few other modules that used links to '
> m.biblegateway.
not confirmed whether it's in
WEB USFX source, Hawiaiaia (I can never spell that right) or in ANDBIBLE.
and there should be some easy workarounds possible in the meantime.
On Mon, May 23, 2016 at 5:09 PM, Michael H <cma...@gmail.com> wrote:
> These 95 verses don't seem to appear in the WE
I should also disclaim, Today I reviewed "WEBBE with Deuterocanon OSIS" in
a text editor, and sample verified the missing verses in WEBC. There might
be slightly different complete list in WEBC than this.
On Mon, May 23, 2016 at 5:34 PM, Michael H <cma...@gmail.com> wrote:
>
These 95 verses don't seem to appear in the WEBC module using ANDBIBLE. (I
only checked the first 10 or so...)
There appears to be an interaction between your missing verses and the appearing after the end of the verse but before the end of the chapter.
Seeing that there's a high correlation,
https://en.wikipedia.org/wiki/IOS_version_history
IOS 5.1.1 represents the last version available most importantly for the
original iPad, but also and iPad touch (3).
There are still a significant number of original iPads out there running
IOS 5.1.1, since Apple deprecated them prior to
That leading colon suggests something is trying to parse a null and
reverting to the last text after a fail. Instead of looking for {John
3:16}, it appears to be searching for {John 3:16,} How the code detects
the end of the verse range (or whether the next range is null) is where I
would start.
Hooray Troy!
___
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
Hooray for the update!
I've previously asked and it was debated, but I'll ask again...
Can the EMTV and the Apostle's Bible be combined into the LOGOS Bible, and
published as such on Crosswire? Paul Esposito previously sold the EMTV and
Apostles Bible (OT) in this form I suspect the name
I use beanshell quite a bit. It's completely integrated into jEdit, and
allows a reatlime onscreen environment rather than a command line, load the
text to see it iterations. The fact it's largely independent of OS helps a
lot, since I switch between Android, OSX, windows, and Linux quite a bit
If I were looking for a solution, I'd try using the \p tag. I suspect
USFM->OSIS step has limited logic for USFM that doesn't include paragraph
tags.
That is, include paragraph tags prior to each verse
\p
\v 1
For every verse in every book. This can be accomplished with a simple
search
There is an updated 2001 edition of the ESV (ESV2001 on crosswire, version
1.0.2), which did not declare itself an update of the older ESV module
(version 1.0.1 on my machine).
1. Does the problem appear in the 1.0.2 version?
2. Is there a way to deprecate the 1.0.1 version without releasing a
Yes, that's an interesting question.. This isn't about just the Julian
calendar, The liturgical calendar is based on the first Sunday after the
first full moon after the spring equinox (also known as Easter.) This
calendar is used to some degree by almost all modern daily reading plans,
not just
On a mission trip this summer, one of my fellows was carrying an Ipod Touch
he purchased in 2016. The Ipod is still developed and sold by Apple and,
and being the only apple product even remotely affordable, is still very
much a front line usage case for PocketSword.
On Sat, Aug 19, 2017 at 4:15
Clearly, the problem was with version 1.0.5 being mistyped as 1.5
somewhere. a 'cleanup' version doesn't sound like a skip 4 type of
version.
On Sat, Jun 24, 2017 at 12:46 PM, David Haslam
wrote:
> I was incorrect in my earlier observation.
>
> Now I see why Bela didn't
Your additional info seems to confirm that Xiphos accepted a typo in 2012,
and has not updated its listing since. The conversation should be how to
mitigate this (and similar typos that may also exist in other modules) in
the Xiphos repository.
On Sat, Jun 24, 2017 at 1:04 PM, David Haslam
I received announcements about these works on June 19.
___
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
Peter isn't who I was thinking would benefit from keeping a professional
level of communication in the list. The other members might enjoy the list
more. The need to adjust things is obviousThe need to tell everyone on the
list about a missing entry which causes nobody trouble is well... possibly
Hooray Peter for the Hard work.
Can we fix the negative comments script to only feedback to those who need
the info?
On Fri, Jun 16, 2017 at 12:55 PM, David Haslam
wrote:
> Please review how the module release script generates this line in the
> announcement message.
>
>
The aggregation into a large USFM file is 1 command line (cat .\*\*.dat >
shona.sfm) .
Splitting that into standard book files is 1 more command (csplit /\\id /
shona.sfm) .
You need to check each \c tag has it's own line , incase the chapter files
end abnormally without a final newline/return.
It's been a week or so since I peeked at the directories. I'm sure the
variation is in my head and there is no other weirdness going on. the unix
utility *cat* will deal with subdirectories without blinking.. the example
I listed before includes 1 level of directory, just add another.
I can
On Wed, Aug 30, 2017 at 3:58 AM, Peter von Kaehne <ref...@gmx.net> wrote:
> On Tue, 2017-08-29 at 23:39 -0500, Michael H wrote:
> >
> > The initial run on my machine took about a quarter second to
> > concatenate, but while the resulting files are valid, they
> >
This is an honor culture issue... (which Peter has previously sent me
useful, if a little off-target, info on.)
My understanding about ruby in Japanese (which is limited to a few
conversations and having been cc'd on emails which danced around the issue
among others like leading and the need for
STEP suggests that leading zeros do not belong in between the letter and
the digits.
https://stepweb.atlassian.net/wiki/spaces/TYNSTEP/pages/36569098/OSIS+samples#OSISsamples-OSISofaBiblewithstrongnumbers(ESV)
On Tue, Sep 26, 2017 at 10:38 PM, Gary Holmlund wrote:
> I am
The \addpn was pre-nested tags... it provided both dotted underline and
italicized text (or in CJK the appropriate alternate font) to indicate a
proper name that is not in the original text. nested tags make this
redundundant.
I would suggest the underline as the proper way to mark the names. It
In USFM, the proper name marker [ \pn ] is a feature in East asian
Languages (Chinese), proper names are typographically marked (dotted
underlines most frequently) to aid the reader recognizing those glyphs.
That's the original use, and the intent of it's presence in OSIS. There
might be others.
Hi Cyrille,
I am preparing to study breakpoints for Cebuano to produce a hunspell
hyphenation list, but haven't completed the process of implementing it. I
am working from 3 paper Cebuano bibles typeset at different times, and
manually copying the existing hyphenated words into a list.
Here's my
If you have a list of words with valid hyphenation points, it is very
valuable to someone someday that list is documented as a spelling
dictionary, even if it is incomplete and known to be. Finding valid
hyphenation points is the biggest chunk of time in preparing for
publication. and in many
FYI:
In USFM:
\vp *replaces *\v - used when the verse numbering appears out of order or
verse markers include alpha characters.
\va creates a visible *added word* inside of the verse. - used when
multiple versifications are being presented at the same time.
The problem with the proper
CAUTION:
The soft hyphen is sometimes used in Indian and East Asian language scripts
to prevent two adjacent characters from becoming a combined ligature. This
is more common in minor languages. It is commonly used when the font in use
while being typed is designed for another language using the
This is a question:
Is there anything in OSIS (or Sword coding) that limits the osisID 1 to 1
to a milestone? Would including more than one osisID within a milestone
create errors?
Dieu dit à Noé de construire un grand bateau
9-10Voici l’histoire de Noé. Noé est le père de trois fils :
Kahunapule,
I sent you an email about this about 9 months ago:
The issue might be that all of the modules on ebible.org have a minimum
requirement for sword 1.7.4 in place, regardless of actual module content
vs. sword engine capabilities. (I did not validate ALL, but I have tested
~20 or so
There is a version of BibleDesktop that allows you to 'view source' and see
the osis of each verse or chapter from inside the front-end. it's an older
version, so you might run into issues with newer versifications, but if
using a longstanding versification it's very helpful if you're
It might add value for everyone if the module upload notice email includes
a link to more information:
http://crosswire.org/sword/modules/ModInfo.jsp?modName=OSHB
This shouldn't take much in the way of logic, and makes it much simpler to
figure out what the module identifier code means.
On Fri,
Hi John,
If you're planning to submit to crosswire for hosting, All of these
questions are handled by the module maintainer at crosswire (currently
Peter.) You don't really need to worry about them, other than to confirm
your source does compile. You need to confirm it's clean source (the OSIS,
Since the .conf files have no user configuration switches... fedora is
wrong.
Files of this type, .conf files, in unix regularly have switches. Fedora is
suggesting the Man pages describe what the end user can do by changing the
configuration files. The only thing they can do is cause the
Has anybody studied whether it is possible to link ParaTExt to sword?
There's an unfilled need here for Translation teams working in windows
hostile areas (Africa/SE Asia)... they use linux to access Paratext, and
many of the resources are hard to get to link to the current verse being
worked on.
Hi Vince,
There isn't really a good native OSIS editing system. However, there are
excellent Bible editing software programs available with no cost.
I suggest you seek an USFM editor instead. Bibledit, Paratext, Autographa
Lite, Translation Studio are all excellent programs. (See the links).
Most newly translated Bibles do not follow the Biblica Hebreica
Stuttgartensia (BHS) versification, only use it as a reference for
describing deviations. Most newly translated Bibles are based on the WORDS
of the BHS for the Old Testament, or at least use BHS as a reference for
where they deviate
Andrew,
If I'm trying to get a novel published and I get a rejection letter, It
does not help my chances to try to publicly ridicule the guy who sent me
that letter. Trying to defame Peter in his efforts is not helping your
efforts, and probably has permanently removed your submissions from
John,
I'm fairly sure the root problem has already been addressed, but due to the
long lead time for the new french versifications to be present across all
front end programs, the fix to the module is being delayed. Once most user
cases are using Sword 1.8, the module will be updated. (but then
One step beyond from DM Smith's response: if you correct the osis2mod
statement to output to the rawtext folder, it should conform to naming
conventions. You might also have to update the conf file to point to this
location.
That is
use this command to create the module:
osis2mod
to Troy.
>>>>>>>
>>>>>>> Troy will have to add that to the list of authorized devices and
>>>>>>> rebuild Bishop.ipa.
>>>>>>>
>>>>>>> Download that ipa and in the same window, click + under INSTALLED
>>
If I'm following your concern correctly, I vote for both a 'conductor' mode
and a 'sidetrip' mode. That is what you describe as the default for xiphos
"speak every time the user navigates" is more of a conductor mode... every
screen follows the primary. Whereas the behavior described for bishop
I already had AndBible installed.
Bishop installed and recognized all the modules (at least 20+ bibles, i
haven't confirmed "ALL") that AndBible has present. I haven't attempted any
more module installs after installing Bishop, either from AndBible or
Bishop.
The text is small on my Samsung
(3rd attempt: no images this time)
The developer on Google play is listed as VSIONTEQ. They aren't related to
the church. They have only a few items on the play store, so this is either
an obfuscation layer of a larger outfit or a small org. But.. they are
likely the ones who can fix the
Any time your list of exceptional conditions contains more text than the
conversion itself, you have to start questioning whether 'automation' is
even possible.
I spent time developing similar scripts (something like wordxml -> USFM)
for single use cases. Doing the conversion was usually about
Re: embedded milestones. Each entry has its own text that isn't repeated,
but also isn't in the biblical stream... These entries are displayed many
times via iframes from within the biblical text. That is, at the
commentary level: (comment1, comment2, ..., comment7399)
Genesis 1:0 pulls an
st public one is of course BibleTime Mobile but I have seen others.
> "Pocket Bible" appears to be based on Sword and seems to use the IBT
> repository - but not the rest(?). I have seen others, but can't find them
> in a rush.
>
> Peter
> *Gesendet:* Freitag, 02.
As long as you're opening the unlock option for debate, can I suggest that
the unlock codes get hashed for the user in some way. That is the user
provides some kind of credential information to the publisher, which the
publisher uses some of the info to hash the unlock code, and the resulting
hich outputs formats
like indesign. I'm not in that group, so I'm not certain if its functioning
on Linux or not.)
On Fri, Jan 4, 2019 at 4:50 PM Matěj Cepl wrote:
> On 2018-12-14, 13:24 GMT, Michael H wrote:
> > If you're familiar with linux, and have a partition to
> > dedica
n on all that on sword-devel. Look into the
>> > archives for more info.
>> >
>> > The other development of course has been the ever improving provision
>> of
>> > TTS systems. These of course do not support many/any minority languages.
>> &
Matej,
you can use Bibledit to import the project into USFM, which is somewhat
easier to deal with.
The Bible Drop-box will produce a myriad of outputs. Both HTML and Word
import into indesign better than your RTF example.
Michael Johnson's Haiola is what runs the Drop box.. it will do most or
Cyrille,
I have sources for CPDV. I've been working with Ron Conte early this year
from January - May. They are complete except for the phrasing of poetic
books. However, I'm not working on them right now. I'll contact you off
list.
On Tue, Dec 4, 2018 at 9:25 AM Cyrille wrote:
>
>
> Le
Cyrille,
Obviously, asking background questions like where is the source very much
moves the project along. Please continue as you were. Your work and
leadership on this are very much noted and appreciated.
There are certain voices that might suggest what to do or how you should be
moving
The biggest problem here is that sword update to 1.8 missed the ubuntu 18
LTS feature freeze, so it will be 2020 before sword 1.8 is fully supported
in the bulk of linux installations without special management, and 2022
before Ubuntu 18 support for Sword 1.7 is officially ended. (SIL/Wycliffe
In usfm:
Vp is displayed instead of v. Correct processing is difficult because this
is frequently used to reorder verses. Vp would represent the matching
versification... the source of the text from the original language, while v
represents the intended order of display.
Va is displayed as will
> 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
What would the command line look like? That is, HOW would you push
commentary into a bible module?
On Sat, Nov 24, 2018 at 4:32 AM Peter von Kaehne wrote:
to distribute anything
> >> which would
> >> > not work on all platforms, at least I'm theory.
> >> >
> >> > More interesting though, and this is where we never made much
> >> progress
> >> > is whether it is poss
There are currently 44 Bible Text projects on Door43 (Unfolding word). Is
any repo willing to host these?
Here's a list of the projects:
https://docs.google.com/spreadsheets/d/1Zq9ySjMA-Dui0-J91IqD03qe-d2LyCb50rdcitMcZSY/edit?usp=sharing
Most of these these use a simple USFM markup with a
a) I don't
currently have any plan to tackle the notes projects stored in tab
separated values files.
On Sat, Apr 6, 2019 at 12:56 AM Michael Johnson wrote:
> Yes. I already have a few of them imported. I plan to import the rest to
> the eBible.org repository.
>
> On 4/5/19 8:
Have you tried scrolling up in Bibletime? Bibletime sets the display to
start at verse 1 in each chapter. If there is a Chapter title, intro,
verse zero or section title information, it is in the stream, but 'above'
the top of the display.
On Sun, Mar 31, 2019 at 8:42 AM Cyrille wrote:
> Ok I
In usfm, and paratext, each row of a table is independent. That is, several
separate "paragraphs" that start \tr are displayed in a grid form, but each
row (\tr) is treated separately.
As you approach 'tables' in OSIS, I think you'll find that you won't have a
problem if you consider this the
For whay it's worth, I promote usfm for exactly the reasons being
discussed here. Ease of editing and semantic tags.
The biggest reason not to use markdown for genbooks is the inability to
properly link references to scripture. Since the whole point of having gen
books in the sword platform is
gt; CC:
>
>
> It’s a book - hence GenBook.
>
> It’s not a Commentary.
>
> USFM simply doesn’t apply to the work in focus or to others that I have in
> mind.
>
> There are a few Scripture references in the text.
>
> David
>
> Sent from ProtonMail Mobile
&g
The link Michael points to is freedom of access itself. You'll miss the
difference if you just go poke through the several English translation
available there.
The concept of freedom of access behind unfolding word is found in the book
"The Christian Commons." I strongly recommend reading this
What's your target audience geographically? Is this mostly non-English
speaking concern? or is the gap of material mostly English?
On a desktop (in English,) the gap that "free" can't currently fill is not
Bible Text, but in 20 and 21st century scholarship about Bible issues. It
is very easy to
I'm not really interested in accessing DBL content from within Sword that
isn't already provided. I don't think there's a lot there beside maybe 10
English works, and a few top European language works that we don't already
have access to.
I AM interested in the locked databases of *Logos* and
Is Pocketsword still able to download from alternate locations? That is,
can you download from xiphos or ebible?
It seems like there should be some is/is not that provides at least a
work-around in a comparative analysis of what is still working. Possibly
even symbolically linking back to
It would make more sense to add another file in the FTP structure, like a
defined "read me," index, or "about" file designed for humans, instead of
expanding the conf file.
The .conf file is supposed to be a standardized file for the benefit of
machines. It makes a lot of sense to segregate a
For a conversion project that won't be repeated like a one off non XML
stylesheet HTML file:
I'd suggest investing in a good editor program, which deals with multiple
files in a search and replace. And a macro language.
Working with multi file search:
0. Strip the non text sections (scripts,
The Unfolding Word Team is using Autographa for its "alignment" process
(which means adding strongs numbers, but they also are working on fixing
stray words into a common (UnfoldingWord) versification across languages,
if I understand chat room babble.
I looked at the Linux version and its limited. If you install the windows
version and find success, I'd like to know.
On Sun, Apr 14, 2019, 9:49 AM Tobias Klein wrote:
> Thanks for the links, Michael. I'll have a look at Autographa.
>
> Best regards,
> Tobias
> On 13.04.19 1
I've been working long hours and emailing in my break time. David has the
basics of converting to VPL.
I would then make the entire work a column in a spreadsheet.
Then in other collumns insert a list of Book/chapter/verse in order.
The BCV and versetext columns should align and can be
I think a configuration in the front ends which allows the user to select
the menu selection from a list
Current work's abbreviations (changes for each work)
Language setting (locale)
A specific installed work's abbreviations
Custom (user entered).
___
https://en.wikipedia.org/wiki/Microsoft_Compiled_HTML_Help
CHM is not exactly opensource. Microsoft successfully sued TomTom for
using FAT32 formatting in it's GPS systems without paying any royalties to
Microsoft. That's the old (Gates, Balmer) Microsoft, but still it's a
proprietary
book ID and main title tags, etc.
>
> Hope this gives some useful suggestions that point towards a practical
> solution.
>
> Best regards
>
> David
>
>
> Sent from ProtonMail Mobile
>
>
> On Mon, May 13, 2019 at 14:57, Michael H wrote:
>
> Cyrille
>
1 - 100 of 188 matches
Mail list logo