Jump to content

Bibleverse on false Place


Fabian

Recommended Posts

Hello

 

I have import a User Bible and now I see that Accordance has moved a Verse. In the TXT it is on the correct place.

 

You'll see that the Psa. 150:4 is between Psa. 50:21 and 50:22. And in the txt it is in <i> </i>. And now not in italic anymore.

 

Accordance 10.4.3.2 import with OS X 10.9 now 10.10

 

Greetings

 

Fabian

post-32723-0-76510200-1413554616_thumb.png

Edited by Fabian
Link to comment
Share on other sites

Funny: I have new import the User Bible and now the Psalm 150:6 is between Psa. 50:23 and Psa. 51:0

Link to comment
Share on other sites

  • 1 month later...

This happens in many Bibles which I have import under Acc 10 and now with Acc 11.0.2 it is not better.

 

Greetings

 

Fabian

Link to comment
Share on other sites

The problem is when the german Bible has on verse more than the KJV.

 

Best solution is when Accordance itself can handle the german Notation. See my post on http://www.accordancebible.com/forums/index.php?showtopic=13348&hl=

 

The second is that we know how the GBS has the german Bibles prepared for this problem.

 

The Third is that Accordance let it pass anyway.

 

But so it makes no fun with Accordance. :(

 

Greetings

 

Fabian

Link to comment
Share on other sites

Correction: This happens even in Bibles with correct KJV verse numbering. Also definitive a bug.

 

Greetings

 

Fabian

Link to comment
Share on other sites

I think in order to make it display properly, you have to use English Bible verse system. It has to be exactly the same.

 

The problem occurs when the User Bible has different verse numbering system.

 

Accordance also has problem with its own Bibles when the parallel Bible has different numbering system.

 

I have pointed out a related problem here.

 

What I would do is to change the User Bible verse numbering to exact the same as the English Bible. You may have to separate a verse in your user Bible or group two verses together, depending the difference between the User Bible and the English Bible.

 

Here are some examples:

 

The English Bible does not have 1 Chr 21:31. The Chinese Union Version has it. 1 Chr 21:31 in CUV is exact the same as 1 Chr 22:1. Therefore, I changed the verse number of 1 Chr 21:31 into 1 Chr 22:1 in the CUV. Then I make comments in the parenthesis.

post-32138-0-92065000-1418077772_thumb.png

 

The CUS does not have John 7:53, but the English Bible has. Therefore I created John 7:53 in the CUS, and made a comment in the parenthesis that the CUS does not have this verse, and the its content is included in John 8:1 in the original version of CUS.

post-32138-0-09403100-1418078296_thumb.png

 

The advantage of User Bible is that you can manipulate the content when necessary.

 

The major problem is that when the original text has different numbering system from the English Bible.

It is not a user Bible problem, but a problem in Accordance itself. This is the problem I pointed out in the post I mentioned above.

An indirect way is to tie the English/User Bible with the original text, rather than making parallel text. Then the problem of Rev 12.18 in my post will be solved. However, you also lose the powerful feature of the tagged text in the parallel window. :(

 

Blessings,
Martin

 

Link to comment
Share on other sites

There are similar issues when tying the English text to the Hebrew text. For example, the Hebrew Bible for Malachi has only three chapters; English Bibles split that chapter at v. 19 and make it the first verse of chapter 4.

 

Since these texts are so common in scholarly research, we can write code that synchronizes them. We simply can't do that for every Bible in every language, specially one imported as a User Bible. The struggles you have when making a User Bible will help you appreciate the hard work of our programmers, though, too much of which we just take for granted.

  • Like 1
Link to comment
Share on other sites

Hello Martin

 

Thanks, Yes even the Luther 1912 and the Elberfelder 1905 from Accordance has this. Only the german Bibles from the GBS works properly.

 

But there are a few chapters that the german Bibles has one verse more. To display it in parallel with other german Bibles it would make no difference but the Accordance-App won't and shift Bibleverse.

 

Hello Dr. J.

 

Yes only for the verse numbering of the Zürcher 1931 and 54 it makes no sense (but the most here are the same like KJV), but for the common Bibles. Even that the german Bibles from the GBS works perfect. So has Accordance no problem that the german Bibles has the same "only 3 Chapters in Malachi" and also has Accordance no problem for User Bibles with only 3 chapters. Here it works properly with User Bibles.

 

So please best Biblesoftware on the planet...

 

Greetings

  • Like 1
Link to comment
Share on other sites

There are similar issues when tying the English text to the Hebrew text. For example, the Hebrew Bible for Malachi has only three chapters; English Bibles split that chapter at v. 19 and make it the first verse of chapter 4.

 

Since these texts are so common in scholarly research, we can write code that synchronizes them. We simply can't do that for every Bible in every language, specially one imported as a User Bible. The struggles you have when making a User Bible will help you appreciate the hard work of our programmers, though, too much of which we just take for granted.

 

I know only little. But I guess there are only a handful of Bible verse numbering systems.

 

In terms of parallel, I guess the major factor is the verse numbering system rather than the language/content of the text.

Therefore, Accordance just needs to synchronize the different verse numbering systems, for example, 1 Chr 21:31 of system A = 1 Chr 22:1 of system B.

 

Chinese Bibles or German Bible probably follow a system that is different from the current popular English verse numbering system. (Even different English versions have different verse numbering systems.)

 

As long as Accordance makes the different systems separate, and let users to choose a verse numbering system when import, it would theoretically solve the problem, I guess.

 

I wish scholars just make an agreement to unify all the verse numbering systems. It does not change the text at all, but will help the programmers so much!

  • Like 1
Link to comment
Share on other sites

Hello

 

After a bedtime and dreaming of Accordance.

 

I belive that this is one of the most important point for a future release. Because if this problem solved then they have the base to import other Bibles with a numbering system like the Strong's or G/K.

 

Like the

 

German Elberfelder CSV 2009 with Strong's

 

German Elberfelder 1905 ...and 1871

German Luther 1912 and 15??

German Münchner neues Testament

 

Russian Synodal Translation

 

Chinese Union Version Simplified

Chines Union Version Traditional

 

Portuguese Almeida Revista ...

 

Dutch Statenvertaling

 

et al.

 

 

This would be a huge step forward to sell Accordance. Even in the not english speaking World

 

Greetings

 

Fabian

Link to comment
Share on other sites

  • 2 weeks later...

O.K. guys

 

I've been made a Bible that don't have the german nor the KJV verse numbering on Job

 

KJV Zürcher 1931 and 54

Job 40:1 [39:31]

Job 40:2 [39:32]

Job 40:3 [39:33]

Job 40:4 [39:34]

Job 40:5 [39:35]

Job 40:6 [40:1]

Job 40:7 [40:2]

Job 40:8 [40:3]

Job 40:9 [40:4]

Job 40:10 [40:5]

Job 40:11 [40:6]

Job 40:12 [40:7]

Job 40:13 [40:8]

Job 40:14 [40:9]

Job 40:15 [40:10]

Job 40:16 [40:11]

Job 40:17 [40:12]

Job 40:18 [40:13]

Job 40:19 [40:14]

Job 40:20 [40:15]

Job 40:21 [40:16]

Job 40:22 [40:17]

Job 40:23 [40:18]

Job 40:24 [40:19]

Job 41:1 [40:20]

Job 41:2 [40:21]

Job 41:3 [40:22]

Job 41:4 [40:23]

Job 41:5 [40:24]

Job 41:6 [40:25]

Job 41:7 [40:26]

Job 41:8 [40:27]

Job 41:9 [40:28]

Job 41:10 [41:1]

Job 41:11 [41:2]

Job 41:12 [41:3]

Job 41:13 [41:4]

Job 41:14 [41:5]

Job 41:15 [41:6]

Job 41:16 [41:7]

Job 41:17 [41:8]

Job 41:18 [41:9]

Job 41:19 [41:10]

Job 41:20 [41:11]

Job 41:21 [41:12]

Job 41:22 [41:13]

Job 41:23 [41:14]

Job 41:24 [41:15]

Job 41:25 [41:16]

Job 41:26 [41:17]

Job 41:27 [41:18]

Job 41:28 [41:19]

Job 41:29 [41:20]

Job 41:30 [41:21]

Job 41:31 [41:22]

Job 41:32 [41:21]

Job 41:33 [41:24]

Job 41:34 [41:25]

 

And it comes correct with the Elb-Lem and the KJV. So it can't be to difficult to make it for the different verse numbering systems from the different Bibles.

 

And even sometimes with a different verse numbering it comes absolut correct and sometimes if one verse shifted Accordance has problems. I believe it comes correct if this is programmed

 

So I know Oaktree has the knowing to handle different verse number systems.

 

It's only the "will" which is against to support it all.

 

I'm really frustrated, that the best Biblesoftware is after 20 year not able to support this few different Bible verse numbering systems.

 

Then when Accordance has this done, then they will be able to import other Bibles with a Strong tagging system, and it would be much easier to make User Bibles.

  • Like 1
Link to comment
Share on other sites

Fabian: Accordance supports every numbering system, for the modules that we create. But you have no idea how complex and difficult it is to make a Bible line up with every other Bible no matter what system they are using. In fact, even our most senior developers usually need help to get this correct. This is why we have not been able to offer a multitude of alternate schemes for user Bibles. As you know, there is no one alternate scheme that would satisfy our users.

 

I do not know whether other software that accepts different numbering schemes, does actually align each verse correctly by content when the texts are used in parallel. This is what Accordance attempts to do, and has done from the beginning.

Link to comment
Share on other sites

  • 10 months later...

Hello Helen

 

Thanks for the possibilities 11.1. A really good solution. 

 

Greetings

 

Fabian

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...