Template talk:Bibleverse-nb

message: Requesting that someone move the template documentation to Template:Bibleverse-nb/doc and then put  on the page itself. Thanks! --- — Preceding signed comment added by Cymru.lass (talk • contribs)  01:17, 9 March 2011 (UTC)
replies: text: — Martin (MSGJ · talk) 15:21, 9 March 2011 (UTC)
thread_title:  Edit request from Cymru.lass, 9 March 2011 

message: Please change the template so it can accommodate en dashes in accordance with MOS:DASH. – ὁ οἶστρος (talk) 19:44, 22 August 2013 (UTC)
thread_title:  Edit request: Please modify template, so it complies with Wikipedia's MoS 

message: In the article titled Noah there were Bible verses written as 12-15 (with a hyphen) where WP:MOS requires 12–15 (with an en-dash).  I changed them to en-dashes and cited WP:MOS.  The change was reverted by a user who claimed that an en-dash won't work because, he claimed, these are URLs – links to external web sites.
: 
Is it impossible to re-write this template to comply with WP:MOS while also linking to external web sites? Michael Hardy (talk) 17:33, 26 March 2014 (UTC)
replies: text: The template does not violate the MOS per se because it simply displays what's entered into it, whether it be a hyphen or an en-dash or something else. That being said, I think you're asking for the template to automatically convert hyphens to en-dashes so it always complies with WP:ENDASH. I made a change in the sandbox that does just that; [ take a look]. Example: . What do you think? LittleMountain5 23:15, 27 March 2014 (UTC)
replies: text:  Interesting.  Is there a way to change that from sandbox to the actual template? Michael Hardy (talk) 05:02, 28 March 2014 (UTC)
replies: text: Yes, by copying the content of the sandbox and pasting it onto the main template page. However, I'm not so sure the code I provided is optimal; it more than doubles the template's load time. I'll ask if there's a better solution over at WT:WPT. LittleMountain5 06:28, 31 March 2014 (UTC)
thread_title:  This template violates [[WP:MOS]] 

message: Going along with the change to  (see Template talk:Bibleverse#Replacing the tool with a Lua module), this template should be changed for consistency as was discussed there. Copy the version in the sandbox to implement the change. JFH (talk) 21:49, 8 January 2017 (UTC)
replies: text: Done — JJMC89 (T·C) 05:05, 9 January 2017 (UTC)
thread_title:  Template-protected edit request on 8 January 2017 

message: I'm very sorry, I should have tested this more thoroughly before the last edit request. The template is creating errors when the version is not defined (e.g. ). I haven't come up with a simple fix, so the last edit should be undone until I figure out how to make it work. This does not affect . JFH (talk) 05:05, 10 January 2017 (UTC)
replies: text: -- John of Reading (talk) 07:17, 10 January 2017 (UTC)
thread_title:  Template-protected edit request on 10 January 2017 

message: I have made changes to Module:Bibleverse so that this template can use it (through Template:Bibleverse. The testcases are working. Please update it to match Template:Bibleverse-nb/sandbox. JFH (talk) 04:17, 17 January 2017 (UTC)
replies: text: Done. We're now in the weird situation that Template:Bibleverse & Template:Bibleverse-nb are protected while the module they rely on, Module:Bibleverse, is not. , please apply for WP:TPE at WP:RFP/TE citing your work on these two templates and the module so that we can sensibly increase the protection on the module. (pinging the two admins most recently active so that they're aware of the reasoning, , ) Cabayi (talk) 12:14, 17 January 2017 (UTC)
replies: text: Oops, Module is already protected. Still think JFH ought to have TPE by now. Cabayi (talk) 13:37, 17 January 2017 (UTC)
thread_title:  Template-protected edit request on 17 January 2017 

message: Trialpears: today's change has messed up the following simple markup:

()

displaying a newline before the close parenthesis:
()
Please fix. —Anomalocaris (talk) 20:28, 10 January 2023 (UTC)
replies: text: @Anomalocaris Sorry for that! Fixed now. That was a really stupid issue caused by me accidentally adding a second documentation and thereby blank row. Thanks for telling me! --Trialpears (talk) 20:35, 10 January 2023 (UTC)
replies: text: Trialpears: Thank you for fixing it so quickly! —20:47, 10 January 2023 (UTC)
thread_title:  New bad behavior within table cells