Template talk:Infobox Bible translation

Good work. I've added an optional image and a border (looks nicer that way). Also, I've changed the relative "em" box size to a fixed, pixel-based one. I know fixed widths are evil, but as far as I can tell there's no way to specify the width of an image in "em"s. Please don't hit me. Collard 11:46, 6 March 2006 (UTC)

Oh, and I made the font size a bit smaller as well. Is this okay? Collard 11:50, 6 March 2006 (UTC)

One more thing (as if my previous nagging hadn't merited a boot to the head already): what should one put for textual basis? Something simple like "Critical text" or "Textus receptus", or something more specific like "United Bible Societies Greek New Testament"? I know you had the example saying "original greek", but this misses an distinction between the text type used for the KJV and the text type used for most post-Westcott/Hort translations. Collard 12:00, 6 March 2006 (UTC)

Whatever you think is best. Brusselsshrek 11:36, 8 March 2006 (UTC)

I'm glad you're so confident in me (that or just naive, wink). I've added a "derived_from" field for translations which are derived from both an English text and the Hebrew/Greek text. ESV, NKJV, WEB come to mind. (You'll see this in action on the ESV page in a moment.)

Very nice work! Two details:

• Is there any real difference between "religious affiliation" and denomonation?
• Let's put in apocrypha (yes or no / what books). Dovi 12:44, 4 January 2006 (UTC)

thanks Dovi.

• By "religious affiliation" I was thinking of "Christian", "Jewish", "Jehovah's Witness". By "denomination" I was thinking of "Baptist", "Methodist" etc. I guess just religious affiliation is enough. Denomination removed
• Apocrypha added
• I would like the verses to be across both columns but I don't (yet) know how to do this
• In terms of layout, I think the 3 dates would be nice as 3 columns in a sort of sub-box. Again I don't (yet) know how to do this.
• I also want a large number of the parameters to be optional (see actual template), so the minimal template would, for example, only require, say, name and date(s). This does not seem to be working (yet). Any ideas what's wrong?

Brusselsshrek 09:57, 5 January 2006 (UTC)

• It appears someone was adding his one personal opinion about the "reading level" of various Bibles. I could find no source for this addition, so I reverted all the edits.131.187.254.7 18:51, 22 March 2007 (UTC)

Reading Levels

Wareh and I are discussing the reading level problem. The "grade level" can vary by as much as 5 grades depending on the scoring calculation (Flesch Kincaid and Gunning Fog are typically 2 to 4 grades apart because of different methods of calculation). I've also found that most of the numbers available online stem from Zondervan, which seems to put a Gunning Fog number on the competitors and something closer to a Flesch Kincaid number on the NIV. After doing some tests in Word and Readability Studio, I've suggested to Wareh that we put a broad description in the reading level box instead of a number. The description should agree with BOTH the online Zondervan numbers and the numbers that are reproducible on Word processor tools or specialty readability tools. Examples, CEV "Grade School." NIV "Middle School." ASV "High School." If there are no objections here or from Wareh, I'll make those changes this week. However, since no single site has information on all of these translations, can I leave the attribution off, or do I have to hunt each one down?

Thanks.

Tim 15:36, 31 October 2007 (UTC)

PS -- for an example of the problem of reading scores, here are the different scores I generated off of the entire New Testament for one translation (i.e. these were NOT different samples).

Revised Spache 3.4; Simplified Automated Readability Index 5.0; New Dale-Chall 5-6; Powers, Sumner, Kearl 5.3; Coleman-Liau 6.4; Raygor Estimate 7; Laesbarhedsindex (LIX) 7; Fry 7; Rate Index (RIX) 7; Flesch-Kincaid 7.7; Automated Readability Index 7.9; FORCAST 8.2; SMOG 9.0; New Fog Count 9.9; Gunning Fog 10.2; Linsear Write 11.4; Average (Mean) 7.3

The Flesch-Kincaid is well known, and most of these scores (including the average) are in the Middle School range. But just putting a number on there isn't helpful, especially if your source is a publisher reporting on its competition.

Tim 19:26, 31 October 2007 (UTC)

The essential thing is to include only a verifiable measurement by a widely available test, so that we're not offering an original synthesis of several sources. Wareh 21:01, 31 October 2007 (UTC)

Wareh -- hence my suggestion to give a broad description that will fit anything that people either do themselves or find online. I think I forgot to mention -- Flesch-Kincaid shows up with different scores depending on the software you are using. I've scored the same file at 6.0 in Microsoft Word, 7.4 in the old DOS Readability Plus, and 7.7 in the Readability Suite. Again, this was the same file and the same Flesch Kincaid test. Each software consistently came up with the same score as itself, but different from the other software. Even if we settled on Flesch-Kincaid, we'd now have the problem of which tool to draw the Flesch-Kincaid from. A "verifiable" measurement isn't verifiable if it varies with the software. Also, people will be trying to verify the scores on the different web sites out there, which won't be identifying their tool or scoring method. I think that you were right about the descriptive values in the Textual Basis and Translation Method. I think your idea applies here too. Virtually everyone will be able to verify "Grade School," "Middle School," and "High School" regardless of the source or software they are using. Tim 23:15, 31 October 2007 (UTC)

Copyright dispute

It is being disputed at Wikipedia_talk:Copyright_problems/Archive_12#Copyrighted_quotes_in_infoboxes that displaying quoted verses in the infobox is a copyright violation (for translations for which copyright has not expired). It is being suggested that if the infobox presents quoted verses, that it should indicate why the quotations are being used. At the very least, I would suggest reordering, so that the quoted verses are shown immediately after the type of translation. Needs further discussion.--Jeffro77 (talk) 17:13, 3 October 2008 (UTC)

Quoting a single verse is absolutely within fair use. There isn't a copyright holder on the planet who wouldn't want a verse of his translation represented in an article ABOUT his translation. SkyWriter (Tim) (talk) 17:26, 3 October 2008 (UTC)

Tell that to the people disputing it.--Jeffro77 (talk) 18:00, 3 October 2008 (UTC)

I'll be glad to -- where do I find them? SkyWriter (Tim) (talk) 18:11, 3 October 2008 (UTC)

"Concordant ... sublinear" display

The template is currently displaying blocks of text titled "Concordant Hebrew English Sublinear" and "Concordant Greek Text Sublinear". I don't understand why these are here at all. Should they be removed? Feline Hymnic (talk) 17:46, 13 April 2009 (UTC)

These were added as a result of a copyright concern about quoting verses from copyright-protected translations. See link from topic above.--Jeffro77 (talk) 07:43, 14 April 2009 (UTC)

Thanks. Hmmm... that discussion weaves all over the place (I realise that is what such discussions tend to do) and some of it is about copyright. Yes, it started off with copyright. But there seems to be no copyright-related conclusion to the discussion. (What conclusion there is seems to be about providing some sort of obscure, hardly-even-English text, itself a translation of sorts, and utterly impenetrable and meaningless even to a lifelong church person.) So I think my original point is still valid... what, in a sentence or two, is the reason for those obscure sequences of English and non-English words? Feline Hymnic (talk) 19:57, 14 April 2009 (UTC)

There are no "non-English" words in the template. Maybe you refer to the Hebrew loan-word Elohim, and the obscure English word eonian. And many 'lifelong church persons' wouldn't know a bible if they fell over one. The quoted verses compared to the interlinear text help demonstrate the style of translation, and the copyright argument (not proposed by me) is that if there is nothing to compare with, there is no justification in quoting key verses from the selected translation at all. If you have an issue with this, perhaps you should continue the original discussion from the link above with User:Moonriddengirl.--Jeffro77 (talk) 22:21, 14 April 2009 (UTC)

I have made the verses collapsible so they don't clutter the template by default, while still retaining the verses (with the comparison for copyright purposes).--Jeffro77 (talk) 09:23, 3 May 2009 (UTC)

I believe the Hebrew and Greek sublinear texts should be removed. They clutter the box. And they add the impression that the sublinear is some sort of golden standard to which the others should be compared. Peter Ballard (talk) 00:43, 15 May 2009 (UTC)

I agree with Peter's suggestion here.SkyWriter (Tim) (talk) 00:50, 15 May 2009 (UTC)

p.s. Looking further up, I see the rationale was discussed at Wikipedia_talk:Copyright_problems/Archive_12#Copyrighted_quotes_in_infoboxes (introduced right at the end of the discussion at 23:34, 3 October 2008). But frankly, it's a bad solution. Adding the "sublinear" for "comprarison" just clutters and confuses. The verses are fine alone - they give a flavour of the translation style - and then users can click to other translations to compare, if they wish to. Peter Ballard (talk) 00:55, 15 May 2009 (UTC)

Alternatively, if the lack of context is the problem (the point User:Moonriddengirl kept hammering at Wikipedia_talk:Copyright_problems/Archive_12#Copyrighted_quotes_in_infoboxes), then we should delete the verses from this template, and instead create the articles Genesis 1:1 in different Bible translations and John 3:16 in different Bible translations, and provide links to those articles in this template. Peter Ballard (talk) 01:13, 15 May 2009 (UTC)

I think your first suggestion was best. The verses just give us a sense of style. The concordant just reads like bad Amplified Bible drafts. It's not necessary. I appreciate her concern, but I don't think it's warranted. SkyWriter (Tim) (talk) 01:34, 15 May 2009 (UTC)

Actually it occurs to me that we could have our cake and eat it too: Quote the verse and then, in place of the current Hebrew/Greek sublinear, have links to Genesis 1:1 in different Bible translations and John 3:16 in different Bible translations respectively, to satisfy the copyright concerns. I'm a little wary of going against a consensus which was established at Wikipedia_talk:Copyright_problems. Peter Ballard (talk) 01:38, 15 May 2009 (UTC)

I'll go with that. Good thinking!SkyWriter (Tim) (talk) 01:59, 15 May 2009 (UTC)

I'm not sure that the suggested articles (Genesis 1:1 in different Bible translations and John 3:16 in different Bible translations) are warranted. If the path chosen is to link to relevant articles, there are existing articles for Genesis 1:1 and John 3:16, which already contain various translations of those verses.--Jeffro77 (talk) 13:39, 15 May 2009 (UTC)

Good point. I've done the change, explicitly pointing to the Genesis 1:1 and John 3:16 pages for alternative translations. Hopefully this will satisfy the WP:NFC concerns. Peter Ballard (talk) 02:20, 16 May 2009 (UTC)

If you are going to quote John 3:16 I'd also like you to quote James 2:24 "You see that a man is justified by works and not by faith alone." There are people who don't like John 3:16 out of context and that is the easiest way to put it back into it. ThePepel-Eterni (talk) 18:53, 6 May 2012 (UTC)

There's no point changing the verse every time someone thinks a certain verse might better suit a particular denomination. The verses that were selected were used because they are verses that have their own articles, and there are reasons related to using copyright sources for doing so.--Jeffro77 (talk) 01:29, 7 May 2012 (UTC)

Change in quote

A recent edit changed the default quote from John 3:16 to Matthew 25:41. It was done without discussion here, without comment as to why it was done, and every edit that applied it to an existing article was similarly done without comment. The verse is not appropriate. It would likely inflame annihilationists. If we're changing it, we should discuss it first. However, John 3:16 is the most well-known English language verse and so it makes sense to keep it. Also, other templates use it such as {{Bibleverse}} and {{Bibleverse-nb}} while a third uses Genesis 1:1. --Walter Görlitz (talk) 14:55, 20 August 2012 (UTC)

Part of the problem is that it's the first line of a longer phrase that ends in v. 46 so it leaves open quotes.

On a separate note, while speaking of quotes, I should also state that when the verse was added to the individual translation articles, it was against formatting standards where straight quotes were ignored and “ and ‘ were used instead of " and '. --Walter Görlitz (talk) 15:00, 20 August 2012 (UTC)

The default verses that were chosen for the template were selected because there are articles about those specific verses. There are potential copyright issues in relation to using verses from translations subject to copyright where the text is used without any basis for comparison or critical review. The presence of articles about those verses provides such a basis. There is no good reason to arbitrarily change the verses to 'xyz's favourite verse'. The advice to editors here is Do not change the verses without discussion.--Jeffro77 (talk) 09:02, 21 August 2012 (UTC)

I cannot see short passages as a copyright violation in any English-speaking country. Exactly which copyright policy would it violate? --Walter Görlitz (talk) 13:57, 21 August 2012 (UTC)

Wasn't my decision. Refer to discussion linked two threads above.--Jeffro77 (talk) 08:41, 22 August 2012 (UTC)

Current copyright policy would not exclude longer passages, but it's good to know that the copyright issue was discussed. --Walter Görlitz (talk) 13:43, 22 August 2012 (UTC)

John 3:16 is an inflammatory passage. Quoted by itself it is an deliberate evangelizing attack on Catholics and Eastern Orthodox. We do not like that verse out of context AT ALL. We do not believe in everlasting salvation just by belief. ThePepel-Eterni (talk) 00:23, 24 August 2012 (UTC)

Making a major, and choosing such a poor verse to highlight is not the solution to your opinion that it is inflammatory, which I don't believe it is. Please suggest what a better passage would be. --Walter Görlitz (talk) 03:45, 24 August 2012 (UTC)

There is no context implied at all. The supposed "deliberate evangelizing attack" is in the mind of the complaining editor, who should assume good faith. It is unclear on what basis ThePepel-Eterni claims to speak for all "Catholics and Eastern Orthodox" by his use of "we".--Jeffro77 (talk) 09:21, 24 August 2012 (UTC)

I see from the comment above, that the editor has an axe to grind. The primary reason that I see John 3:16 being used is that it is the most well-known verse in the English language: [1], [2], [3] and other sources. This may be a byproduct of the extent of non-Catholic influence in the English world, or it may be something else. Regardless as to why it is the most popular verse in the English language, the fact remains that it is. This is why a discussion should be opened if we are going to change it and not simply make the change and arbitrarily using an arbitrary verse. And as a side-note, the article on the verse indicates that "the text of the verse is incorporated into the Divine Liturgy of St. John Chrysostom, the fourth century archbishop of Constantinople ... [and ] ... is still commonly used in the Eastern Orthodox Church and in the Byzantine rite of the Roman Catholic Church" so it can't be as "inflammatory" as ThePepel-Eterni has stated. Granted, that statement is not referenced nor is "commonly" defined. It could be an annual service on a special day or it could be more frequent than that. --Walter Görlitz (talk) 15:37, 24 August 2012 (UTC)

John 3:16 is well established as a well-known verse of the Bible. There is absolutely nothing inflammatory about its usage in the template at all, and there is a specific reason for using a verse that has its own article.

But if people are going to arbitrarily suggest their own favourite verse instead, how about 1 Corinthians 14:34? (That, by the way, is a joke.)--Jeffro77 (talk) 23:16, 24 August 2012 (UTC)

Aside from the inflammatory nature of that verse, I do like that it would have a footnote in the NASB, which is one of its hallmarks. --Walter Görlitz (talk) 01:24, 25 August 2012 (UTC)

Not sure I follow you. There is no footnote in the NASB for 1 Corinthians 14:34.--Jeffro77 (talk) 01:33, 25 August 2012 (UTC)

Bible verse headers

@Remsense I see that you've reverted my changes, but I'm just a little confused as to why you're against "[hardcoding] colors unless you really need to". As a pre-existing example that I haven't touched, you can see Show/Hide headers with hardcoded colours in Portal:Religion (and other portals), which is quite similar to this case.

If an appropriate header colour isn't set, then it looks like there are just links to Genesis 1:1-3 and John 3:16 sitting there for some reason (because the Show/Hide options are small and right-aligned), and these links lead to articles, rather than the actual Scripture text for the translation in question, which is confusing. From a visual design perspective, I feel that having no colour with an element that has two options (a link, and then an option to display more text) is simply less helpful than having an appropriate, non-obtrusive colour. VistaSunset (talk) 06:14, 27 October 2024 (UTC)

I don't think the color serves a specific indicative function for readers that you put it out to: what's more, there's a lot of templates suddenly floating around that need to look correct on both light and dark mode, and it's really better to avoid hardcoding colors if we can help it. I'm trying to figure out if we can potentially specify a variable color used by the site, or if that would only work for Vector 2022. Remsense ‥ 论 06:49, 27 October 2024 (UTC)