Tobias,
You need to look up the language codes from ISO 639-2 and ISO 639-3
Using only ISO 639-1 is clearly inadequate.
Aside: Language decoding files complied into front-ends can easily become out
of date.
So for example, there are still 8 language codes at eBible.org that are not yet
decoded by PocketSword.
Regard#,
David
Sent from ProtonMail Mobile
On Mon, Jun 3, 2019 at 22:06, Tobias Klein <[email protected]> wrote:
> I can answer the point about the number of repos and translations.
>
> Basically I filtered on "known" languages. If a repo didn't have any "known"
> languages it was also hidden. A "known" language is one where the language
> code can be mapped to a language name.
>
> Is there any way to render the language codes of all those indigenous
> languages on eBible.org into something more readable than a few letters?
>
> Best regards,
> Tobias
>
> Am 3. Juni 2019 21:01:56 MESZ schrieb Tobias Klein <[email protected]>:
>
>> Hi Troy,
>>
>> Yay! I'm excited to hear that Ezra Project works for you and thanks for this
>> report! :)
>> I'm glad I found some tools that allow packing of Electron applications into
>> *.debs and *.rpms rather easily.
>> I now have a script that can create packages for Ubuntu 18.04 & 19.04,
>> Fedora 29 and CentOS 7 in one go, so for future updates it's gonna be easier
>> with the packaging. I may still add some other distributions based on
>> demand. The packaging for each of these distributions is done in individual
>> Docker containers, which also really helped to get this done efficiently.
>>
>>> The repos list doesn't seem to show all the repos available from our
>>> registry.
>>
>> Oh, ok. Interesting. I though I'm just showing the content of the "master
>> repo list".
>> Which repos are shown on your computer and which are missing?
>>
>> Essentially I'm just calling installMgr->refreshRemoteSourceConfiguration(),
>> then installMgr->saveInstallConf() and then I'm iterating over
>> installMgr->sources to get the repositories.
>>
>>> Selecting CrossWire and choosing Greek, English, and Hebrew, I don't see
>>> the WHNU Greek module.
>>>
>>> Noticed the eBible.org repo only shows that is has like 74 modules
>>> available, but I think Michael has like 2000 or something :)
>>
>> Currently only modules with "recognized languages" are shown.
>> When loading the languages I'm separating them into "known" ones and
>> "unknown" ones using the ISO-639-1 Javascript module.
>> https://www.npmjs.com/package/iso-639-1#validatecode
>> Only the "known" languages end up being shown in the installation wizard. I
>> should change that and also show the other ones below the recognized
>> languages in the installation wizard.
>>
>>> I like that I can have multiple tabs of different Bibles pointing to
>>> different locations.
>>>
>>> Noticed Hebrew (module: WLC) is left justified. You should be able to key
>>> off the config entry: Direction=RtoL
>>
>> Thanks for the hint! Could I do that automatically based on certain
>> information in that bible's *.conf file?
>>
>>> I like that I can highlight multiple verse and then click a tag to add them
>>> to that tag. I am not sure if they are tagged individually, or as a group,
>>> but regardless, they all seem to be tagged.
>>
>> They are tagged individually in the database.
>>
>>> I am not sure how to show all the verses associated with one of my tags.
>>
>> Click on "Select tag" (next to "Select book") in the menu above the text
>> display area and choose one. You can also choose multiple ones. Then click
>> on "Select tag" again to hide that dropdown.
>>
>>> I notice you're not showing all the books associated with the current
>>> module.
>>
>> Yes, that's correct. At the moment the books shown is a static list. The
>> only thing dynamic is that within that static list Ezra Project checks which
>> of these books are actually available and disables the links if they're not.
>>
>>> Great start! Thanks for your work! I am sure building up personal tab
>>> libraries of Bible topics and sharing those with others can be a wonderful
>>> way to study God's Word.
>>
>> Thanks for the encouragement :). Sharing a tag library could be a feature
>> for the future. At the moment a "Word export" is implemented, but that
>> obviously is not the same as sharing a technical database. I could implement
>> a simple JSON or XML export/import to support such a feature.
>>
>> There's other features besides tagging that I have on my mind. Generally I
>> want to support the user in creating material based on the bible that is not
>> "separate" (like separate text documents), but rather directly linked with
>> the text.
>>
>> Best regards,
>> Tobias
>
> --
> Message sent from my phone. Please excuse brevity.
_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
